> > Geoff: > > It appears that your machine may not be capable of running FlightGear > > properly. This stuff should not be happening. ... > > ... I ran into similar things to what you are seeing a year ago when I > > had a seriously underpowered machine/display card.
Right. > 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. W98SE requires about 32MB of memory for _itself_, so there is little left for FGFS. The difference between a PIII and a Celeron is not apparent under Windows when you are low on memory, unfortunately. 500MHz is plenty to run FGFS under Linux with a good video card, based on the one I have here, but was marginal dual boot to Windows. Most commercial off the shelf computers from two years ago provided either software-only OpenGL or used the intel 810 style AGP chipsets which (a) require processor assistance and (b) need between 8MB and 16MB of your main memory in order to draw any 3D accelerated graphics. Given low memory and a marginal processor, performance will suffer. > I would respectfully say some very good parts of FG do run 'properly' > in my system. Simply, the CPU (and io bus) resources can meet the > demands of the application, and have lots of spare cycles left over ... It isn't that the PC is below what is recommended for FGFS, but that the resources remaining (after the operating system) are very low. I generally find that I need about 25% more processor and 64MB more memory on a computer, to use Windows as well as Linux on it. > Maybe 'this' pc system is below what you consider the MINIMUM > requirements are for a 'Flight Simulator --fdm=jsbsim' to successfully > run. If so, stop reading now ... this does not concern you ... JSBSim actually works very hard to simulate realistically and uses the processor; with logging turned on, it does significant disk I/O. If you're short of memory and having to swap, the extra disk load can crucify the performance of Windows to keep the application running. > 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. I suspect that part of the problem on low Windows PCs is that FGFS often assumes that it is running on a computer with either a lot of memory (for caching) or a decent swapping algorithm. I've always found that Windows machines run like a dog when they start swapping, much more so than Linux, which may be leading into the problem. Hope that helps ... _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
