> More specifically 'this' machine - Back at the end of 1999 this > latest-so-far pc (i hv 4 if i do not count those that just gather dust) > was a 'big store' off-the-shelf bargain 'package' with > 'genuine intel' PIII at abt 500+ MHz. The mark is 'Unika', with only > 64 MB RAM, but with a 256 MB upgrate waiting in the wings, running > Windows 98 SE ... stock standard stuff.
Tell me about the display car dyou have, how much memory there? > re:JSBout - in a way i was asking why all those calculations when I have > not even started the engine yet? Trimming is done, for one thing. Really, the FDM takes a very small amount of computation time. Most of the time is spent in the display routines, IIRC. > Or simply stated, avoid the 'slower micro-coded on chip' FPU > instructions as much as possible to help in the general system > resource use ... Do you have some particular examples? > That is also 'good' in the sense, since the ac should not move (no wind) > there will be no changes in lat/lon/alt, and no change in pitch/roll/yaw, > and the 'scenery/tile' manager can get on with its task ... but do you > also avoid EOM-FPU calcs at this time? This is a non-issue, as far as I am concerned. Like I said, these calculations have a very small impact on the program. > Geoff. > > ps: just to mention, after a similar 2/3 minute start-up my > FS2000 runs fine in this system ... so it can not be all bad. The same thing was true of my machine, which was less powerful than yours. My problem, I think, was that I had only 8 MB of video RAM. Jon _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
