Re: [Flightgear-devel] Broken aircrafts in CVS + Patches to property path
AnMaster wrote: -BEGIN PGP SIGNED MESSAGE--- with --aircraft=707 I get: YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! Current version needed is: 2.0 You have version: Found unexpected subsystem: METRICS, exiting. JSBSim failed to load aircraft and/or engine model Unknown exception in the main loop. Aborting... And that is just the two I remember, there are many more broken aircrafts in cvs, these two just happen to have bad property paths as well. Regards, AnMaster Sorry, AnMaster, I updated the 707 FDM back in May, but since I was working on it along with a bunch of other aircraft with visual reference point type problems (a task I haven't yet finished), I did not post the patch. Any bad property paths will still have to be corrected. Here it is: http://139.78.95.188/flightgear/VRP/707/ -- Reagan Thomas CEAT Labs 323 Engineering North Oklahoma State University (405) 744-5735 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Broken aircrafts in CVS + Patches to property path
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 First I have some more patches for property paths: http://rage.kuonet.org/~anmaster/flightgear/a4.patch http://rage.kuonet.org/~anmaster/flightgear/F80C.patch http://rage.kuonet.org/~anmaster/flightgear/UH-60.patch I would be happy to fix other aircrafts but some just doesn't work, so I can't test that my fix works. For example (both of these are unmodified from CVS with fg/plib as of this morning): with --aircraft=f4u I get: Failed to load submodel: Failed to open file at /home/arvid/src/external/flightgear/data/Aircraft/F4U/Models/pdisk.xml Failed to load aircraft from Aircraft/F4U/Models/f4u-model.xml (Falling back to glider.ac.) with --aircraft=707 I get: YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! Current version needed is: 2.0 You have version: Found unexpected subsystem: METRICS, exiting. JSBSim failed to load aircraft and/or engine model Unknown exception in the main loop. Aborting... And that is just the two I remember, there are many more broken aircrafts in cvs, these two just happen to have bad property paths as well. Regards, AnMaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGoMFnWmK6ng/aMNkRCnUPAJ0R2r4K43k6GFJNqQjBZnPAkKsnLwCguSSA y1HWENjAQSxg1/bHzUvide8= =Vsdv -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Broken aircrafts in CVS + Patches to property path
Hello AnMaster, Am Freitag, den 20.07.2007, 16:06 +0200 schrieb AnMaster: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 First I have some more patches for property paths: http://rage.kuonet.org/~anmaster/flightgear/a4.patch http://rage.kuonet.org/~anmaster/flightgear/F80C.patch http://rage.kuonet.org/~anmaster/flightgear/UH-60.patch I would be happy to fix other aircrafts but some just doesn't work, so I can't test that my fix works. For example (both of these are unmodified from CVS with fg/plib as of this morning): with --aircraft=f4u I get: Failed to load submodel: Failed to open file at /home/arvid/src/external/flightgear/data/Aircraft/F4U/Models/pdisk.xml Failed to load aircraft from Aircraft/F4U/Models/f4u-model.xml (Falling back to glider.ac.) thanks for reporting, there are two files missing, just committed a fix for that and the property names. greetings Detlef with --aircraft=707 I get: YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! Current version needed is: 2.0 You have version: Found unexpected subsystem: METRICS, exiting. JSBSim failed to load aircraft and/or engine model Unknown exception in the main loop. Aborting... And that is just the two I remember, there are many more broken aircrafts in cvs, these two just happen to have bad property paths as well. Regards, AnMaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGoMFnWmK6ng/aMNkRCnUPAJ0R2r4K43k6GFJNqQjBZnPAkKsnLwCguSSA y1HWENjAQSxg1/bHzUvide8= =Vsdv -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Broken aircrafts in CVS + Patches to property path
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Detlef Faber wrote: Hello AnMaster, Am Freitag, den 20.07.2007, 16:06 +0200 schrieb AnMaster: First I have some more patches for property paths: http://rage.kuonet.org/~anmaster/flightgear/a4.patch http://rage.kuonet.org/~anmaster/flightgear/F80C.patch http://rage.kuonet.org/~anmaster/flightgear/UH-60.patch I would be happy to fix other aircrafts but some just doesn't work, so I can't test that my fix works. For example (both of these are unmodified from CVS with fg/plib as of this morning): with --aircraft=f4u I get: Failed to load submodel: Failed to open file at /home/arvid/src/external/flightgear/data/Aircraft/F4U/Models/pdisk.xml Failed to load aircraft from Aircraft/F4U/Models/f4u-model.xml (Falling back to glider.ac.) thanks for reporting, there are two files missing, just committed a fix for that and the property names. greetings Detlef Thanks for also fixing the property path in it. Btw, some more patches: http://rage.kuonet.org/~anmaster/flightgear/patches/fkdr1.patch http://rage.kuonet.org/~anmaster/flightgear/patches/rascal.patch http://rage.kuonet.org/~anmaster/flightgear/patches/f4u.patch Regards AnMaster with --aircraft=707 I get: YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! Current version needed is: 2.0 You have version: Found unexpected subsystem: METRICS, exiting. JSBSim failed to load aircraft and/or engine model Unknown exception in the main loop. Aborting... And that is just the two I remember, there are many more broken aircrafts in cvs, these two just happen to have bad property paths as well. Regards, AnMaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGoOeGWmK6ng/aMNkRCnqrAKCgY3T4vDYH9j7bfW5tTH+T8hI8CACfSfPC U6N51o/O6aUzICdlz1RC+lY= =esu2 -END PGP SIGNATURE- - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
