> 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.
SUMD = 'seriously underpowered machine/display' = SUMD
EXACTLY! I am happy that you today have a
'machine' that has 'power', but do NOT be sad for me with my
little machine. Year by year i grow, hopefully ...
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.
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 ...
DirectX 8.0a updates (video and sound) are smooth ... inputs (kb,js)
are read and acted upon 'immediately' ... and as i say, the -
:-)) the simulator FLIES :-))
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 ...
> ... I haven't seen reports (...) that comes close to the chaotic mess
you
> are reporting ... But I think your problems are beyond my control.
Now preference everything with - when running in a SUMD -
Well, yes and no. You can certainly do little about the approx. 2
minute start-up time for FG in my system, with any FDM. This is loading,
mapping, sorting, cacheing, indexing, etc etc ... and the disk light is
constantly on ... time to get coffee ...
Interestingly enough, one of the first indications that my SUMD is
settling down is I hear the 'sort-of-thump', which I have always presumed
is the gear coming into contact with the runway ...
I wish I could 'find' that event ... call it SUMDUP
To try to 'wait' such system-equilibrium, or SUMDUP, in
FGMagicarpet::update( multi_loop )
I experimented with a simple do not even run the EOM until at least 5
real seconds have elapsed ... but i agree there should be a better
trigger than time elapsed ...
You see. Here is a place where you could maybe help ...
re:JSBout - in a way i was asking why all those calculations when I have
not even started the engine yet?
Sure you still need to check wind/weather effects, but once wind
say is seen to be zero do NOT go off and set the property tree
with values that are already there, if your code does that ... This seems
especially true when some of the 'calculations' do not seem 'clamped' to
a sort of minimum-changed-before-more-calcs.
Or simply stated, avoid the 'slower micro-coded on chip' FPU
instructions as much as possible to help in the general system
resource use ...
But one piece of code you do have that I like very much is that
you start in a 'dead' ac. I really like that i have to get in and
remember to do some things to get the ac rolling ...
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?
Again taking the sample of 'magic', it seems the PLIB js read of
what is the 'throttle slider', on the very early, maybe only first
read yields a value above ZERO, thus if you 'ignored' the mags
setting (and starter) like magic (and JASim also) you sort of hit the
runway running ...
'magic' has no problem with this since if the FDM finds itself
below ground it pop itself back to the top ... and in JASim it is
only about 60% power, some the ac only moves slowly ...
All in all i hope you understand my comments are sometimes
related to all FDM's run by FGFS ... not 'singling' out any ...
and i hope they help.
rgds,
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.
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
