On 10/24/02 at 12:48 PM Jacek M. Holeczek wrote:
>> This is a known problem - Win95/98/Me are absolutely hopeless at
>outputting
>> to the console - NT/2000/XT are much quicker, and Linux quicker still.  
>
>I'm not very experienced here ... but are you sure that the problem is
>just writing to the "terminal window" ?
>>From what I can see ... when it happens ... there are about 20 lines of
>text written (something like "... Updating Sun position ..." is among
>them). That is not very much ! Moreover ... If I remember well the problem
>seems to exist also when the "terminal window" is minimized and when FGFS
>runs in "full screen mode" - in both cases the "terminal window" is
>invisible (writing to it should be fast).
>I tried to "set JSBSIM_DEBUG=0", but it does not seem to help much.
>In any case ... is there anywhere any option in Win98SE that I could
>try to activate in order to get it faster ?

Yes, I'm absolutely sure, the problem *is* writing to the console window in
Win9x/Me.  I run Flightgear in 98SE, NT4 and Linux, and it is absolutely,
definately the console output that causes the pauses.  The whole Win9x/Me
console API is inherently inefficient and broken - attempting to use a
scroll buffer in the console also doesn't work properly with 9x but is fine
with NT.  The only way to get round it is to output nothing whilst running.
 Unfortunately console output is currently set at compile time in
Flightgear (JSBSim has some runtime control but I'm not sure if the ground
contact messages can currently be turned off), and even when compiled with
--without-logging the sun update stuff still gets output.  The quickest fix
would be to fix the SG_LOG level of that output to be disabled with
--without-logging.  The best fix might be to enable full run-time logging
control.  I have commented out all the sun position information stuff in my
own build in the past and the pauses go away.  As someone else has said,
minimising the console window can help, but some pauses still get through
IME.  Curt - can we change the SG_LOG level of the sun position stuff so it
is disabled by configuring with --without-logging along with the rest of
the output?

Cheers - Dave


_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to