From: John C. <j4s...@ro...> - 2001-07-23 19:52:01
|
On Mon, 23 Jul 2001, Cameron Moore wrote: > * da...@me... [2001.07.23 13:29]: > > js...@ha... writes: > > > > > > I never saw this on my old 400MHZ processor. Could it be a problem > > > > with JSBSim's logging output going to a graphical terminal? In you're > > > > in Unix, try running > > > > > > > > fgfs --fdm=jsb --aircraft=c172 >/dev/null 2>&1 > > > > > > Oh, blast it! Yes, that could be part of the problem. Look in the aircraft > > > config files (c172.xml or x15.xml) in the appropriate aircraft directory. At > > > the very bottom of the config files is the <OUTPUT> section. You will likely > > > see this line: > > > > > > <OUTPUT NAME="JSBout.csv" TYPE="CSV"> > > > > > > If you want to turn logging off, change TYPE to NONE: > > > > > > <OUTPUT NAME="JSBout.csv" TYPE="NONE"> > > > > > > This should help at least a little. > > > > I doubt the CSV stuff is hurting much -- it's probably the information > > going to stdout and stderr. Graphical terminals can take a long time > > to draw text. > > -- > > David Megginson Turning logging off made a *big* difference for me. My system is weak in the processor area (K6-2 400) but I have a GeForceMX.Right now I'm flying over the ocean and I'm pulling about 20FPS, usually its 35-40. On the runway I was getting 1-6, where as LaRCsim gets around 15-20. Performance is way better though. I'll see what happens with todays code. TTYL John > > Is there a run-time option to change the FG log levels? AFAIK, the > setLogLevels() is hardcoded in main.cxx. > -- > Cameron Moore > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > http://lists.sourceforge.net/lists/listinfo/flightgear-devel > |