ok ... one more time ... > > > ... Really, the FDM takes a very small amount > > That is agreed. But i was making a point about how 'rocking' the ac > > when the engine/mags are off (and 0 wind) cause the 'display' to be > The wind will rock the aircraft. If your display card can't keep up with > this minimal activity, get a new display card.
Yeah! Precisely. perfectly. Can I give you the number of my person-in-charge-of-upgrade of our in-house major system? ... and you tell them (actually her) - err, I only write an fdm for that in which in can run. Get a better capability, or ??? shut up ??? :-))) > only 2 or 4 MB of video RAM I am surprised you can run at all. It does run. It runs well. It is the best since sliced bread! Keep it up forever. I am really for dissemination of knowledge. And being able to 'magic carpet' along a coast line, could really help in geography lessons ... at the very least ... There are really and truely not many (free or otherwise) products out there where you can elevate your self say just 5000 feet above mean sea level above SF, turn south, take on some speed and travel along the 'real' usa coast until say you reach the LA basin, which you 'recognise' from your geography lessons, or on further south ... forever, until the tiles run out !!! So why does this FGFS workable-in-this-tiny-pc-environment scenerio become 'impossible', or at least more/very difficult, if you add in the EOM, 'equation of motion' of an aircraft? You tell me? I have just agreed i turn OFF another big graphic grabber - the panel - and run only on the HUD - modified as earlier mentioned to ALWAYS show frame rate ... HUD's must do this ... maybe a hud xml changes? The only 'suggestion' i had was that an fdm who did well in the overall scene would have *nothing* to do until eng/mags/wind became 'alive. No trim or ANYTHING until at least all the scenery tiles had been laid ... As mentioned, that can be several 'minutes' into the ride ... > nothing in the FDMs that is giving you problems, so just put that out of > your mind. Your troubles are caused by having a machine that is apparently > not up to the task. I found this out myself ... for many months ... > until I upgraded my machine. So we re-start at the same sentence. :-))) I like JSBSim, at least in its c172 'feel'. I am not so familiar with other ac, but spend at least some of my time c172'ing around airfields. But this ac is not a real mover ... and must try others ... I am sorry none of what i said made any difference ... but it is ok. i enjoyed saying it ... A few questions ... some 'silly' cvs things ... I use the cmd cvs update -dP, but in FlightGear, i constantly get some 'warning' report about a missing 'yasim\util'??? directory ... but is says 'skipped' ... Is this all ok? I thought -P = prune empty. But of course it will NOT be empty until you/i/cvs delete things ... Now i am also getting the same thing in SimGear regarding the dearly recently departed zlib directory ... You mean cvs DOES NOT delete non-existant items in what is now knows as a non-existant directory? Then that seems to miss the point of 'update' ... > The card itself has zero memory; it steals what it needs from the system > memory to do graphics. At 1024x768x16, that is 1.5MB for 2D graphics > and increases to between 6MB and 8MB for 3D. A severe impact for you. I know this. Have to tolerate this. Live with this ... I certainly agree 'certain' iterative memory allocation should have 'no impact' on a well written memory system ... did i not mentions i run win32? :-)) rgds, Geoff. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
