[Flightgear-devel] Networking doesn't work (for me at least)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I recompiled FlightGear yesterday with the option --with-network-olk (since I didn't do that the first time), but it doesn't seem to work. When I run fgfs --enable-network-olk I don't get a Network menu or any other kind of indication that networking is up. Further, when I throw in the option --net-hud the program has a segmentation violation the moment I try to switch the HUD on. I got a backtrace, and here's the part that matters: Refreshing timestamps for -122.375 37.5625 scheduling needed tiles for -122.358 37.6117 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 20388)] net_hud_update () at net_hud.cxx:81 81other = head-next; (gdb) backtrace #0 net_hud_update () at net_hud.cxx:81 #1 0x080ef1f4 in fgUpdateHUD (x_start=-172.307709, y_start=0, x_end=812.307678, y_end=480) at hud.cxx:1172 #2 0x080eeca9 in fgUpdateHUD () at hud.cxx:1048 #3 0x080e8875 in fgCockpitUpdate () at cockpit.cxx:713 #4 0x08050a63 in fgRenderFrame () at main.cxx:854 #5 0x080527fa in fgMainLoop () at main.cxx:1265 #6 0x40090845 in idleWait () from /usr/lib/libglut.so.3 #7 0x0805700a in main (argc=3, argv=0xb804) at main.cxx:1823 #8 0x403963c1 in __libc_start_main () from /lib/libc.so.6 It sure looks like we're dereferencing another NULL pointer. Just in case there was some kind of unusual funkiness with configure, I erased all installed FlightGear binaries and recompiled again with --with-network-olk=yes, but I get the same result. This almost seems like an error on my part somewhere, but I don't know where it would be. I just tried running FlightGear again with --httpd=3000 and then again with --telnet=3000, in case that made a difference, but it still crashes the moment I try to turn on the HUD. Does anyone know what's going on here? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+C0ISVB8FYP9YqDcRAruxAJ9Szv/dUjhy8qzXeX6mIjJPZNrWkgCfS/GG vbzrZ3eKE7Q2XGI12ftmTM4= =HQYA -END PGP SIGNATURE- __ Do you Yahoo!? New DSL Internet Access from SBC Yahoo! http://sbc.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Scenery not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have a similar problem with KSJC. I'm running fgfs 0.91, with the 0.90 base package, the KSJC photo-realistic scenery version 2.0, and lots of scenery for the northern part of the western hemisphere. It appears that I'm underground. The altimeter reads 0, but the radar altimeter reads something a little over 32800 feet. The aircraft is still stuck, even if I supply a --altitude=3 parameter. I can use the autopilot to fly to KSJC, though, without trouble if I start at another airport. I didn't submit this yet because my mix of versions could conceivably cause odd behavior, and I haven't looked into it. -Luke On Mon, 2002-12-16 at 18:18, Curtis L. Olson wrote: Tommy, Here's a couple things you could try. - specify a starting airport: fgfs --airport=ENTC We have quite a few Norwegian airports in our database. - If you want to specify a lat/lon try avoiding exact whole number coordinates. Instead of --lat=59 --lon=10 try --lat=59.001 --lon=10.001 (or better yet, start at an aiport.) Regards, Curt. Luke's problem is pretty much exactly what I was getting. The workarounds indeed work though (at least the one I tried). Is this bug being looked into, however? Tommy McDaniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9/27sVB8FYP9YqDcRAkj1AKCKJA48/lNuGwVzHLff5jn/EU9SFACdETSs d41k2xbf5Hwo9BeU6bA0QQ4= =VBUY -END PGP SIGNATURE- __ Do you Yahoo!? New DSL Internet Access from SBC Yahoo! http://sbc.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Some aircraft crash FlightGear upon startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yesterday I downloaded, compiled, and installed the latest stable FlightGear, 0.9.1. Unfortunately, some of the aircraft do not work. When doing fgfs --aircraft=shuttle, the program dies as soon as soon as the cockpit view starts to pop up. I searched this list, and found some advice someone had given someone else about running the program with gdb and getting a backtrace, and I have done so, and will now present my results. I don't really know how to use the debugger for much, so I'll mention everything I did, just in case: $ gdb ./fgfs (from the directory FlightGear is in, of course; I installed it and some of the libraries it requires in a toplevel /flightgear directory) (gdb) run --aircraft=shuttle ... tons of output that can be supplied if needed... ... Start common FDM init ...initializing position... FGJSBsim::set_Longitude: -2.13556 FGJSBsim::set_Latitude: 0.656448 cur alt (ft) = 0 FGJSBsim::set_Altitude: -0.000431126 lat (deg) = 37.6117 Terrain altitude: -0.00141445 ...initializing ground elevation to -0.000431126ft... ...initializing sea-level radius... lat = 37.6117 alt = -0.000431126 ...initializing velocities... FGJSBsim::set_V_calibrated_kts: 0 ...initializing Euler angles... FGJSBsim::set_Euler_Angles: 0, 0.0074002, 5.19934 End common FDM init Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 4089)] SGPropertyNode::getDoubleValue (this=0x0) at props.cxx:1117 1117props.cxx: No such file or directory. in props.cxx (gdb) backtrace #0 SGPropertyNode::getDoubleValue (this=0x0) at props.cxx:1117 #1 0x0822fd3a in FGGain::Run (this=0x9891960) at FGGain.cpp:136 #2 0x0816ecc4 in FGFCS::Run (this=0x90315a0) at FGFCS.cpp:137 #3 0x08180762 in FGFDMExec::Run (this=0x8ddc130) at FGFDMExec.cpp:369 #4 0x081807ca in FGFDMExec::RunIC (this=0x8ddc130) at FGFDMExec.cpp:384 #5 0x08153167 in FGJSBsim::init (this=0x902b578) at JSBSim.cxx:234 #6 0x08050d57 in fgUpdateTimeDepCalcs () at main.cxx:909 #7 0x08051faf in fgMainLoop () at main.cxx:1177 #8 0x40090845 in idleWait () from /usr/lib/libglut.so.3 #9 0x0805700a in main (argc=2, argv=0xb824) at main.cxx:1823 #10 0x403963c1 in __libc_start_main () from /lib/libc.so.6 While I don't really know how to use the debugger, I do know C and C++, and it certainly appeared that SGPropertyNode::getDoubleValue was getting called with a NULL this pointer from FGGain::Run. I looked at the code, and indeed there are two calls to getDoubleValue in Run, both from pointers, so either InputNodes[0] or ScheduledBy is NULL. According to head, line 136 is LookupVal = ScheduledBy-getDoubleValue();, so ScheduledBy would appear to be the culprit to me. But it's not only the shuttle that does this; for example, using --aircraft=X15 results in the exact same output. I don't think these are the only two aircraft that do this either. If there's any more information I can provide or another way for me to be helpful in general, please let me know. Tommy McDaniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9/e3ZVB8FYP9YqDcRAkBeAJwNN30TOcN+mSFDV032VZUDUPiMsgCfS18z RIoCX7oZ1MfVSHvzgIYm6l4= =P9F7 -END PGP SIGNATURE- __ Do you Yahoo!? New DSL Internet Access from SBC Yahoo! http://sbc.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Scenery not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As I mentioned in another message I just sent to this list, I installed the latest FlightGear yesterday. Of course, I couldn't go long without trying different terrain, and my first try was a piece including southeast Norway. The problem is that, when I try starting FlightGear up in that tile, there is no scenery, it says my coordinates are 0 degrees and 0 degrees, and the plane just doesn't do squat. I can tell the engine to throttle up, but the RPM indicator stays at 0, and the plane just flat doesn't do anything but sit there. Also, there seems to be an infinite number of no terrain intersection messages that begin to be output as soon as the plane is ready to go (if only it worked), interspersed with occassional Failed to remove nav-vor-ident sound messages and a few others. I looked through the list archives, and I found mention from October or so about --lon and --lat having problems, and someone suggesting that it was only the eastern hemisphere that wasn't working, perhaps because FlightGear was parsing coordinates in that hemisphere improperly. I therefore downloaded the terrain tile that includes Orlando, Florida, and lo and behold, it worked like a charm. It was suggested that the problem might be in options.cxx, and I have indeed looked at the file for a few minutes, but can find no particular error. In fact, when I run ./fgfs --lon=11 --lat=59 2 /dev/null from the directory FlightGear is in the very first output is: parse_time() = 11 parse_time() = 11 parse_time() = 59 parse_time() = 59 which seems to correspond to the coordinates I have entered. Perhaps someone that knows which variables to follow (and knows how to use the debugger, which I don't) can check out what's going on here. I have plenty of output messages that I can present if needed, but I doubt that they will be helpful. If there's anything I can do to help out here and restore half of the world to FlightGear (assuming that's what the problem is), just let me know. I know C and C++, for what it matters. Tommy McDaniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9/fcyVB8FYP9YqDcRAre8AJ0R57OTsWO8lt6i1p3d6MIe+nlDYACffMV9 481jT9li4U0WEFfjxo18LC4= =Z9ph -END PGP SIGNATURE- __ Do you Yahoo!? New DSL Internet Access from SBC Yahoo! http://sbc.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
