WoodSTokk wrote in Fri Jan 11, 2019 7:20 pm:Yes, i propose you shoud use the official hanger from FG and this is FGaddon.
You should NOT use the FGMEMBERS hangar! It is not the official FG hangar, ist often outdated and aircrafts include sometimes material that is questionable if it comes to the licence.
I have no idea how you define the master-library - I would always start on the Home-Page of the program in question! Thus:
--->
http://home.flightgear.org/---> Download
---> Download Aircraft (or Main Prog or Scenery or source etc.)
---> Official Aircraft --->
http://mirrors.ibiblio.org/flightgear/ftp/Aircraft/I do agree that in this library there never will be all the most beautiful (newest, looking, functional, etc.) models -- BUT that is the base if you talk about an FGFS home base. But nobody wants to restrict the "designer" from developing always the best of the best outside of that! That engineering wish is now pretty good supported by the new "fgfs launcher", that allows every user to define from which library he wants to get the newest updates for the model(s) he uses.
BUT the designers now have to be aware of 3 situations, based on the fact that:
If anybody sees a model on his user-screen - he always
a) sees that
visible-model as he downloaded it (maybe years ago!)
b) being controlled by the new
control-model from far away via MP!
Thus: If a designer changes his model, the "visual model" (on the user-disk) may now not match the new "control model" (on the designer disk)!! Thus we have 3 possibilities:
1) The designer changes the model to be used just by him-selves -->> no problem at all (but the model just may not be visible to others!)
2) The designer will use that model together with some friends - then he might distribute that to all his friends --> again no problem at all because all of them have the same "visible+control" parts (it just may not be visible to others)
3) If you (and friends) want to bee seen by the whole community, you must remember that all others will only see their locally installed model --> CONTROLLED by your controls (via MP). And that may be incompatible!
And that is the issue I have with the designers that distribute new models into any library - without caring about the "old versions" still being used! In EDDF-Triangle I make movies of every model coming in. And based on the above, those incoming models may use different "control-models" than my "visual-model" on my disk - receiving that controls from the outside (may they be older or newer!)!
Please accept that it is not possible to have multiple models with the same name but different structure etc. on one local disk!
Right now I often noticed that problem (as ATC) with 2 models:
- 777 that shows some minor difference in outside functions (e.g. wheels: I would not care - but the pilot does!)
- A320 some version of that model appears on radar + screen - others only on radar
etc.
That is why I say: For events the engineers must find a solution for designing their unique models so, that they have one "visible model" that can be controlled by any newly designed "control model". So all FGFS-member just need to load that common "visible model" that can be controlled by all versions of the "control model".
And pls keep in mind: Some users are satisfied with the model they have - they do not care to consonantly update their models!
Pls do not shoot me - I know how hard world-wide engineering is!