Discussion:
Catalog issues with dhc3W
(too old to reply)
Stuart Buchanan
2017-06-16 20:40:13 UTC
Permalink
Hi All (primarily James),

I'm seeing odd behaviour with the launcher. It doesn't seem to detect
the dhc3/dhc3W-set.xml file, and subsequently complains that the
various variants can't find the file either:

can't find principal aircraft "dhc3W" for variant:
"/home/stuart/FlightGear/fgaddon/Aircraft/dhc3/dhc3A-set.xml"
can't find principal aircraft "dhc3W" for variant:
"/home/stuart/FlightGear/fgaddon/Aircraft/dhc3/dhc3F-set.xml"

I've had a look, and the file looks fine, and indeed I can start FG
with --aircraft=dhc3W

On the principle that any bug is shallow to enough eyes, has anyone
got any idea what might be going on?

-Stuart
Thorsten Renk
2017-06-17 05:48:53 UTC
Permalink
It's the included keyboard file dhc3-keyboard.xml which contains an out of
aircraft reference - once that is removed, all is fine here.

Why that makes the launcher complain I can't really say.

* Thorsten
Post by Stuart Buchanan
I'm seeing odd behaviour with the launcher. It doesn't seem to detect
the dhc3/dhc3W-set.xml file, and subsequently complains that the
"/home/stuart/FlightGear/fgaddon/Aircraft/dhc3/dhc3A-set.xml"
"/home/stuart/FlightGear/fgaddon/Aircraft/dhc3/dhc3F-set.xml"
I've had a look, and the file looks fine, and indeed I can start FG
with --aircraft=dhc3W
On the principle that any bug is shallow to enough eyes, has anyone
got any idea what might be going on?
-Stuart
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Flightgear-devel mailing list
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
James Turner
2017-06-19 08:12:16 UTC
Permalink
It's the included keyboard file dhc3-keyboard.xml which contains an out of aircraft reference - once that is removed, all is fine here.
Why that makes the launcher complain I can't really say.
The launcher needs to parse -set.xml files, and uses the SimGear parser to do that. However, the Simgear parse raises exceptions in various scenarios, such as when it can’t find an include file. And the launcher treats /any/ exception from the parser as fatal for that XML file, since it doesn’t have any other alternative.

The best solution would to fix the out-of-aircraft ref in the DHC3, assuming the path is ‘wrong’. (‘Correct’ paths should already be added to the search list when parsing, eg the FG_DATA directory). If the DHC3 path looks correct, but the launcher is rejecting it, we need to tweak the launcher code of course.

Kind regards,
James

Loading...