Re: [Flightgear-devel] slow start-up
David Culp said: > > Try 'hdparm -d /dev/hdxx to check status of drive > > Yep, DMA checks on. I'm sure Curt has the problem figured out. What to do > about it is another issue. Some possible solutions: > > 1) Extend the appearance of the splash screen until all the loading is > finished. > > 2) Put a progress bar in the middle of the screen. > > 3) An hour-glass cursor? > > 4) A message box "Scenery Loading. Stand By..." > I may take a stab at this later in the week. If it is possible to query the tile loading queue then you can have the initialization delay the fdm until the loader is caught up (queue gets emptied). I'm not sure, but I think something like that would work. It'd be good to have this fixed for the release. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] slow start-up
> Try 'hdparm -d /dev/hdxx to check status of drive Yep, DMA checks on. I'm sure Curt has the problem figured out. What to do about it is another issue. Some possible solutions: 1) Extend the appearance of the splash screen until all the loading is finished. 2) Put a progress bar in the middle of the screen. 3) An hour-glass cursor? 4) A message box "Scenery Loading. Stand By..." Dave -- David Culp [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] slow start-up
- Original Message - From: "David Culp" <[EMAIL PROTECTED]> To: "flightgear-devel" <[EMAIL PROTECTED]> Sent: Monday, July 05, 2004 11:46 AM Subject: [Flightgear-devel] slow start-up > This topic was brought up by someone earlier, but I don't think there was any > resolution. When I start up FlightGear, after the "world" first appears on > the screen my frame-rate varies between 1 to 37 or so for about six seconds. > After that the frame-rate settles down to a fairly constant value. > Is there drive activity after the "world" appears? Make sure you have DMA enabled for the driive else you might be losing CPU cycles Try 'hdparm -d /dev/hdxx to check status of drive Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] slow start-up
David Culp wrote: This topic was brought up by someone earlier, but I don't think there was any resolution. When I start up FlightGear, after the "world" first appears on the screen my frame-rate varies between 1 to 37 or so for about six seconds. After that the frame-rate settles down to a fairly constant value. I haven't done a thorough search for the source of this problem. I will try turning off whatever can be turned off, and see if I can make it go away. Right now I'm curious as to how many people are getting this start-up delay. BTW, I'm building with threads enabled. The problem is more than just cosmetic. If I start the sim with throttles forward the FDM (JSBSim) seems to "wind-up" while the sim is stalled (frame-rate near one). When the frame rate bounces back up to near normal the airplane leaps forward (and sometimes upward). The only solution is to sit with throttles idle and watch the frame-rate. When the frame-rate settles down I can take off. Now that the frame-rate is no longer displayed by default I just count to seven and then go. When flying the glider there is no opportunity to wait, so I just have to let the pitch vary wildly until the frame-rate settles down. Anyone else seeing this? This is most likely overhead from loading the 3d models (bldgs/bridges/etc.) for the san fransciso area. Model loading is done in the main render thread because the plib model loaders can trigger texture loading which can trigger opengl calls which is forbidden from happening outside the main render thread. (This could lead into a long discussion about thread safety and threading opengl calls, but the simple answer is don't put opengl calls in multiple threads or you are asking for instant death of your application. If you *know* what you are doing, you could get away with it if you used extreme caution, but if you aren't sure what all the issues are, or are hoping for good luck, then you don't know what you are doing and shouldn't even go there.) :-) Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] slow start-up
On Montag, 5. Juli 2004 20:46, David Culp wrote: [minute's silence] > Anyone else seeing this? Yes. I first thought, that my timestepping code is the reason for that. And I searched and searched :) But it was not ... Seriously, I have no clue where this stems from. Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] slow start-up
This topic was brought up by someone earlier, but I don't think there was any resolution. When I start up FlightGear, after the "world" first appears on the screen my frame-rate varies between 1 to 37 or so for about six seconds. After that the frame-rate settles down to a fairly constant value. I haven't done a thorough search for the source of this problem. I will try turning off whatever can be turned off, and see if I can make it go away. Right now I'm curious as to how many people are getting this start-up delay. BTW, I'm building with threads enabled. The problem is more than just cosmetic. If I start the sim with throttles forward the FDM (JSBSim) seems to "wind-up" while the sim is stalled (frame-rate near one). When the frame rate bounces back up to near normal the airplane leaps forward (and sometimes upward). The only solution is to sit with throttles idle and watch the frame-rate. When the frame-rate settles down I can take off. Now that the frame-rate is no longer displayed by default I just count to seven and then go. When flying the glider there is no opportunity to wait, so I just have to let the pitch vary wildly until the frame-rate settles down. Anyone else seeing this? Dave -- David Culp [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
