Tim Moore wrote: > Durk Talsma wrote: >> On Friday 15 May 2009 20:31:17 Durk Talsma wrote:
>> >> While trying to trap bad data in this the popMatrix function, I just >> noticed that a bad transformation matrix is already set up relatively >> early in the process, only a few levels deep at the stack. I haven't >> been able to relate this to any meaningful object yet. (All that came up >> was the name "Scene"). >> >> So, it looks like a transformation error early on blows up the intersect >> line vector(s) already. and scenegraph is traversed further down, OSG >> keeps happily multiplying already corrupted data with valid >> transformation data further down the line, restuling in an intersect >> line, composed of NaNs. This goes unnoticed, until the error is finally >> picked up at the first possible occasion where there's a nan error >> check. That is, in trialintersect. >> >> I hope to continue this investigation later, and hope to be able to >> traverse the bad data to their true source. > It may be helpful to dump the scene graph to a file (from the debug menu) > once you're getting the NaN error. Hopefully the offending matrix will > be printed with NaNs instead of valid coordinates. > > Tim I've added an --enable-fpe argument which, on Linux, will cause an abort or core dump on a division-by-zero or other invalid floating point operation, including generating NaNs and overflowing float-to-integer conversions. See if you can get to the source of the NaNs using that. Tim ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
