Update: To observe this bug, I don't even need to taxi. I can just sit at the starting point of runway 31L at JFK with the engine off. After sitting about 8 minutes, I observe nan messages on the console.
One interesting thing is that *no* floating point exception was raised this time. The FPE trap was enabled but didn't catch anything. This is in contrast to previous times where either the trap was disabled or the FPE preceded any nan messages. This time I got only a finite number of nan messages ... in contrast to previous times when I got an apparently endless spew. This was with options passed via .fgfsrc not via the command line. This is more-or-less necessary when the FPE trap is enabled, if I want the sim to live long enough to get past the splash screen. For details, see http://www.av8n.com/fly/fgfs/nan--27763.log As before, the barf of system information is at http://www.av8n.com/fly/fgfs/barf.log ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
