Le vendredi 17 juin 2005 à 13:19 +0200, Erik Hofman a écrit : > Harald JOHNSEN wrote: > > BONNEVILLE David wrote: > > > >> I forced 60 Hz because I will use a projection system ;) > >> > >> Well for the moment, I don't think I need to lower my fps, but maybe, > >> what would > >> be nice is if I could force FG to run at a given fps which prevents me > >> from > >> "little freezes"... ;) > > > I see... There is something weird somewhere in the code, don't know if > > someone has allready investigated that or > > perhaps it is simply by design but those freeze are a real pain. The fps > > can drop by 50 or 90% for a few frames > > for no reason. Is it caused by the 360° scan done every 500 frames, or > > some side effect of the autogen or > > perhaps some other piece of code (atc, ai, fdm, etc) ? > > You can only effectively reduce them by using a dual processor system > and with threads enabled. Reading the scenery from disk does take time, > whether you like it or not. > > Using SCSI (and disk striping) would help also. > > Erik > SCSI has ever been, surely, the best way, i do use it with the best results. May be an other way: Does anybody tried to preload scenery in virtual memory disk ? -- Gerard
_______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
