In my experience, worst case is having the terminal (console) window open but covered (partially or completely) by another window, least bad is to have the console window selected. Best case for when the console window is not selected is to have it minimised. On NT like systems, it feels as if it helps to reduce the size of the console window as well.
Since I have never used game mode, I have no data points, but I would think that it is comparable to open and covered. Yes even a few lines really is a problem, I have seen characters appearing at about 2 a second when things get really bad. Try the logging options that other people have mentioned. Richard > 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 ? > > Best regards, > Jacek. > > _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
