[Flightgear-devel] TriangleIntersect errors (also an FPE in SGSoundSample::update_absolute_position)
Trying a multiplayer session at KSFO today, starts up fine (with the R22), after about 30 - 40 seconds a constant stream of Warning:: Picked up error in TriangleIntersect (0.488171 0.432994 0.074523,0.419428 0.338607 0.151383, 0.488171 0.338607 0.131757) (nan,nan,nan) which locks the sim, the numbers vary. Mailing list search indicated that gdb'ing with --enable-fpe would be useful, but in this case it gives us an FPE as below before the splash screen is gone... Program received signal SIGFPE, Arithmetic exception. [Switching to Thread 0x7f181bb82790 (LWP 20736)] 0x0098b6bf in SGSoundSample::update_absolute_position (this=0x984d1b0) at ../../../SimGear/simgear/math/SGQuat.hxx:405 405T r = 2/dot(*this, *this); -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] TriangleIntersect errors.
Greetings, For about the last month I've noticed with the CVS build of FG that after some time (it seems to vary between about 40mins to around 90mins) I'll get a constant stream of errors. Sometimes it starts when I switch to the Tower View, but most times it just starts mid-flight. I have tried turning off TrafficManager with --prop:/sim/traffic-manager/enabled=0 and also turning off AI as mentioned in the forums, but this seems to have no effect. When this occurs the errors are so frequent that it becomes unusable, the only way out is CTRL-C from the command line, or clicking and waiting for 30seconds to get a menu to quit. Below is an short extract of the errors; Warning:: Picked up error in TriangleIntersect (-0.072605 0.529981 -0.111424, -0.073436 0.535242 -0.117702, -0.07705 0.529981 -0.114243) (nan,nan,nan) Warning:: Picked up error in TriangleIntersect (-0.078412 0.535242 -0.135916, -0.082994 0.529981 -0.136174, -0.07705 0.529981 -0.114243) (nan,nan,nan) Warning:: Picked up error in TriangleIntersect (-0.078412 0.535242 -0.135916, -0.07705 0.529981 -0.114243, -0.073436 0.535242 -0.117702) (nan,nan,nan) Warning:: Picked up error in TriangleIntersect (0.377004 -5.62643 0.600728, 0.232501 -5.62643 0.612474, 0.145284 -5.62643 0.611523) (nan,nan,nan) Warning:: Picked up error in TriangleIntersect (0.145284 5.62643 0.611525, 0.232501 5.62643 0.612476, 0.377004 5.62643 0.60073) Is there anything else I can try to determine what causes the errors or to fix them? Cheers Scott. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TriangleIntersect errors.
On Sun, Sep 13, 2009 at 8:19 AM, Scott Hamilton scott.hamil...@popplanet.biz wrote: Greetings, Below is an short extract of the errors; Warning:: Picked up error in TriangleIntersect (-0.072605 0.529981 -0.111424, -0.073436 0.535242 -0.117702, -0.07705 0.529981 -0.114243) (nan, nan, nan) Is there anything else I can try to determine what causes the errors or to fix them? Use the --enable-fpe option, preferably with a debug build, and get a backtrace from gdb. -- Csaba/Jester -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TriangleIntersect errors.
On Sun, 2009-09-13 at 22:48 +0200, Csaba Halász wrote: On Sun, Sep 13, 2009 at 8:19 AM, Scott Hamilton scott.hamil...@popplanet.biz wrote: Greetings, Below is an short extract of the errors; Warning:: Picked up error in TriangleIntersect (-0.072605 0.529981 -0.111424, -0.073436 0.535242 -0.117702, -0.07705 0.529981 -0.114243) (nan,nan,nan) Is there anything else I can try to determine what causes the errors or to fix them? Use the --enable-fpe option, preferably with a debug build, and get a backtrace from gdb. command line options; gdb --args bin/fgfs --enable-sound --enable-hud --aircraft=A380 --airport=YSSY --runway=34L --timeofday=afternoon --enable-real-weather-fetch --enable-clouds3d --nav1=108.3 --dme=nav1 --enable-fpe Program received signal SIGFPE, Arithmetic exception. 0x0087e6f2 in FGNavRadio::updateReceiver (this=0xc09c760, dt=0.03) at navradio.cxx:474 474 double range_exceed_norm = loc_dist/effective_range_m; (gdb) bt #0 0x0087e6f2 in FGNavRadio::updateReceiver (this=0xc09c760, dt=0.03) at navradio.cxx:474 #1 0x0087ec4b in FGNavRadio::update (this=0xc09c760, dt=0.03) at navradio.cxx:363 #2 0x00b2b691 in SGSubsystemGroup::Member::update (this=0xc099ff0, delta_time_sec=value optimized out) at subsystem_mgr.cxx:308 #3 0x00b2dc6c in SGSubsystemGroup::update (this=0xc064db0, delta_time_sec=0.03) at subsystem_mgr.cxx:161 #4 0x00b2b691 in SGSubsystemGroup::Member::update (this=0xc06a1a0, delta_time_sec=value optimized out) at subsystem_mgr.cxx:308 #5 0x00b2dc6c in SGSubsystemGroup::update (this=0xfb4d68, delta_time_sec=0.03) at subsystem_mgr.cxx:161 #6 0x004354b2 in fgMainLoop () at main.cxx:461 #7 0x0049c369 in fgOSMainLoop () at fg_os_osgviewer.cxx:172 #8 0x0043204c in fgMainInit (argc=12, argv=0x7fffd9e8) at main.cxx:1005 #9 0x00431523 in main (argc=12, argv=0x7fffd9e8) at bootstrap.cxx:228 (gdb) inspect loc_dist $1 = 295313.5432570572 (gdb) inspect effective_range_m $2 = 0 Hope that helps. Scott. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TriangleIntersect errors.
On Mon, 2009-09-14 at 01:52 +0200, Csaba Halász wrote: On Mon, Sep 14, 2009 at 1:11 AM, Scott Hamilton scott.hamil...@popplanet.biz wrote: command line options; gdb --args bin/fgfs --enable-sound --enable-hud --aircraft=A380 --airport=YSSY --runway=34L --timeofday=afternoon --enable-real-weather-fetch --enable-clouds3d --nav1=108.3 --dme=nav1 --enable-fpe Hmm, 108.3 is out of range for me from YSSY, so the code doesn't even get to the location of your crash. Maybe the problem concerns nav2, can you tell what frequency that is tuned to? 108.3 is for WSSS (the intended destination) From the Equipment - Radio menu I see; NAV1 108.3 / 111.7 radial 280 NAV2 116.8 / 113.9 radial 28 ADF 379/ 341 The FPE signal does occur within the range of nav radio for YSSY, it's often not that far out, but the original TriangleIntersect was normally further along the flightpath. This feels like it is new behaviour as I have been specifying the destination ils freq for quite some time on the command line, is that not such a good idea? Cheers Scott. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
