Long-Range Flight Impossible?

[Vodoun da Vinci]

If you haven't already, try turning off the traffic manager.
--prop:/sim/traffic-manager/enabled=false
While ai traffic looks nice, it needs fixing, as it tends to cause errors.

My solution to this issue happened quite a few pages back...I wonder how many continued failures due to unkown exception in the main loop will be cured by disabling AI traffic.

I thought we all already knew this or I would have mentioned it earlier.

"VooDoo" da Vinci

[mifi]

If you haven't already, try turning off the traffic manager.
--prop:/sim/traffic-manager/enabled=false
While ai traffic looks nice, it needs fixing, as it tends to cause errors.

My solution to this issue happened quite a few pages back...I wonder how many continued failures due to unkown exception in the main loop will be cured by disabling AI traffic.

I thought we all already knew this or I would have mentioned it earlier.

"VooDoo" da Vinci

While I appreciate this, it is not a solution. It is a workaround.

Anyways, I guess I will do as told and not bother with it...

m

[ChocBoy]

Well, if it's a workaround, it's a solution. Do you really want AI traffic?

[redneck]

TBH, I'd rather have planes in the area, even if no human controlled planes are, so yes, I would like to have AI traffic, at least until we have a much larger user base. It gets kinda lonely when you realize there's no one around for hundreds or thousands of miles. At least you get to see something, even if it won't talk to you during your flight if you have a nice set of AI traffic, which by the way could use some work once a real solution is found. I wouldn't prioritize it, but it would be nice to have it as a working feature.

[Vodoun da Vinci]

I have been running with the AI turned on to see aircraft using the bombable scripts and scenarios and haven't had any problems but prior to loading the bombable script I had to turn off AI to stop crashes...very intermittent crashes usually at KSFO and some others.

I don't see it as a permanent solution but it makes FGFS useable for those having lots of crashing. I don't feel that I have a prayer of contributing towards a fix of this. So temporary work arounds are the best I have to offer.

My apologies if it is inadequate.

"VooDoo"

[nickyivyca]

The Bay Area is generally the only area consistently giving me complete crash problems-It's also really bad with the freezeups, because FG gets really confused when I don't have an aircraft someone's using (or one that uses Pushback, but I copied the Pushback folder off of CVS) because it can't find any animations. Ironically, this area is my home area, so I want to fly around there the most, and I do.

But let's say I'm on a longish range flight starting at KSFO, once I get out of the Bay Area, and I don't change my tower location to away from it, if I go to Tower view, it immediately detects but cannot identify an error in the main loop. That's why I'm sure the Bay Area causes problems for me, and certainly for others. And AI traffic is disabled, and I run 1.9.1.

[mifi]

The Bay Area is generally the only area consistently giving me complete crash problems-

An interesting observation that your crashes are related to the location you fly in... Which route do you fly? (I will try if I can reproduce your problem)

I too have noticed that some flights are possible without any problems, while other routes consistently have problems. I will test some more this weekend with the Traffic Manager turned off. I am under the impression that turning off the traffic manager is an effective workaround (as was pointed out to me by this community). It is probable, but I have not yet done enough testing myself to be able to confirm.

Switching off AI is not the same as switching off the traffic manager though, is it?

When the property /sim/traffic-manager/enabled=false is set in the property window of fgrun, it generates a line "--prop:/sim/traffic-manager/enabled=false" (including the double quotes!) in the command line options that are passed to fgfs. This does not work on Linux. FGFS is exiting with an error message about the XML format, probably due to a problem in fgrun.

That is why I am starting fgfs in the usual way from fgrun. Then when fgfs is running and my plane is idling on the runway, I type '/' and then scroll to sim, traffic-manager, enabled and set the latter to false.

m

[AndersG]

Switching off AI is not the same as switching off the traffic manager though, is it?

When the property /sim/traffic-manager/enabled=false is set in the property window of fgrun, it generates a line "--prop:/sim/traffic-manager/enabled=false" (including the double quotes!) in the command line options that are passed to fgfs. This does not work on Linux. FGFS is exiting with an error message about the XML format, probably due to a problem in fgrun.

AI Traffic and the traffic manager are two different systems.
I would also use "/sim/traffic-manager/enabled=0" rather than false since I'm not sure that false would not be interpreted as the string "false" (which would, in many programming languages, be true if converted to a boolean value!).

/Anders

[MAKG]

Switching off AI is not the same as switching off the traffic manager though, is it?

When the property /sim/traffic-manager/enabled=false is set in the property window of fgrun, it generates a line "--prop:/sim/traffic-manager/enabled=false" (including the double quotes!) in the command line options that are passed to fgfs. This does not work on Linux. FGFS is exiting with an error message about the XML format, probably due to a problem in fgrun.

