jomo wrote in Wed Oct 21, 2020 8:21 am:tikibar wrote in Wed Oct 21, 2020 12:05 am:The 747-8F is available in the official hangar / fgaddon / whatever you want to call it. It is packaged together with the -8i. I'm not sure why it wouldn't show up. If you have the 747-8i from the official hangar, you have the 747-8F too.
Nice to hear from somebody who knows -- but sorry: I do not find the FGFS-pages "/ fgaddon" as you defined!
As I see it there are:
*
https://www.flightgear.org/ I would call that the basic FGFS home-page
*
https://www.flightgear.org/download/ for all FGFS downloads
*
https://www.flightgear.org/download/download-aircraft/ to my knowledge the
FGFS-official Aircraft librariesin that one i do find a 747-8i -- but not a 747-8F - but only a 747-8f!
I guess it could be that most systems do differentiate between an 8i and 8I and 8F and 8f.
Thus I guess many of us might have difficulties in finding those 2 models - just based on those little differences.
Why not (as usual) name the master-folder "747-8" and put "747-8i" and "747-8f" into that (and watch Capital and normal letters !? Like e.g. the 777 is listed!)
Maybe then those problems disappear!
The 'master-folder' doesn't matter. The problem is that the developer worked on Windows and Windows isn't case-sensitve.
In the example of the 747-8i, as jomo pointed out, we find '747-8i-set.xml' and '747-8f-set.xml'.
If we open the file '747-8f-set.xml' and look under <sim> … <model> we find <path>Aircraft/747-8i/Models/747-8F.xml</path>
Exectly there is the problem! FG trasmit this model (747-8F) over the MP-protocol.
Now, FG from other users (like jomo and other pilots) receive '747-8F' and search for '747-8F-set.xml', but can't find it.
Its possible that it works under Windows, but Linux, Mac, BSD and so on are case-sensitve, also FG is case-sensitve.
Jomo is also on Ubuntu (Linux), so it won't work and there is nothing we can do to fix it.
Best way is the developer of the 747-8 fix the filenames and pay attention on the case-sensitveness in the future.
BTW: it should also be uppercase 'I' (not lowercass 'i').
EDIT:
there is one option for users under Linux and BSD (maybe also MacOS).
Go to the directory of the aircraft ('747-8i').
Make a symbolic link to the '747-8f-set.xml' and name it '747-8F-set.xml':
- Code: Select all
ln -s 747-8f-set.xml 747-8F-set.xml
Not tested but should work.
This will not work under Windows! A link (symbolic or hard) under UNIX-like operating systems is competely different to links under Windows!