Re: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-22 Thread Cameron Moore
* [EMAIL PROTECTED] (Jim Wilson) [2001.12.22 08:27]: > Cameron Moore <[EMAIL PROTECTED]> said: > > > Speaking of which, when I hit 's' to switch panel, it looks like we're > > reading the XML file each time. It funny that loading scenery doesn't > > cause any hiccups in performance but switching

Re: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-22 Thread Jim Wilson
Cameron Moore <[EMAIL PROTECTED]> said: > Speaking of which, when I hit 's' to switch panel, it looks like we're > reading the XML file each time. It funny that loading scenery doesn't > cause any hiccups in performance but switching panels does. Yep, I just used the panel-load that was/is boun

Re: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-21 Thread Cameron Moore
* [EMAIL PROTECTED] (Norman Vine) [2001.12.21 19:25]: > Bernie Bright writes: > > > >Norman Vine wrote: > >> > >> We could even walk both the compressed and the uncompressed > >> tree and use the 'newest' file for easy experimentation. > >> > >Easy and slow. I remember someone once saying on th

RE: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-21 Thread Norman Vine
Bernie Bright writes: > >Norman Vine wrote: >> >> We could even walk both the compressed and the uncompressed >> tree and use the 'newest' file for easy experimentation. >> >Easy and slow. I remember someone once saying on this very list that >file opening is a performance killer :) It can be

Re: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-21 Thread Bernie Bright
Norman Vine wrote: > > John Check writes: > > > >> Eventually, I guess you could have a separate subdirectory for each > >> instrument, with a README, etc. Think of yourself as a fine > >> craftsman, like a watchmaker. > >> > > > >err.. uhh... umm.. whatever. > >I'd like to stay away

RE: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-21 Thread Norman Vine
John Check writes: > >> Eventually, I guess you could have a separate subdirectory for each >> instrument, with a README, etc. Think of yourself as a fine >> craftsman, like a watchmaker. >> > >err.. uhh... umm.. whatever. >I'd like to stay away from excessive directories. Maybe if t

Re: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-21 Thread John Check
On Friday 21 December 2001 04:34 pm, you wrote: > John Check writes: > > While I'm at it... is there a chance we might see being able to > > include fully defined layers in instruments at some point? The best > > I can do now is > > > > > > > > > > > You should be able to include a

re: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-21 Thread David Megginson
John Check writes: > While I'm at it... is there a chance we might see being able to > include fully defined layers in instruments at some point? The best > I can do now is > > > > > where Layers/gauge-face.xml contains n gauge face Aircraft/Instruments/Textures/v

Re: Including instrumenst was: Re: [Flightgear-devel] c310 Panel

2001-12-08 Thread Andy Ross
I found the following magazine review, which I used to fix the performance of the YASim model. It's the turbo variant. http://www.planeandpilotmag.com/content/specs/79cessnaturbo.html Also, this site, which is a buyer's guide for the 310 family, has lots of good trivia about equipment variat