[Flightgear-devel] Re: Materials animation bug
* Jim Wilson -- Wednesday 25 May 2005 01:44: > It looks like setting up a materials animation with emission values clobers > the ambient values (sets them all to 0). This produces some pretty strange > looking shading. No, it looks as if you are neither using the most recent cvs version, nor are you reading your private email. I fixed that two days ago and sent you a CC about it. (Or are there *still* problems?) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] MD-11 is slow (was FlightGear startup time)
On May 24, 2005 07:45 am, Melchior FRANZ wrote: > for (3): use as few textures as possible; You can: > - edit material.xml and let it share textures (only one wood > texture) or start fgfs in the desert :-) > - use aircraft with few and small textures (hint: avoid the MD-11 > :-) - scale down textures > But all that makes the scenery uglier and is probably not what you > want. The gain is probably not worth it, anyway. Sorry about that. =( I will do an update soon, which will include: * down sizing the textures * eliminating the LOD's * directories and files restructuring * landing gear animations * a more "complete" cockpit model. * possibility of a better 3D model for the aircraft But first, I will need to finish these monstrous scripts for the A380. Your help in speeding up this process will be most welcome though. =) Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Transparency
Hi Mostyn "Mostyn Gale" writes I am trying to create an upper layer on a gauge which masks lower layers using transparency. I have looked at the data/aircraft/Instruments/fuel.xml file which appears to do this. However I can not figure out where the transparency comes from. Could someone point me in the right direction, I am not sure what you are asking but in the above case the transparency is provided by the textures.If you have a look at the textures that fuel.xml calls you will see they all have masks. Cheers, Mostyn Cheers Innis ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Backing out Andy's p51d changes
Hi Andy, On the p51d fdm configuration, it looks like the substantial change was actually increasing the turbo multiplier from 2.0 to 5.5, and not reducing the cruise speed as stated in the CVS log of March 23. The cruise speed change does have an effect, but it is fairly small. The problem with putting the turbo multiplier up in that range is the manifold pressure output is directly multiplied by that number. So full throttle produces an output of 164 inHG manifold pressure. We should be seeing about 61 inHG at sea level for this engine. Setting this multiplier lower to get the correct manifold pressure with turbo at sea level should reduce the maximum flight level for the aircraft since the second stage turbo cannot currently be modeled. On the other hand, using this lower value should NOT produce incorrect lower altitude performance since all the data I'm using is for below the 20,000 ft altitude where the second stage kicks in. The drag numbers calculated by YASim should be more or less correct up to at least up to 20,000 ft where the second stage would be kicking in. If there is a problem that setting the multiplier to 5.5 fixes, I suspect it is in the FDM design and not the P51D configuration. Any ideas how we can fix or work around this? Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Materials animation bug
It looks like setting up a materials animation with emission values clobers the ambient values (sets them all to 0). This produces some pretty strange looking shading. Best regards, Jim Wilson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Transparency
I am trying to create an upper layer on a gauge which masks lower layers using transparency. I have looked at the data/aircraft/Instruments/fuel.xml file which appears to do this. However I can not figure out where the transparency comes from. Could someone point me in the right direction, Cheers, Mostyn ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Strange acceleration issues with 9.8---possibly terrain related?
Le mardi 24 mai 2005 à 16:42 -0500, Wesley Alden Pegden a écrit : > while I was at it. And magically: it worked, even though my frame < > > rate in glxgears is only up to 750. I'm now where I remember being a > few years ago, which is great > Wow, thanks for all the replies! So, in any case... direct rendering was > indeed working, it glinfo reporting everything okay. Anyways, in a last > ditch attempt to improve my situation, I ended up destroying my xorg, so I > had to recompile (I use gentoo and didn't have a bin package). I upgraded to > xorg 6.8.2, the latest gentoo stable, while I was at it. And magically: it > worked, even though my frame rate in glxgears is only up to 750. I'm now > where I remember being a few years ago, which is great. San Fran looks > beautiful (much better than before!). Now I'm going to try to tweak to > improve my fps > > Thanks again, > Wes > > Happy for you. About FPS in glinfo it depends on the windows size . Glxgear has never been more than 300 fps with a very big window and 32 bits > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Strange acceleration issues with 9.8---possibly terrain related?
Wow, thanks for all the replies! So, in any case... direct rendering was indeed working, it glinfo reporting everything okay. Anyways, in a last ditch attempt to improve my situation, I ended up destroying my xorg, so I had to recompile (I use gentoo and didn't have a bin package). I upgraded to xorg 6.8.2, the latest gentoo stable, while I was at it. And magically: it worked, even though my frame rate in glxgears is only up to 750. I'm now where I remember being a few years ago, which is great. San Fran looks beautiful (much better than before!). Now I'm going to try to tweak to improve my fps Thanks again, Wes On Tue, May 24, 2005 at 11:18:30PM +0200, Arnt Karlsen wrote: > On Tue, 24 May 2005 13:17:43 -0500, Wesley wrote in message > <[EMAIL PROTECTED]>: > > > Hi all, > > I have Gentoo Linux 2.6.9 running on a 1 GHz Pentium III, with an ATI > > Radeon Mobility M6 card. > > ..and lspci calls it a what??? > > > 1 or 2 years ago, I remember having > > FlightGear working properly. Now, I have no success, and someone on > > the IRC channel recommend I forward my issues to this list. > > > > First, the good news. If I delete all the terrain files, FlightGear > > starts, and runs with very acceptable framerates---although I'm just > > in the middle of a giant ocean. > > > > The bad news, is that with terrain files, it either doesn't start at > > all, or starts with frame rates on the order of 1 per every 10 > > seconds. > > ..you wanna see at least 10 fps, with everything turned on, I got 1-5 > off an 128bit 128MB 9250 clone on an Epox MVP3G2 with an AMD > K6-2 450MHz w 384MB ram. > > > When it doesn't start, it's killed by the kernel for exhausting all of > > my 500MB of ram and 1GB of swap (ouch!). I've tried running it with > > everything disabled I could think of: specular highlighting, textures, > > enhanced lighting, etc. etc.. It would still either fail to start, or > > start and be unusably slow. > > > > glxgears gives me 700fps (as good as it's ever given me), and I have > > ..run glxinfo??? You want something like:" > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: SGI > server glx version string: 1.2 > server glx extensions: " etc > > > xorg 6.8, and the xorg ati drivers (the ati drivers don't support my > > card). > > .._which_ ati drivers??? > > ..Debian Sid's XFree86-4.3.0.dfsg.1-13 looks like it can do X.org > vintage tricks, judging by my /var/log/XFree86.0.log : > (II) ATI: ATI driver (version 6.5.5) for chipsets: ati, ativga > (II) R128: Driver for ATI Rage 128 chipsets: > ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF > (AGP),ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility > M4 ML (AGP),ATI Rage 128 Pro GL PA (AGP?), ATI Rage 128 Pro GL > PB (AGP?),ATI Rage 128 Pro GL PC (AGP?), ATI Rage 128 Pro GL PD > (PCI),ATI Rage 128 Pro GL PE (AGP?), ATI Rage 128 Pro GL PF > (AGP),ATI Rage 128 Pro VR PG (AGP?), ATI Rage 128 Pro VR PH > (AGP?),ATI Rage 128 Pro VR PI (AGP?), ATI Rage 128 Pro VR PJ > (AGP?),ATI Rage 128 Pro VR PK (AGP?), ATI Rage 128 Pro VR PL > (AGP?),ATI Rage 128 Pro VR PM (AGP?), ATI Rage 128 Pro VR PN > (AGP?),ATI Rage 128 Pro VR PO (AGP?), ATI Rage 128 Pro VR PP > (PCI),ATI Rage 128 Pro VR PQ (AGP?), ATI Rage 128 Pro VR PR > (PCI),ATI Rage 128 Pro VR PS (AGP?), ATI Rage 128 Pro VR PT > (AGP?),ATI Rage 128 Pro VR PU (AGP?), ATI Rage 128 Pro VR PV > (AGP?),ATI Rage 128 Pro VR PW (AGP?), ATI Rage 128 Pro VR PX > (AGP?),ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP), > ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI), > ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (AGP?), > ATI Rage 128 4X SF (AGP?), ATI Rage 128 4X SG (AGP?), > ATI Rage 128 4X SH (AGP?), ATI Rage 128 4X SK (AGP?), > ATI Rage 128 4X SL (AGP?), ATI Rage 128 4X SM (AGP), > ATI Rage 128 4X SN (AGP?), ATI Rage 128 Pro ULTRA TF (AGP), > ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR > (AGP),ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA > TT (AGP?),ATI Rage 128 Pro ULTRA TU (AGP?) > (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), > ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), > ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ > (AGP/PCI),ATI Radeon Mobility M7 LW (AGP), > ATI Mobility FireGL 7800 M7 LX (AGP), > ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ > (AGP),ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336, > ATI Radeon IGP330/340/350 (A4) 4137, > ATI Radeon IGP330M/340M/350M (U2) 4337, > ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP > 4437,ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP), > ATI Radeon 9100 QM (AGP), ATI
Re: [Flightgear-devel] Strange acceleration issues with 9.8---possibly terrain related?
Oops, sorry. Will do next time. Thanks again, Wes On Tue, May 24, 2005 at 08:06:59PM +, [EMAIL PROTECTED] wrote: > > Hi. Just as a request, you might wanna set a line length of <80 chars > or so (74 is good). Your lines are coming across many lines long, thus > difficult to read on some clients and through web interfaces (like the > one I'm currently stuck using, unfortunately). > > > The bad news, is that with terrain files, it either doesn't start > > at all, or starts with frame rates on the order of 1 per every 10 > > seconds. > > > > When it doesn't start, it's killed by the kernel for exhausting all > > of my 500MB of ram and 1GB of swap (ouch!). I've tried running it > > with everything disabled I could think of: specular highlighting, > > textures, enhanced lighting, etc. etc.. It would still either fail > > to start, or start and be unusably slow. > > Can you be more specific? What command are you using to start up > fgfs, and what are the contents of your .fgfsrc? > > Previous times that stuff like this has happened, it's been because > people have set absurdly high values for things like visibility > in their .fgfsrc. > > Thanks, > > -c > > > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Strange acceleration issues with 9.8---possibly
Selon Martin Spott <[EMAIL PROTECTED]>: > Wesley Alden Pegden wrote: > > > glxgears gives me 700fps (as good as it's ever given me), [...] > > With a working OpenGL/DRI setup you typically get far more than 1000 > fps with 'glxgears'. Please run 'glxinfo' or 'gl-info' - whatever you > have on your machine - and have a closer look at the OpenGL 'vendor', And there must be : direct rendering : yes -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Strange acceleration issues with 9.8---possibly terrain related?
On Tue, 24 May 2005 13:17:43 -0500, Wesley wrote in message <[EMAIL PROTECTED]>: > Hi all, > I have Gentoo Linux 2.6.9 running on a 1 GHz Pentium III, with an ATI > Radeon Mobility M6 card. ..and lspci calls it a what??? > 1 or 2 years ago, I remember having > FlightGear working properly. Now, I have no success, and someone on > the IRC channel recommend I forward my issues to this list. > > First, the good news. If I delete all the terrain files, FlightGear > starts, and runs with very acceptable framerates---although I'm just > in the middle of a giant ocean. > > The bad news, is that with terrain files, it either doesn't start at > all, or starts with frame rates on the order of 1 per every 10 > seconds. ..you wanna see at least 10 fps, with everything turned on, I got 1-5 off an 128bit 128MB 9250 clone on an Epox MVP3G2 with an AMD K6-2 450MHz w 384MB ram. > When it doesn't start, it's killed by the kernel for exhausting all of > my 500MB of ram and 1GB of swap (ouch!). I've tried running it with > everything disabled I could think of: specular highlighting, textures, > enhanced lighting, etc. etc.. It would still either fail to start, or > start and be unusably slow. > > glxgears gives me 700fps (as good as it's ever given me), and I have ..run glxinfo??? You want something like:" name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: " etc > xorg 6.8, and the xorg ati drivers (the ati drivers don't support my > card). .._which_ ati drivers??? ..Debian Sid's XFree86-4.3.0.dfsg.1-13 looks like it can do X.org vintage tricks, judging by my /var/log/XFree86.0.log : (II) ATI: ATI driver (version 6.5.5) for chipsets: ati, ativga (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP),ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP),ATI Rage 128 Pro GL PA (AGP?), ATI Rage 128 Pro GL PB (AGP?),ATI Rage 128 Pro GL PC (AGP?), ATI Rage 128 Pro GL PD (PCI),ATI Rage 128 Pro GL PE (AGP?), ATI Rage 128 Pro GL PF (AGP),ATI Rage 128 Pro VR PG (AGP?), ATI Rage 128 Pro VR PH (AGP?),ATI Rage 128 Pro VR PI (AGP?), ATI Rage 128 Pro VR PJ (AGP?),ATI Rage 128 Pro VR PK (AGP?), ATI Rage 128 Pro VR PL (AGP?),ATI Rage 128 Pro VR PM (AGP?), ATI Rage 128 Pro VR PN (AGP?),ATI Rage 128 Pro VR PO (AGP?), ATI Rage 128 Pro VR PP (PCI),ATI Rage 128 Pro VR PQ (AGP?), ATI Rage 128 Pro VR PR (PCI),ATI Rage 128 Pro VR PS (AGP?), ATI Rage 128 Pro VR PT (AGP?),ATI Rage 128 Pro VR PU (AGP?), ATI Rage 128 Pro VR PV (AGP?),ATI Rage 128 Pro VR PW (AGP?), ATI Rage 128 Pro VR PX (AGP?),ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI), ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (AGP?), ATI Rage 128 4X SF (AGP?), ATI Rage 128 4X SG (AGP?), ATI Rage 128 4X SH (AGP?), ATI Rage 128 4X SK (AGP?), ATI Rage 128 4X SL (AGP?), ATI Rage 128 4X SM (AGP), ATI Rage 128 4X SN (AGP?), ATI Rage 128 Pro ULTRA TF (AGP), ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP),ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?),ATI Rage 128 Pro ULTRA TU (AGP?) (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI),ATI Radeon Mobility M7 LW (AGP), ATI Mobility FireGL 7800 M7 LX (AGP), ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon IGP330M/340M/350M (U2) 4337, ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP 4437,ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP), ATI Radeon 9100 QM (AGP), ATI Radeon 8500 AIW BB (AGP), ATI Radeon 8500 AIW BC (AGP), ATI Radeon 7500 QW (AGP/PCI), ATI Radeon 7500 QX (AGP/PCI), ATI Radeon 9000/PRO If (AGP/PCI), ATI Radeon 9000 Ig (AGP/PCI), ATI FireGL Mobility 9000 (M9) Ld (AGP),ATI Radeon Mobility 9000 (M9) Lf (AGP), ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9100 IGP (A5) 5834, ATI Radeon Mobility 9100 IGP (U3) 5835, ATI Radeon 9200PRO 5960 (AGP), ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP), ATI Radeon 9200SE 5964 (AGP), ATI Radeon Mobility 9200 (M9+) 5C61 (AGP), ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Radeon 9500 AD (AGP),ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP), ATI FireGL Z1 AG (AGP), ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AG
Re: [Flightgear-devel] Strange acceleration issues with 9.8---possibly
Wesley Alden Pegden wrote: > glxgears gives me 700fps (as good as it's ever given me), [...] With a working OpenGL/DRI setup you typically get far more than 1000 fps with 'glxgears'. Please run 'glxinfo' or 'gl-info' - whatever you have on your machine - and have a closer look at the OpenGL 'vendor', Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Strange acceleration issues with 9.8---possibly terrain related?
Le mardi 24 mai 2005 à 13:17 -0500, Wesley Alden Pegden a écrit : > Hi all, > I have Gentoo Linux 2.6.9 running on a 1 GHz Pentium III, with an ATI Radeon > Mobility M6 card. 1 or 2 years ago, I remember having FlightGear working > properly. Now, I have no success, and someone on the IRC channel recommend I > forward my issues to this list. > > First, the good news. If I delete all the terrain files, FlightGear starts, > and runs with very acceptable framerates---although I'm just in the middle of > a giant ocean. > > The bad news, is that with terrain files, it either doesn't start at all, or > starts with frame rates on the order of 1 per every 10 seconds. > > When it doesn't start, it's killed by the kernel for exhausting all of my > 500MB of ram and 1GB of swap (ouch!). I've tried running it with everything > disabled I could think of: specular highlighting, textures, enhanced > lighting, etc. etc.. It would still either fail to start, or start and be > unusably slow. > > glxgears gives me 700fps (as good as it's ever given me), and I have xorg > 6.8, and the xorg ati drivers (the ati drivers don't support my card). > > I've tried lots of places without complicated terrain (i.e., not just san > fran). > > Thanks very much for any help! I long to be in the FlightGear skies once > more... > > > -Wes > Are you sure, you have opengl implemented/ may be you are using mesa GL. > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] mirror ftps
Le mardi 24 mai 2005 à 10:37 -0700, can kalkan a écrit : > when i was looking on some mirror ftps to find older sources i > ve found an f-18 aircraft. first i thought it was only flight > dynamics experience but it is a full animated 3d model with > accurate looking jsbsim dynamics. (based on nasa > documentery. ) i want to know why FG.ORG website did not put > this aircraft on the web. are there an other suprises hiding > in mirror ftps > > > __ I agree with you, that F18 is a "jewel". By the way, have you paid attention to the patch which come whis it You can land on the Nimitz and take off. (launchbar and hook) I do use the JBSim patch these new functionalities are NOT yet included in the cvs version. Let's be patient. -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Strange acceleration issues with 9.8---possibly terrain related?
Hi. Just as a request, you might wanna set a line length of <80 chars or so (74 is good). Your lines are coming across many lines long, thus difficult to read on some clients and through web interfaces (like the one I'm currently stuck using, unfortunately). > The bad news, is that with terrain files, it either doesn't start > at all, or starts with frame rates on the order of 1 per every 10 > seconds. > > When it doesn't start, it's killed by the kernel for exhausting all > of my 500MB of ram and 1GB of swap (ouch!). I've tried running it > with everything disabled I could think of: specular highlighting, > textures, enhanced lighting, etc. etc.. It would still either fail > to start, or start and be unusably slow. Can you be more specific? What command are you using to start up fgfs, and what are the contents of your .fgfsrc? Previous times that stuff like this has happened, it's been because people have set absurdly high values for things like visibility in their .fgfsrc. Thanks, -c ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew a écrit : Correction, that was pthreadVC-nd.dll As I said, you must install fgsetup-0.9.8a.exe before, and replace fgfs.exe -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Success! I just commented out the call to fgAirportDBLoad as well, and now it starts up in less than 20 seconds, which is perfect. It seems to run more smoothly as well having freed up so much memory, but I can't confirm that. KSFO still seems to be there, visually, and all I need from flightgear are the visual model and terrain elevations. Am I losing anything important by bypassing this? Is the airport data simply marker beacon and ILS information? Drew On 5/24/05, Drew <[EMAIL PROTECTED]> wrote: > That's helpful...thanks. I just commented the call to FGNavDBInit, > which shaved off about 10 seconds, so that's some good progress...I'll > play with it some more to see what I can do. > > Thanks for all your help. > > On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > > Frederic Bouvier a écrit : > > > > > It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > > > > > > 9 seconds to load airports and nav data, > > 5 seconds to init other subsystems, > > 9 seconds to load scenery objects. > > > > -Fred > > > > > > > > ___ > > Flightgear-devel mailing list > > Flightgear-devel@flightgear.org > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > 2f585eeea02e2c79d7b1d8c4963bae2d > > > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Correction, that was pthreadVC-nd.dll On 5/24/05, Drew <[EMAIL PROTECTED]> wrote: > I will, probably tonight...I tried it really quickly, and it needs a > C-nd.dll. I suspect there are similar issues, so I'll work through it > when I've got some more time. > > Thanks again, > Drew > > On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > > Drew a écrit : > > > > >Really? That's helpful. I wasn't able to get the CVS software to > > >work last time I tried...it seems like that's a useful feature, so I > > >think I'll try again. > > > > > > > > Get a taste of it by downloading the binary I posted earlier. > > > > -Fred > > > > > > > > ___ > > Flightgear-devel mailing list > > Flightgear-devel@flightgear.org > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > 2f585eeea02e2c79d7b1d8c4963bae2d > > > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] HTTPD PROBLEM
hi all i am running fg in jsbsim under xp . i connected via httpd but some variable changes have some problems. i tried to change the air speed and altitute in flight in real time sim and in pause. but both didn't work. the fg went crazy i found myself on the ground in seconds. anybody knows why these happens to me? _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
I will, probably tonight...I tried it really quickly, and it needs a C-nd.dll. I suspect there are similar issues, so I'll work through it when I've got some more time. Thanks again, Drew On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Drew a écrit : > > >Really? That's helpful. I wasn't able to get the CVS software to > >work last time I tried...it seems like that's a useful feature, so I > >think I'll try again. > > > > > Get a taste of it by downloading the binary I posted earlier. > > -Fred > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew a écrit : Really? That's helpful. I wasn't able to get the CVS software to work last time I tried...it seems like that's a useful feature, so I think I'll try again. Get a taste of it by downloading the binary I posted earlier. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: mirror ftps
* can kalkan -- Tuesday 24 May 2005 19:37: > when i was looking on some mirror ftps to find older sources i ve found an > f-18 aircraft. first i thought it was only flight dynamics experience but > it is a full animated 3d model with accurate looking jsbsim dynamics. > (based on nasa documentery. ) Do you mean this here? ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/carrier/FA-18.tar.bz2 http://members.aon.at/mfranz/fa18a.jpg [45 kB] (screenshot) That's Mathias' work ... mostly. It's a great aircraft. Flies very well and is ideal for carrier landings. One of my favorites! http://members.aon.at/mfranz/fa18a.jpeg [78 kB] (screenshot) > i want to know why FG.ORG website did not put this aircraft on the web. Because it's not (yet) GPL compatible and, thus, must not get re-distributed. Mathias has done most of it anyway and is about to replace the last traces of the borrowed original work from anonymous. I guess and hope it'll will be available on the fgfs homepage, or even in cvs. > are there an other suprises hiding in mirror ftps No. :-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Strange acceleration issues with 9.8---possibly terrain related?
Hi all, I have Gentoo Linux 2.6.9 running on a 1 GHz Pentium III, with an ATI Radeon Mobility M6 card. 1 or 2 years ago, I remember having FlightGear working properly. Now, I have no success, and someone on the IRC channel recommend I forward my issues to this list. First, the good news. If I delete all the terrain files, FlightGear starts, and runs with very acceptable framerates---although I'm just in the middle of a giant ocean. The bad news, is that with terrain files, it either doesn't start at all, or starts with frame rates on the order of 1 per every 10 seconds. When it doesn't start, it's killed by the kernel for exhausting all of my 500MB of ram and 1GB of swap (ouch!). I've tried running it with everything disabled I could think of: specular highlighting, textures, enhanced lighting, etc. etc.. It would still either fail to start, or start and be unusably slow. glxgears gives me 700fps (as good as it's ever given me), and I have xorg 6.8, and the xorg ati drivers (the ati drivers don't support my card). I've tried lots of places without complicated terrain (i.e., not just san fran). Thanks very much for any help! I long to be in the FlightGear skies once more... -Wes ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Really? That's helpful. I wasn't able to get the CVS software to work last time I tried...it seems like that's a useful feature, so I think I'll try again. Drew On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Do you compile the last code ? > Now the splash screen writes the current stage on screen and it is > easier to know where time is spent. > > -Fred > > Drew a écrit : > > >That's helpful...thanks. I just commented the call to FGNavDBInit, > >which shaved off about 10 seconds, so that's some good progress...I'll > >play with it some more to see what I can do. > > > >Thanks for all your help. > > > >On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > > > > > >>Frederic Bouvier a écrit : > >> > >> > >> > >>>It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > >>> > >>> > >>9 seconds to load airports and nav data, > >>5 seconds to init other subsystems, > >>9 seconds to load scenery objects. > >> > >>-Fred > >> > >> > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] mirror ftps
when i was looking on some mirror ftps to find older sources i ve found an f-18 aircraft. first i thought it was only flight dynamics experience but it is a full animated 3d model with accurate looking jsbsim dynamics. (based on nasa documentery. ) i want to know why FG.ORG website did not put this aircraft on the web. are there an other suprises hiding in mirror ftps Do you Yahoo!? Make Yahoo! your home page ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Do you compile the last code ? Now the splash screen writes the current stage on screen and it is easier to know where time is spent. -Fred Drew a écrit : That's helpful...thanks. I just commented the call to FGNavDBInit, which shaved off about 10 seconds, so that's some good progress...I'll play with it some more to see what I can do. Thanks for all your help. On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: Frederic Bouvier a écrit : It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. 9 seconds to load airports and nav data, 5 seconds to init other subsystems, 9 seconds to load scenery objects. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
That's helpful...thanks. I just commented the call to FGNavDBInit, which shaved off about 10 seconds, so that's some good progress...I'll play with it some more to see what I can do. Thanks for all your help. On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Frederic Bouvier a écrit : > > > It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > > > 9 seconds to load airports and nav data, > 5 seconds to init other subsystems, > 9 seconds to load scenery objects. > > -Fred > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew, The question was intended to the other Linux adopters, not you specifically. -Fred Drew a écrit : I don't know. I can't try it, though, because this is a work computer, and 'm not supposed to install Linux. On 5/24/05, Frederic Bouvier wrote: Drew a écrit : That's probably about right, but your computer is much more capable than mine (Intel Pentium M 1600 MHz laptop, 512 Megs of RAM). I just timed mine at 57 seconds. On 5/24/05, Frederic Bouvier wrote: It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. Is it different under Linux ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Frederic Bouvier wrote: > By popular demand ( sort of ;), I uploaded my current release build ( > latest CVS ) here : Thanks ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Frederic Bouvier a écrit : It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. 9 seconds to load airports and nav data, 5 seconds to init other subsystems, 9 seconds to load scenery objects. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
I don't know. I can't try it, though, because this is a work computer, and 'm not supposed to install Linux. On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Drew a écrit : > > >That's probably about right, but your computer is much more capable > >than mine (Intel Pentium M 1600 MHz laptop, 512 Megs of RAM). I just > >timed mine at 57 seconds. > > > >On 5/24/05, Frederic Bouvier wrote: > > > > > >>It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > >> > >> > > Is it different under Linux ? > > -Fred > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew a écrit : That's probably about right, but your computer is much more capable than mine (Intel Pentium M 1600 MHz laptop, 512 Megs of RAM). I just timed mine at 57 seconds. On 5/24/05, Frederic Bouvier wrote: It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. Is it different under Linux ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Martin Spott wrote : In article <[EMAIL PROTECTED]> you wrote: The Release build, as in the official win32 releases, is way faster. Maybe 5x to 10x. BTW, Frederic, would you consider uploading a Win32 binary - to the 'well-known site' - that represents the current stae of development ? By popular demand ( sort of ;), I uploaded my current release build ( latest CVS ) here : ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/fgfs-win32-20050524.zip It goes on top of a valid install, as it requires some dlls not provided here, after the usual backup, of course. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
That's probably about right, but your computer is much more capable than mine (Intel Pentium M 1600 MHz laptop, 512 Megs of RAM). I just timed mine at 57 seconds. On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > > -Fred > > Drew a écrit : > > >I'm compiling a Release build. It takes me a bit under a minute to > >bring it up, which isn't as bad as the 5 minutes Vivian reported, but > >it's still longer than I'd like (and longer than I believe is > >necessary). I'll see what I can do about disabling navaids...that > >seems like it be a lot of help. I haven't found a property in > >preferences.xml or a command-line option for this, yet. > > > >Drew > > > >On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > > > > > >>Drew a écrit : > >> > >> > >> > >>>FlightGear takes nearly a minute to start up from my Windows build, > >>>and I'm just wondering if there's an easy way to shorten this if I'm > >>>not using all of flightgear's features. Is there one particular task > >>>that takes particularly long? > >>> > >>> > >>> > >>> > >>Do you use the Debug or the Release build ? > >>MSVC 7.x adds a lot of debug code in memory management (assertion check, > >>corrupted heap) that makes the Debug build **very** slow. > >>The Release build, as in the official win32 releases, is way faster. > >>Maybe 5x to 10x. > >> > >>-Fred > >> > >> > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. -Fred Drew a écrit : I'm compiling a Release build. It takes me a bit under a minute to bring it up, which isn't as bad as the 5 minutes Vivian reported, but it's still longer than I'd like (and longer than I believe is necessary). I'll see what I can do about disabling navaids...that seems like it be a lot of help. I haven't found a property in preferences.xml or a command-line option for this, yet. Drew On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: Drew a écrit : FlightGear takes nearly a minute to start up from my Windows build, and I'm just wondering if there's an easy way to shorten this if I'm not using all of flightgear's features. Is there one particular task that takes particularly long? Do you use the Debug or the Release build ? MSVC 7.x adds a lot of debug code in memory management (assertion check, corrupted heap) that makes the Debug build **very** slow. The Release build, as in the official win32 releases, is way faster. Maybe 5x to 10x. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Harald JOHNSEN wrote: I've just looked at the code. I see that the error count is incremented in the catch but I think I don't enter here, I am spamed with 'metar data too old' on the console. After some time I have a real socket error and I think that after that I enter the catch statement and the error counter is finaly incremented ! Strange that the increment is inside the #ifdef threads. So to be clear : 1) I have a lot of 'metar too old' message (no log file but its more than 50 per loop) 2) after some time I have a sigio (if I remember well, that does not happens everyday of course) 3) repeat 3 times Its with cvs version and that happens in the init code. I see, the problem is basically introduced again after adding code to see whether the data is too old. This probably requires another error counter ... Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
I'm compiling a Release build. It takes me a bit under a minute to bring it up, which isn't as bad as the 5 minutes Vivian reported, but it's still longer than I'd like (and longer than I believe is necessary). I'll see what I can do about disabling navaids...that seems like it be a lot of help. I haven't found a property in preferences.xml or a command-line option for this, yet. Drew On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Drew a écrit : > > >FlightGear takes nearly a minute to start up from my Windows build, > >and I'm just wondering if there's an easy way to shorten this if I'm > >not using all of flightgear's features. Is there one particular task > >that takes particularly long? > > > > > > Do you use the Debug or the Release build ? > MSVC 7.x adds a lot of debug code in memory management (assertion check, > corrupted heap) that makes the Debug build **very** slow. > The Release build, as in the official win32 releases, is way faster. > Maybe 5x to 10x. > > -Fred > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear startup time
Durk Talsma wrote: Maybe this is a good time time to formulate a though I've had for some time now: With rumours of a possible 1.0.0 version sometime in 2005, I don't think it's a good time to start digging into the basic architecture of FlightGear. However, once version 1.0 is out, wouldn't that be an excellent opportunity to carefully scrutinize the core architecture of FlightGear and redesign it with the goal of ruducing interdependencies, memory requirements, and improving startup time? I've been working on this regularly the in the past. It's not easy and I doubt it will gain much. However, I think the current airport reading code is just a mixture of code from the past adopted to read the new data. So it could be the code currently is reading one file more than once ... Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew a écrit : FlightGear takes nearly a minute to start up from my Windows build, and I'm just wondering if there's an easy way to shorten this if I'm not using all of flightgear's features. Is there one particular task that takes particularly long? Do you use the Debug or the Release build ? MSVC 7.x adds a lot of debug code in memory management (assertion check, corrupted heap) that makes the Debug build **very** slow. The Release build, as in the official win32 releases, is way faster. Maybe 5x to 10x. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear startup time
Le mardi 24 mai 2005 à 17:42 +0200, Durk Talsma a écrit : > On Tuesday 24 May 2005 13:45, Melchior FRANZ wrote: > > > > (1) loading airport and navigation data; very rough guess: ~ 45% > > (2) initializing subsystems (atc, weather, ai, ...) ~ 30% > > (3) creating MipMaps (no perceived delay, because it's done in another > > thread) > > > > Maybe this is a good time time to formulate a though I've had for some time > now: With rumours of a possible 1.0.0 version sometime in 2005, I don't think > it's a good time to start digging into the basic architecture of FlightGear. > However, once version 1.0 is out, wouldn't that be an excellent opportunity > to carefully scrutinize the core architecture of FlightGear and redesign it > with the goal of ruducing interdependencies, memory requirements, and > improving startup time? > > Any thoughts/comments? > > Cheers, > Durk > > may be i am the only one to be satisfied with startup time: less than 50 secondes: -->metar -->geometry 1280*896 ->nmea socket (atlas) -->ai (carrier Nimitz in Mediterranean sea) -->High detailed and textured aircraft (3 Mb) with 3D panel/instruments in addition to every default -->fgfs parameters The main difficulties are rather coming from the tiles loading during flight. Which could be tuned. If possible. fgfs running with Linux 2.6.11 > > Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear startup time
Drew wrote: > Believe me, guys, if I could use Linux for this application, I > would...I am much more familiar with developing in Linux than Windows. > Unfortunately, that isn't an option for me in this case. Well, I wouldn't use Windows either and I actually don't. But I installed the latest release binary of FG on my life-mates/girl-friends PeeCee and I acknowledge that it works excellent. The main drawback appears to lie in different environments that try to emulate Unix features. The MSVC binary instead does a great job, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear startup time
On Tuesday 24 May 2005 13:45, Melchior FRANZ wrote: > > (1) loading airport and navigation data; very rough guess: ~ 45% > (2) initializing subsystems (atc, weather, ai, ...) ~ 30% > (3) creating MipMaps (no perceived delay, because it's done in another > thread) > Maybe this is a good time time to formulate a though I've had for some time now: With rumours of a possible 1.0.0 version sometime in 2005, I don't think it's a good time to start digging into the basic architecture of FlightGear. However, once version 1.0 is out, wouldn't that be an excellent opportunity to carefully scrutinize the core architecture of FlightGear and redesign it with the goal of ruducing interdependencies, memory requirements, and improving startup time? Any thoughts/comments? Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] for help
Citeren yue xianf <[EMAIL PROTECTED]>: > Hi all: > > anyone can give me some hint how can I get the data out of > flightgear, I am > interested in > the data speed in 3D and latitude, longtitude, altitude. I am working > in > windows 2000, Which > kinds of steps do i need to finish. > > I very appreicate your help > docs-mini/README.IO gives you a description of what is possible. Steven ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Erik Hofman wrote: Harald JOHNSEN wrote: Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. Which version of FlightGear are you using? This has been fixed a long time ago. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d I've just looked at the code. I see that the error count is incremented in the catch but I think I don't enter here, I am spamed with 'metar data too old' on the console. After some time I have a real socket error and I think that after that I enter the catch statement and the error counter is finaly incremented ! Strange that the increment is inside the #ifdef threads. So to be clear : 1) I have a lot of 'metar too old' message (no log file but its more than 50 per loop) 2) after some time I have a sigio (if I remember well, that does not happens everyday of course) 3) repeat 3 times Its with cvs version and that happens in the init code. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
On Tuesday 24 May 2005 16:09, Harald JOHNSEN wrote: > Edit apt.dat and runways.dat, just leave KSFO for example. Normaly you > should leave a few others used in ai or atc (I don't remember) or > disable this functionalities if you don't want an abort of FG. > The latest version of the Traffic manager derived AI is done such that it discards any route that tries to fly to/from an unknown airport. Unfortunately this has to be done at startup, adding to the initialization time. The run-time consequence if you only keep one airport is that you won't see any airliner traffic... Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Le mardi 24 mai 2005 à 16:43 +0200, Erik Hofman a écrit : > Harald JOHNSEN wrote: > > > Another problem not related to pure performance is that the first > > retrieval of metar data can block FG for a long time (perhaps one > > minute) when the metar server is not accessible (or when there is any > > network problem). The code does a lot of (useless) retries. Perhaps its > > simpler not to update the metar on IO error and continue silently. > > Which version of FlightGear are you using? > This has been fixed a long time ago. > On my side I do confirm: Metar is waiting for an answer during startup. I do use permanently Metar , if the network is off, fgfs wait for a lot of time before going on ===> fgfs 9.8 and fgfs cvs > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear startup time
Believe me, guys, if I could use Linux for this application, I would...I am much more familiar with developing in Linux than Windows. Unfortunately, that isn't an option for me in this case. Drew On 5/24/05, Melchior FRANZ <[EMAIL PROTECTED]> wrote: > * Norman Vine -- Tuesday 24 May 2005 14:05: > > I guess I should mention the deficiencies of non MSoft OSs but > > I will leave the *flames* for another time :-) > > Yeah, don't bother. 99% of Windows users don't know alternatives, but 99% of > Linux/Unix users *do* know Windows. Of course, there are deficiencies in Unix > too (hmm ... game support?). But while deciding for Windows is mostly a matter > of ignorance and inertia, deciding for Unix is a matter of reason. ;-) > > m. > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Hi Erik: The version is v0.9.8 for windows. Clifford From: Erik Hofman <[EMAIL PROTECTED]> Reply-To: FlightGear developers discussions To: FlightGear developers discussions Subject: Re: [Flightgear-devel] FlightGear startup time Date: Tue, 24 May 2005 16:43:32 +0200 Harald JOHNSEN wrote: Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. Which version of FlightGear are you using? This has been fixed a long time ago. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Harald JOHNSEN wrote: Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. Which version of FlightGear are you using? This has been fixed a long time ago. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] for help
Hi all: anyone can give me some hint how can I get the data out of flightgear, I am interested in the data speed in 3D and latitude, longtitude, altitude. I am working in windows 2000, Which kinds of steps do i need to finish. I very appreicate your help _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Questions about IO system
Steven Beeckman wrote: Hi Mike, there's an example in the scripts folder (or utils folder) of the sourcecode (I think) on how to interface in Java. I haven't used it yet due to lack of time :(. Greets, Steven Citeren Mike Kopack <[EMAIL PROTECTED]>: Hey gang, I'm trying to write some Java code to interface with FlightGear's IO system via sockets. I'm running on Windows (don't know if that matters or not.) Anyhow, I need to do two things: 1) Have one socket sending flight commands (like changing the rudder position, or turning on/off the autopilot, setting throttle, etc.) These can come in at any time. 2) Have another socket that my code listens for periodic updates in status information from FlightGear (position, attitude, engine temp, fuel flow rates, etc.) From what I see in the documentation, it shows that you can do this. I'm a bit confused by it though. To do task #1 above, do I just open a socket to Flightgear on the specified port, then send a XML doc with just the 1 command element I want to specify? To do task #2 above, as I understand it, I have to set up a XML file on the machine running FG that basically tells FG what data I want sent back over the socket. Does it come across the wire as an XML doc every x.x seconds (I see that there's a Hz setting when specifying the socket connection in FG), or does it come across as comma delimited or something like that? Any help with this is greatly appreciated. Thanks! --Mike Mike Kopack ISX Corporation 1800 Parkway Place Suite 900 Marietta, GA 30067 678-581-2025 [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d You don't need XML, all you want to do is read and write the property tree. As Steven said, check FGFSConnection.java in the scripts subdir for access via props/telnet protocol. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew wrote: FlightGear takes nearly a minute to start up from my Windows build, and I'm just wondering if there's an easy way to shorten this if I'm not using all of flightgear's features. Is there one particular task that takes particularly long? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew wrote: Interesting...I have no use for navaid data. Is there an option to turn these off? And as far as airports go, I only care about the imagery. Any other info, I can do without. Hmmm, that would probably free up a lot of memory too, huh? I'll look into limiting the region of airports it loads. I find it odd that it takes 5 minutes for you...I'm by no means running it on a top-of-the-line gaming machine...a Centrino laptop 1600 MHz with 256 Megs of RAM and a Mobility Radeon 9000 graphics card. Edit apt.dat and runways.dat, just leave KSFO for example. Normaly you should leave a few others used in ai or atc (I don't remember) or disable this functionalities if you don't want an abort of FG. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: AC3D format and material settings
* Ben Morrison -- Tuesday 24 May 2005 15:47: > On flightgear's console it gives me a warning: Can't parse this material. What about posting that broken line? This is a developers' list, remember? > I read in a past discussion this may be because of the specular > component of the material. The components must be in strict order MATERIAL "foo" rgb 0 0 0 amb 0 0 0 emis 0 0 0 spec 0 0 0 shi 0 trans 0 the material name *must* be quoted (which is a bug in plib's loader -- the AC3D spec AFAIK only requires that for names containing spaces!) > The other problem I am having is once I export the model to AC3D from blender > it will give me an error when I try to import it back in. "an error" is what? An error message? Which? (This is a developers' list!) Or is it only imported in wrong orientation? This is a bug in the importer, that is fixed in recent versions. > Does anyone have a solution for this? Depends on the problem, which you didn't really tell us. :-P m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Questions about IO system
Hi Mike, there's an example in the scripts folder (or utils folder) of the sourcecode (I think) on how to interface in Java. I haven't used it yet due to lack of time :(. Greets, Steven Citeren Mike Kopack <[EMAIL PROTECTED]>: > Hey gang, > > I'm trying to write some Java code to interface with FlightGear's IO > system > via sockets. I'm running on Windows (don't know if that matters or > not.) > Anyhow, I need to do two things: > > 1) Have one socket sending flight commands (like changing the rudder > position, or turning on/off the autopilot, setting throttle, etc.) > These can > come in at any time. > > 2) Have another socket that my code listens for periodic updates in > status > information from FlightGear (position, attitude, engine temp, fuel > flow > rates, etc.) > > >From what I see in the documentation, it shows that you can do this. > I'm a > bit confused by it though. > > To do task #1 above, do I just open a socket to Flightgear on the > specified > port, then send a XML doc with just the 1 command element I want to > specify? > > To do task #2 above, as I understand it, I have to set up a XML file > on the > machine running FG that basically tells FG what data I want sent back > over > the socket. Does it come across the wire as an XML doc every x.x > seconds (I > see that there's a Hz setting when specifying the socket connection > in FG), > or does it come across as comma delimited or something like that? > > Any help with this is greatly appreciated. > > Thanks! > > --Mike > > Mike Kopack > ISX Corporation > 1800 Parkway Place Suite 900 > Marietta, GA 30067 > 678-581-2025 > [EMAIL PROTECTED] > > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] AC3D format and material settings
I am having problems with materials not being rendered on my model in AC3D's format. On flightgear's console it gives me a warning: Can't parse this material. I read in a past discussion this may be because of the specular component of the material. The other problem I am having is once I export the model to AC3D from blender it will give me an error when I try to import it back in. Does anyone have a solution for this? Thanks, Ben ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Questions about IO system
Hey gang, I'm trying to write some Java code to interface with FlightGear's IO system via sockets. I'm running on Windows (don't know if that matters or not.) Anyhow, I need to do two things: 1) Have one socket sending flight commands (like changing the rudder position, or turning on/off the autopilot, setting throttle, etc.) These can come in at any time. 2) Have another socket that my code listens for periodic updates in status information from FlightGear (position, attitude, engine temp, fuel flow rates, etc.) >From what I see in the documentation, it shows that you can do this. I'm a bit confused by it though. To do task #1 above, do I just open a socket to Flightgear on the specified port, then send a XML doc with just the 1 command element I want to specify? To do task #2 above, as I understand it, I have to set up a XML file on the machine running FG that basically tells FG what data I want sent back over the socket. Does it come across the wire as an XML doc every x.x seconds (I see that there's a Hz setting when specifying the socket connection in FG), or does it come across as comma delimited or something like that? Any help with this is greatly appreciated. Thanks! --Mike Mike Kopack ISX Corporation 1800 Parkway Place Suite 900 Marietta, GA 30067 678-581-2025 [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear startup time
On Tue, 24 May 2005 14:26:17 +0200, Melchior wrote in message <[EMAIL PROTECTED]>: > * Norman Vine -- Tuesday 24 May 2005 14:05: > > I guess I should mention the deficiencies of non MSoft OSs but > > I will leave the *flames* for another time :-) > > Yeah, don't bother. 99% of Windows users don't know alternatives, but > 99% of Linux/Unix users *do* know Windows. Of course, there are > deficiencies in Unix too (hmm ... game support?). But while deciding > for Windows is mostly a matter of ignorance and inertia, ..you forgot viscosity here. ;o) > deciding for Unix is a matter of reason. ;-) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] 3 USB Joysticks CH
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Luuk van > Hal > Sent: 24 May 2005 13:07 > To: flightgear-devel@flightgear.org > Subject: [Flightgear-devel] 3 USB Joysticks CH > > > I'm still using Red Hat 8.0 on kernel 2.4.24 with 3 joysticks from CH > products on a Sweex usb 2.0 hub. > Firstly: Are the joysticks detected properly if you plug just one at a time directly into the PC (no hub)? Then: Do they work with more than one plugged directly into the PC? Then: Does one work on the hub? Lets simplify the configuration to work out where the problem is. Richard This e-mail has been scanned for Bede Scientific Instruments for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear startup time
* Norman Vine -- Tuesday 24 May 2005 14:05: > I guess I should mention the deficiencies of non MSoft OSs but > I will leave the *flames* for another time :-) Yeah, don't bother. 99% of Windows users don't know alternatives, but 99% of Linux/Unix users *do* know Windows. Of course, there are deficiencies in Unix too (hmm ... game support?). But while deciding for Windows is mostly a matter of ignorance and inertia, deciding for Unix is a matter of reason. ;-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] 3 USB Joysticks CH
I'm still using Red Hat 8.0 on kernel 2.4.24 with 3 joysticks from CH products on a Sweex usb 2.0 hub. /usr/src/make xconfig support for usb (usbcore.o) -- Y Preliminary USB device filesystem -- Y EHCI HCD -- Y UHCI alternate driver (JE) -- Y USB full HID support -- Y HID Input layer support -- Y Input core support -- Y Joystick support -- Y lsmod: Module Size Used by rtnet 53768 0 rtai_rtdm 12900 0 [rtnet] rtai_shm 7368 0 (unused) rtai_fifos 17672 0 (unused) rtai_sched_up 48241 0 [rtnet rtai_rtdm] rtai 39616 2 [rtnet rtai_rtdm rtai_shm rtai_fifos rtai_sched_up] 3c59x 29552 1 mousedev 5492 1 dmesg | grep usb: usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb.c: new USB bus registered, assigned bus number 1 usb.c: new USB bus registered, assigned bus number 2 usb.c: new USB bus registered, assigned bus number 3 usb.c: new USB bus registered, assigned bus number 4 usb.c: new USB bus registered, assigned bus number 5 usb.c: registered new driver hid input: USB HID v1.00 Joystick [CH PRODUCTS CH PRO PEDALS USB ] on usb1:3.0 input: USB HID v1.00 Joystick [CH PRODUCTS CH THROTTLE QUADRANT] on usb1:4.0 input: USB HID v1.00 Joystick [CH PRODUCTS CH FLIGHT SIM YOKE USB ] on usb1:5.0 So far so good, I would say ...BUT ...this is the output of js_demo: Joystick test program. ~~ Joystick 0 not detected Joystick 1 not detected Joystick 2 not detected Joystick 3 not detected Joystick 4 not detected Joystick 5 not detected Joystick 6 not detected Joystick 7 not detected I've tried every possible combination of modules concerning usb and joysticks but I can't get any of the USB joysticks to work. Can someone tell me why these joysticks don't work while they are installed correctly. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: FlightGear startup time
> > * Drew -- Tuesday 24 May 2005 07:54: > > FlightGear takes nearly a minute to start up from my Windows build, > > and I'm just wondering if there's an easy way to shorten this if I'm > > not using all of flightgear's features. Is there one particular task > > that takes particularly long? > > Because yesterday was the 200th bithday of the Wiener/Frankfurter/Hot-Dog > sausage, I add my mustard (German saying; does probably not translate well :-) > > I know about the deficiencies of MICROS~1 Windos in general, but not about > CygWin/MinG. The problem is Cygwin emulates Posix streams and this adds significantly to the overhead of stream based ops The XML files require *many* stream ops This addirional overhead is not present in MingW in that it uses native Win32 streams. I guess I should mention the deficiencies of non MSoft OSs but I will leave the *flames* for another time :-) Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear startup time
* Drew -- Tuesday 24 May 2005 07:54: > FlightGear takes nearly a minute to start up from my Windows build, > and I'm just wondering if there's an easy way to shorten this if I'm > not using all of flightgear's features. Is there one particular task > that takes particularly long? Because yesterday was the 200th bithday of the Wiener/Frankfurter/Hot-Dog sausage, I add my mustard (German saying; does probably not translate well :-) I know about the deficiencies of MICROS~1 Windos in general, but not about CygWin/MinG. fgfs starts in about 35 seconds for me on Linux (2.4GHz). Mathias and I did some profiling recently, after I had changed the starting order and added the progress information. The most significant time sinks are (as some pointed out already): (1) loading airport and navigation data; very rough guess: ~ 45% (2) initializing subsystems (atc, weather, ai, ...) ~ 30% (3) creating MipMaps (no perceived delay, because it's done in another thread) To speed things up other than with migrating to a sane system/OS, you could for (1): cut down the databases to a bare minimum (they are just gzipped ASCII files; unpack them, edit them, and AFAIK you don't even need to compress them again; only remove complete chunks) for (2): turn off as many subsystems as possible (/sim/atc/enabled=false, etc.) for (3): use as few textures as possible; You can: - edit material.xml and let it share textures (only one wood texture) or start fgfs in the desert :-) - use aircraft with few and small textures (hint: avoid the MD-11 :-) - scale down textures But all that makes the scenery uglier and is probably not what you want. The gain is probably not worth it, anyway. Finally: if you need to restart fgfs very often, because you are developing something for/with it, you can preload and even pre-relocate it: Just run it in gdb and never leave gdb. The code remains relocated in memory then and start much quicker. I do this regularly. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Interesting...I have no use for navaid data. Is there an option to turn these off? And as far as airports go, I only care about the imagery. Any other info, I can do without. Hmmm, that would probably free up a lot of memory too, huh? I'll look into limiting the region of airports it loads. I find it odd that it takes 5 minutes for you...I'm by no means running it on a top-of-the-line gaming machine...a Centrino laptop 1600 MHz with 256 Megs of RAM and a Mobility Radeon 9000 graphics card. On 5/24/05, Vivian Meazza <[EMAIL PROTECTED]> wrote: > Drew wrote > > > FlightGear takes nearly a minute to start up from my Windows build, > > and I'm just wondering if there's an easy way to shorten this if I'm > > not using all of flightgear's features. Is there one particular task > > that takes particularly long? > > > > Only a minute eh? Under Cygwin cvs takes nearly 5 minutes - time for a brew > a coffee - and that's on a pretty powerful machine. The majority of this > time seems to be taken up by the loading of Airport and Navaid data. As I > understand it, the program loads all that are available without regard for > the location of the aircraft. Keeping this number to a minimum should help. > The other variable under your control is the number of scenery objects, but > this doesn't seem to take all that much tile anyway. > > We really need to sort this one. > > Regards, > > Vivian > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear startup time
Vivian Meazza writes: > > Drew wrote > > > FlightGear takes nearly a minute to start up from my Windows build, > > and I'm just wondering if there's an easy way to shorten this if I'm > > not using all of flightgear's features. Is there one particular task > > that takes particularly long? > > > > Only a minute eh? Under Cygwin cvs takes nearly 5 minutes - time for a brew > a coffee - and that's on a pretty powerful machine. The majority of this > time seems to be taken up by the loading of Airport and Navaid data. As I > understand it, the program loads all that are available without regard for > the location of the aircraft. Keeping this number to a minimum should help. > The other variable under your control is the number of scenery objects, but > this doesn't seem to take all that much tile anyway. > > We really need to sort this one. I adbandoned Cygwin for MingW years ago for just this reason Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
"Vivian Meazza" wrote: > Drew wrote >> FlightGear takes nearly a minute to start up from my Windows build, >> and I'm just wondering if there's an easy way to shorten this if I'm >> not using all of flightgear's features. Is there one particular task >> that takes particularly long? > Only a minute eh? Under Cygwin cvs takes nearly 5 minutes - time for a brew > a coffee - and that's on a pretty powerful machine. At home I run FG on a 400 MHz CPU (on a Unix system), probably not _that_ much compared to your setup. It takes approximately one minute to let FlightGear walk through its initialization - which makes me think that the problem does not lie in FG but in the Cygwin environment instead. On the other hand I would not hold anyone off from optimizing the startup procedure ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear startup time
Drew wrote > FlightGear takes nearly a minute to start up from my Windows build, > and I'm just wondering if there's an easy way to shorten this if I'm > not using all of flightgear's features. Is there one particular task > that takes particularly long? > Only a minute eh? Under Cygwin cvs takes nearly 5 minutes - time for a brew a coffee - and that's on a pretty powerful machine. The majority of this time seems to be taken up by the loading of Airport and Navaid data. As I understand it, the program loads all that are available without regard for the location of the aircraft. Keeping this number to a minimum should help. The other variable under your control is the number of scenery objects, but this doesn't seem to take all that much tile anyway. We really need to sort this one. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
