RE: [Flightgear-devel] FDM from file broken?
I've looked into this further and it seems that FGNative::process() fails when reading in FDM data from the file. Process() calls io-read(...) asking for a 1704 byte chunks from the input file. After one or two successful 1704 reads, io-read(...) returns indicating that it couldn't read another 1704 bytes from the file and FGNative::process() dies. This happens even though the total numbers of bytes read from the file are no where near its total size. Unless I've set something up incorrectly, it looks like this functionality is broken. Does anyone know if this is a known issue? Replay functionality is very important to me, so if it's broken I'll take the time to fix it; I just want to make sure it's not something I've set up incorrectly. Also, I'm running FlightGear on Windows XP. Thanks, Vance -Original Message- From: Vance Souders Sent: Thursday, August 19, 2004 3:53 PM To: [EMAIL PROTECTED] Subject: [Flightgear-devel] FDM from file broken? I saved out FDM information using -native=file,out,120,flight1.fgfs. When I try and read it back in using -native=file,in,120,flight1.fgfs --fdm=external, the aircraft just sits there. It looks like FGNative::process() is pulling data out of the file. Any ideas on what might be causing this? I'm using the latest source code release (0.9.5). Thanks, Vance ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM from file broken?
Vance Souders wrote: I've looked into this further and it seems that FGNative::process() fails when reading in FDM data from the file. Process() calls io-read(...) asking for a 1704 byte chunks from the input file. After one or two successful 1704 reads, io-read(...) returns indicating that it couldn't read another 1704 bytes from the file and FGNative::process() dies. This happens even though the total numbers of bytes read from the file are no where near its total size. Unless I've set something up incorrectly, it looks like this functionality is broken. Does anyone know if this is a known issue? Replay functionality is very important to me, so if it's broken I'll take the time to fix it; I just want to make sure it's not something I've set up incorrectly. Also, I'm running FlightGear on Windows XP. It could be that process() is reading the entire file the first time. This makes sense in the context of a net connection where you want to grab all pending messages and just use the most recent one, but doesn't make sense in the context of a file obviously. file should be special cased, but perhaps it's been overlooked for the native protocol? Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FDM from file broken?
I think I might have goofed... I compiled simgear without __MINGW32__ defined. I'm in the process of recompiling the lib; I'm pretty sure that's what was tripping things up. Thanks, Vance -Original Message- From: Curtis L. Olson [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 12:20 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] FDM from file broken? Vance Souders wrote: I've looked into this further and it seems that FGNative::process() fails when reading in FDM data from the file. Process() calls io-read(...) asking for a 1704 byte chunks from the input file. After one or two successful 1704 reads, io-read(...) returns indicating that it couldn't read another 1704 bytes from the file and FGNative::process() dies. This happens even though the total numbers of bytes read from the file are no where near its total size. Unless I've set something up incorrectly, it looks like this functionality is broken. Does anyone know if this is a known issue? Replay functionality is very important to me, so if it's broken I'll take the time to fix it; I just want to make sure it's not something I've set up incorrectly. Also, I'm running FlightGear on Windows XP. It could be that process() is reading the entire file the first time. This makes sense in the context of a net connection where you want to grab all pending messages and just use the most recent one, but doesn't make sense in the context of a file obviously. file should be special cased, but perhaps it's been overlooked for the native protocol? Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FDM from file broken?
Well, it still doesn't work. I tried exporting and importing a flight using -native... with the released windows binary and it exhibits the same behavior as the source release. -Vance -Original Message- From: Vance Souders Sent: Friday, August 20, 2004 12:30 PM To: 'FlightGear developers discussions' Subject: RE: [Flightgear-devel] FDM from file broken? I think I might have goofed... I compiled simgear without __MINGW32__ defined. I'm in the process of recompiling the lib; I'm pretty sure that's what was tripping things up. Thanks, Vance -Original Message- From: Curtis L. Olson [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 12:20 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] FDM from file broken? Vance Souders wrote: I've looked into this further and it seems that FGNative::process() fails when reading in FDM data from the file. Process() calls io-read(...) asking for a 1704 byte chunks from the input file. After one or two successful 1704 reads, io-read(...) returns indicating that it couldn't read another 1704 bytes from the file and FGNative::process() dies. This happens even though the total numbers of bytes read from the file are no where near its total size. Unless I've set something up incorrectly, it looks like this functionality is broken. Does anyone know if this is a known issue? Replay functionality is very important to me, so if it's broken I'll take the time to fix it; I just want to make sure it's not something I've set up incorrectly. Also, I'm running FlightGear on Windows XP. It could be that process() is reading the entire file the first time. This makes sense in the context of a net connection where you want to grab all pending messages and just use the most recent one, but doesn't make sense in the context of a file obviously. file should be special cased, but perhaps it's been overlooked for the native protocol? Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
