Ok, grabbed your latest exe from - > >> http://www.vso.cape.com/~nhv/files/fgfs/fgfs.exe.gz
> My binaries are made against the 'then current' fgfsbase CVS files > Trying to run them against older base files is disaster Agreed! Do not know what caused you to think I would do this? I do have some old 'copies' around, but have been doing daily cvs updates for at least the last week or so ... That is an update of at least the Simgear, FlightGear and fgfsbase trees ... But not yet fully trusting this 'relatively new to me' tool called cvs, and since I normally do my updating from - :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.7, I decided to do a new complete base download to a new folder (HOME=d:\fg79cvs) - The anon ftp log of http://rockfish.net/fg should show a 2 hour session about 11:00 hrs GMT/UTC. Here .cvspass contains - :pserver:[EMAIL PROTECTED]:/home/cvsroot But your new exe of 15th CRASHES in exactly the same place as previously enumerated ... A compare of my update from flightgear.org with the fresh copy from rockfish.net, ignoring CVS generated files like Entries,Root,etc, show them to be exactly the same - as I think they should be? Of course about 60+ files of the some 2,300 in the base have up to about a 1 day different time stamp, but the contents remain unchanged. And of course ignoring the mashed c172.xml as also enumerated ... But I am no better off at the moment - After yesterdays complete recompile using yesterdays cvs FlightGear src my exe also now crashes ... we have seen this gremlin before ! Naturally the first two lines of the logs using your exe and mine are 'different'. Yours shows - Exec:[d:\dtemp\fgfs.exe] with command(s) [] FlightGear: Version 0.7.9 Mine shows - Exec:[..\debug\flightgear.exe] with command(s) [] FlightGear: Version MSVC6-FGFS32-0.7.8 Of course DO NOT BE FOOLED by the 'version' shown. This IS the 7.9 src. It is just that I have not yet altered the #define in FlightGear\src\include\config.h.msvc6, and thus the 'generated' src\include\config.h to the next version yet ... which you obviously have ... should do that soon. But there after the logs continue the same for a long time with - Scanning for root: command line fg_root = D:\fg79\fgfsbase Reading global preferences Finished Reading global preferences Reading default aircraft: c172 from D:\fg79\fgfsbase/preferences.xml Processing command line arguments Finished command line arguments Opening a window: 800x600 ... and so on, on, on, on ... When running your fgfs.exe the log ends abruptly with ... </autopilot> </PropertyList> ********* After fgSaveFlight() ********* Before globals->saveInitialState() I do not even know why it is doing fgSaveFlight() at all??? When running my flightgear.exe the log end with things we have SEEN before ... Touchdown report for RIGHT_TIP Sink rate at contact: 0.0000 fps, 0.0000 mps Contact ground speed: 0.0000 knots, 0.0000 mps Maximum contact force: 0.0000 lbs, 0.0000 Newtons Maximum strut travel: 0.0000 inches, 0.0000 cm Distance traveled: 0.0000 ft, 0.0000 meters fgGeodToGeoc(): Domain error sqrt(1.#QNAN) Initialized JSBSim with: Indicated Airspeed: 0 knots Bank Angle: -1.#IND deg Pitch Angle: 1.#QNAN deg True Heading: -1.#IND deg Latitude: 1.#QNAN deg Longitude: 1.#QNAN deg Altitude: -1.#IND feet loaded initial conditions set dt Finished initializing JSBSim FGControls::get_gear_down()= 1 FGJSBsim::set_Euler_Angles: 0, 1.#QNAN, -1.#IND FGJSBsim::set_Euler_Angles: -1.#IND, 0.0074002, -1.#IND FGJSBsim::set_Euler_Angles: -1.#IND, 1.#QNAN, 5.19934 So at the moment both exe are toast on my system. I wish I had zipped up the src of my previous exe before updating the folder from the cvs download, since I could then 'backtrack' a few days in the source, and begin adding the changes since then one by one - but I can't! I am sure there is probably a cvs command to 'do this', but am not so sure I would trust the update, and anyway it can not give me back the files I had modified ... Some days are just like that ... rgds, Geoff. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
