Okay, I understand that you are saying that the planes are not listing in FGrun using 3.5, I think.
I also saw you mention something about files that have a letter(a,b,c,e or A,B,C,E). Please notice that the files with the capital letters also have the word '-set'.
The files with names like Electra10a-jsb.xml get used by the associated file Electra10A-jsb-set.xml. It's the files that end in -set.xml that the Launcher wizards, FGrun or Qt5(the official 3.5 launcher ) are looking for.
In other threads Jabberwocky(the current active plane author) and I and others have detailed a problem that planes by Jabberwocky using his "JPack" ( you have to have JPack for this Electra set of planes to work ) are not listing planes in some instances using some Launchers.
There is a bug report about this at the bug tracker.
1772 PropertyList Include tag a problem for Qt5This is the thread with the most discussion about the problem here in the forum:
Airplane is in FG root, can't see in flightgear wizardThis link from that thread is particularly of interest as it spells out a work around that seems to work, is easiest to perform, as we await the actual bug fix that would make this moving a folder around unnecessary any longer.
http://forum.flightgear.org/viewtopic.php?f=22&t=26504&start=45#p248139Also, being that you are on Linux, I might suggest that until the bug is fixed that if you decide to use a Jabberwocky plane that doesn't list in a launcher that you instead do not use the launcher and instead load the plane from the command line using a configuration file.
http://wiki.flightgear.org/FlightGear_configuration_via_XML#Adding_your_own_settingsOr you can do this file moving I mentioned.
one)
This is easiest if you have the download version of the plane from the GIT site rather than the plane actually in a local git repository, because the first thing I'm going to ask you to do is delete the Lockheed-Model10 folder to fix any case where some of the planes
are listing and some are not.
two)
Start the simulator with any other plane in your launcher of choice and after the simulator loads and settles for usage, close the simulator. This flushes out any memory of the Lockheed-Model10 folder in the launcher.
three)
unzip the Lockheed-Model10-master.zip into the Aircraft folder where you keep your planes.
four)
There is no four ( thanks Douglas Adams hehe
)
five)
Make sure that the folder "JPack" is in that same Aircraft folder.
six)
MOVE the "JPack" folder out of that Aircraft folder and move it into FlightGear 3.5.0/data/Aircraft folder.
seven)
Start the launcher using the wizard as normally. On this load you should see the Electra's A, Amelia, B, C, and E listed.
eight)
Choose one of those planes and then start the simulator. As soon as the simulator settles for usage exit the simulator and if you have to, close the launcher wizard if it is still open.
nine)
MOVE "JPack" folder back to the Aircraft folder where the Lockheed-Model10 and all your other installed aircraft are.
We do this because in some cases leaving the JPack in /data/Aircraft often does not let the Launcher load and the Launcher crashes if we try to load it with out having moved JPack back.
ten)
Restart the launcher and notice that the planes all list, are selectable, and will load in the simulator, that the simulator will run them without crashing.
I have to do this file moving every time I install a plane from Jabberwocky that uses the JPack in order to see the new plane listed. Minor nuisance while I await the actual bug fix. Jabberwocky's planes are typically worth the nuisance.
I would be interested if any or all of this does or does not work for you. This is what I have to do every time I install a very new to me Jabberwocky plane until the Qt5 Launcher PropertyList/Include bug is fixed.
Best of luck to you
--Ray
Post Edit: seems I'm wrong about no number four. The reference is not Doug Adams and the Hitchhikers guide to the galaxy but instead it the Monty Python's "Bruces Sketch" where there is
no rule 6Ray St. Marie
FlightGear Forum
But IIRC this version should be fairly fresh...
Other times I encountered this problem, but I never found any documentation to explain what is necessary to insert the definition file in order to see the plane in the list of "run_fgrun.sh".