AI Traffic and the traffic manager are two different systems.
I would also use "/sim/traffic-manager/enabled=0" rather than false since I'm not sure that false would not be interpreted as the string "false" (which would, in many programming languages, be true if converted to a boolean value!).

/Anders

Which languages?

Anything that uses strtod() or its relatives to parse would give 0 for any string, and virtually everyone uses 0 to mean false.

[Jester]

Guess which language .... nasal of course!

[AndersG]

Guess which language .... nasal of course! :roll:

And in the property tree, since the GetValue*() methods just casts the value to the requested type and strings are (or at least used to be) represented as a pointer to a null terminated char array there. Hence, any string value apart from NULL is true. :)

/Anders

[mifi]

Goodness, now what?

Planned a flight from LFLL to LEBL... Shortly after takeoff, fg no longer updates the screen (fg does not hang, but it looks like it hangs).

In the log window I find the following (shortened):

Code: Select all

Warning: TangentSpaceGenerator: unknown primitive mode 9
Warning: TangentSpaceGenerator: unknown primitive mode 9
Warning: TangentSpaceGenerator: unknown primitive mode 9
.
.
.
Warning: TangentSpaceGenerator: unknown primitive mode 9
Warning: TangentSpaceGenerator: unknown primitive mode 9
Warning: TangentSpaceGenerator: unknown primitive mode 9
Warning: TangentSpaceGenerator: unknown primitive mode 9
Warning: TangentSpaceGenerator: unknown primitive mode 9
Program's vertex attrib binding 7, binormal
Program's vertex attrib binding 6, tangent
pos in msg = 45,4
lat = 45 lon = 4
lat_dir = 0  lon_dir = -1
AL Error (avionics): Invalid Operation at buffer remove
AL Error (avionics): Invalid Operation at buffer remove
AL Error (avionics): Invalid Operation at buffer remove
AL Error (avionics): Invalid Operation at buffer remove
AL Error (avionics): Invalid Operation at buffer remove
AL Error (avionics): Invalid Operation at buffer remove
AL Error (avionics): Invalid Operation at buffer remove
AL Error (avionics): Invalid Operation at buffer remove
Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..)
         -nan -nan -nan -nan -nan -nan segment ignored..
Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..)
         -nan -nan -nan -nan -nan -nan segment ignored..
Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..)
         -nan -nan -nan -nan -nan -nan segment ignored..
Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..)
         -nan -nan -nan -nan -nan -nan segment ignored..
.
.
.
Warning:: Picked up error in TriangleIntersect
   (0.032565 0.026345 0.032594,   -0.05076 0.022405 0.028615,   0.027754 0.026345 0.024356)
   (-nan,   -nan,   -nan)
Warning:: Picked up error in TriangleIntersect
   (-0.05076 -0.022405 0.028615,   0.032565 -0.026345 0.032594,   0.027754 -0.026345 0.024356)
   (-nan,   -nan,   -nan)
Warning:: Picked up error in TriangleIntersect
   (0.034332 0.013173 0.035063,   0.034332 -0.013173 0.035063,   -0.05076 -0.011202 0.031085)
   (-nan,   -nan,   -nan)
Warning:: Picked up error in TriangleIntersect
   (0.034332 0.013173 0.035063,   -0.05076 -0.011202 0.031085,   -0.05076 0.011202 0.031085)
   (-nan,   -nan,   -nan)
