On 01/26/2011 01:31 PM, Anders Gidenstam wrote:
On Tue, 25 Jan 2011, dave perry wrote:
I have tried to load several AC that did not load with "filed to load
<file name>" errors. So I did a survey of the entire up-to-date
fgdata. I used an up-to-date fgrun and went through all the AC.
The following do not load even to the viewer in fgrun:
737-100, 737-300, AG-14, Airwave Xtreme 150, CRJ-200, DC-8-63, Fairchild
Metroliner, Fooker50-Denim, Jaguar, Late-29, marchetti, MIG-29 Fulcrum,
Mirage F1, North American OV-10A USAFE Bronco, Short Empire, x24b, and
Zepphelin NT07 multiplayer copilot.
Did you try them in FlightGear too?
As far as I know both Short Empire and ZLT-NT-copilot (the latter doesn't
have any visible model btw) load fine in FlightGear so if the problems
with them occur only in fgrun I'd be inclined to consider it a problem in
fgrun's model viewer rather than a problem in the aircraft.
Cheers,
Anders
Hi again,
I decided to kill a few hours today chasing down the source of the
failure in fgrun for each AC I listed. I can put these failures in 3
classes. These are the first things that fgrun rejects. There are
likely others.
Class 1: fgfs and fgrun handle recursion of paths differently.
Anders, you are correct concerning the failure of fgrun to load both
the Short Empire and the ZLT-NT-copilot. These as well as the
Jaguar fail to load in fgrun because of differences in the way
recursive paths are handled in fgrun and fgfs xml parsers.
Class 2: Linux Windows path differences (spaces in dir and file names
or case sensitive).
737-300 path is .../Flightdeck/Instruments/STBY/alt.xml but file is
ALT.xml
AG-14 path is .../Instruments/Reloj digital/Reloj digital.xml
Fairchild Metroliner path is .../Instruments/Marker/MarkerLights.xml
but actual path is .../Instruments/marker/MarkerLights.xml
Mirage_F1 path is ../Models/cockpit/Divers/... but actual dir is
divers
Class 3: File or dir missing
737-100 several redundant models for instruments need to be deleted
to match actual
directory structure. Example:
.../Instruments/aib/ai.xml dir aib doesn't exist
CRJ-200 path .../fgdata/Models/Airport/Pushback/warning-light.xml
doesn't exist
DC-8-63 <path>Aircraft/dc8-63/Models/cargobox.xml</path> doesn't exist
Fokker50-Denim path .../Models/fokker50denim.xml doesn't exist
Fokker50-KLM path .../Models/fokker50klm.xml doesn't exist
Fokker50-VLM path .../Models/fokker50vlm.xml doesn't exist
Late-29 path .../Effects/wakeG.xml, actual path
.../Effects/waves/wakeG.xml
Mig-29 path .../Effects/tiptrail.xml, no Effects dir
OV-10A USAFE path .../Aircraft/OV10/Effects/smoke.xml, no Effects dir
The UIUC models with .mdl files don't load in fgrun viewer and don't
seem to work from the command line either.
Case 1 needs to be addressed by the maintainers of fgrun. Since this
difference in parsing recursive paths only shows up for 3 of 100+
aircraft, it is true that this can be easily avoided by the aircraft
maintainers.
Case 2 should be addressed by the aircraft maintainers as FlightGear is
a cross-platform project.
Case 3 should also be addressed by the aircraft maintainers. Some of
this is just sloppy xml files with cruft not removed because it is not
causing fgfs to crash or abort. Some of this is likely "work in progress".
Is it possible to add a switch to the fgfs command line so that it
aborts when a file or directory request violates the cross-platform goal
(names with case not matching the actual dir or file names or names with
embedded spaces).
Cheers,
Dave P.
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