Warning:: Picked up error in TriangleIntersect
   (-0.05076 0.022405 0.028615,   0.032565 0.026345 0.032
.
.
.
Warning:: Picked up error in TriangleIntersect
   (0.00123479 -0.0181318 0.00338253,   0.00123479 -0.0263018 -0.00342587,   0.00123479 -0.0181318 -0.00342587)
   (-nan,   -nan,   -nan)
Warning:: Picked up error in TriangleIntersect
   (0.00123479 -0.0628944 0.0189039,   0.00123479 -0.0666297 0.0189039,   0.00123479 -0.0666297 0.00932382)
   (-nan,   -nan,   -nan)
Warning:: Picked up error in TriangleIntersect
   (0.00123479 -0.0628944 0.0189039,   0.00123479 -0.0666297 0.00932382,   0.00123479 -0.0628944 0.00932382)
   (-nan,   -nan,   -nan)
Warning:: Picked up error in TriangleIntersect
   (0.00123479 -0.0570738 0.0189039,   0.00123479 -0.0608091 0.0189039,   0.00123479 -0.0608091 0.00932382)
   (-nan,   -nan,   -nan)
Warning:: Picked up error in TriangleIntersect
   (0.00123479 -0.0570738 0.0189039,   0.00123479 -0.0608091 0.00932382,   0.00123479 -0.0570738 0.00932382)
   (-nan,   -nan,   -nan)


Those last lines were repeated endlessly with slighly different values, untill I killed fgfs. Judging from the log, I suspect fgfs was still flying, but was unable to update the screen for me.

Details of flight:
Traffic Manager was turned off
3D clouds on
AI on
Multi Player on
Real weather fetch on
Random objects on
Randow trees on
Aerostar 700

Command line (as generated by fgrun):

Code: Select all

/home/mifi/Software/Sources/fgfs/install/fgrun/bin/../../fgfs/bin/fgfs
  --fg-root=/home/mifi/Software/Sources/fgfs/install/fgrun/bin/../../fgfs/data
  --fg-scenery=/home/mifi/fgfs/terrasyncdata:/home/mifi/Software/Sources/fgfs/install/fgrun/bin/../../fgfs/data/Scenery
  --airport=LFLL
  --aircraft=aerostar700
  --control=joystick
  --enable-random-objects
  --disable-hud-3d
  --enable-ai-models
  --enable-real-weather-fetch
  --enable-clouds3d
  --geometry=800x600
  --bpp=32
  --atlas=socket,out,5,localhost,5505,udp
  --callsign=PH-MIFI
  --multiplay=out,10,mpserver02.flightgear.org,5000
  --multiplay=in,10,192.168.2.15,5001


Traffic Manager was later switched off while sitting on the runway.

EDIT: And it is reproducible. Did the same thing again, same result.

m

[Jester]

We like reproducible NaN errors
Use the --enable-fpe option and provide a gdb backtrace (preferably from a debug build)

[mifi]

We like reproducible NaN errors
Use the --enable-fpe option and provide a gdb backtrace (preferably from a debug build)

OK. I did.
Here is the bt from gdb:

Code: Select all

Program terminated with signal 8, Arithmetic exception.
#0  0x00000000009d9c7e in sg_bucket_span (l=-nan(0xf0000119dd940))
    at newbucket.hxx:80
80       } else if ( l >= -89.0 ) {
(gdb) bt
#0  0x00000000009d9c7e in sg_bucket_span (l=-nan(0xf0000119dd940))
    at newbucket.hxx:80
#1  0x00000000009d9e20 in SGBucket::set_bucket (this=0x7fffb830cb20,
    dlon=<value optimized out>, dlat=<value optimized out>) at newbucket.cxx:90
#2  0x00000000008506c0 in FGTileMgr::scenery_available (
    this=<value optimized out>, position=..., range_m=<value optimized out>)
    at tilemgr.cxx:402
#3  0x0000000000497483 in FGAILocalTraffic::DoGroundElev (this=0xd48b820)
    at AILocalTraffic.cxx:1533
#4  0x000000000049ba28 in FGAILocalTraffic::Update (this=0xd48b820,
    dt=<value optimized out>) at AILocalTraffic.cxx:563
#5  0x000000000049d66d in FGAIGAVFRTraffic::Update (this=0x7fffb830cb20,
    dt=-89) at AIGAVFRTraffic.cxx:129
#6  0x0000000000494347 in FGAIMgr::update (this=0xdcacf20,
    dt=<value optimized out>) at AIMgr.cxx:272
#7  0x000000000042f3ec in fgMainLoop () at main.cxx:446
#8  0x0000000000479692 in fgOSMainLoop () at fg_os_osgviewer.cxx:201
#9  0x000000000042e619 in fgMainInit (argc=19, argv=0x7fffb830d148)
    at main.cxx:951
#10 0x000000000042c47e in main (argc=19, argv=0x7fffb830d148)
    at bootstrap.cxx:229


Just to be complete... the command was

Code: Select all

/home/mifi/Software/Sources/fgfs/install/fgrun/bin/../../fgfs/bin/fgfs \
  --fg-root=/home/mifi/Software/Sources/fgfs/install/fgrun/bin/../../fgfs/data \
  --fg-scenery=/home/mifi/fgfs/terrasyncdata:/home/mifi/Software/Sources/fgfs/install/fgrun/bin/../../fgfs/data/Scenery \
  --airport=LFLL \
  --aircraft=aerostar700 \
  --control=joystick \
  --enable-random-objects \
  --disable-hud-3d \
  --enable-ai-models \
  --enable-real-weather-fetch \
  --enable-clouds3d \
  --geometry=800x600 \
  --bpp=32 \
  --atlas=socket,out,5,localhost,5505,udp \
  --callsign=PH-MIFI \
  --multiplay=out,10,mpserver02.flightgear.org,5000 \
  --multiplay=in,10,192.168.2.15,5001 \
  --enable-fpe \
  --prop:/sim/traffic-manager/enabled=0


As soon as in the air, I switched on the autopilot, heading 205, altitude 13000 (which was never reached).

Hope this helps.

m

[Jester]

That is in AI traffic. We have said many times to disable it. (It is a bug, nevertheless)
EDIT: you are missing --prop:bool:/sim/ai-traffic/enabled=0