Board index FlightGear Support Flying

Aircraft-model-MP-compatability

Controlling your aircraft, using the autopilot etc.

Aircraft-model-MP-compatability

Postby jomo » Mon May 29, 2017 9:27 am

At the 4-times-a-week events at EDDF we experience more and more that models suddenly are not visible any more, i.e. they just show up as blue/yellow gliders or even cause a FGFS-crash for other MP-users - who may have that same model installed from a different "hangar". I myself know very well how difficult it is to agree worldwide on ONE unique model - every engineer wants to improve "his" baby without getting bothered with "compatibility between versions". But on the other hand we want that our "fantastic, new, and better Baby" is seen and used by others (e.g. via MP). But that is not possible if there is not at least one common MP-source for all models of that type. Sorry enough: In the meantime there are over 50 different hangars in FGFS (see http://wiki.flightgear.org/FlightGear_h ... e_releases) where there may be different versions of same models - thus pilots may be using same/different models and never notice the reason why they cannot see the other "same" model! Anyhow: You cannot expect any FGFS-user (or ATC) to reload models according to the unique model that a unique user is flying! So we must find a way to ensure that every MP-user can visualize every Model in his area - independent of any "hangars".

I am not sure how much we can "standardize" the design-control inside FGFS - but my suggestion would be: Use the
* http://mirrors.ibiblio.org/flightgear/ftp/Aircraft/ as a base
+ https://github.com/FGMEMBERS for upgrades that are controlled MP-compatible
- everything else may be used by the designer himself in his own environment
Thus we could achieve an enjoyable get-together in MP - without long discussions about who's model is the correct one.

For the EDDF events I will in future: Whenever I notice a blue yellow I try to find an update in the FGMEMBERS:
- if I find an update there I will reload
- if it "crashes" other MP-users I will delete it out of my library (now about 400 models!). (Of course that then makes all models of that type to blue/yellows - independent of the hangar it comes from!)

I will not try to find it in any other hanger because the next guy coming might need it from again another hangar! (And I will not daily search 50 hangers for 400 model-changes!). Because of that I already have deleted from my list: A320neo, A330-300, F14b, F-15, TU154B, TU154B-MOD (see list on top of table http://www.emmerich-j.de --> EDDF- Triangle Movies).

Does anybody have a better idea how to solve that MP-incompatibility-problem?
jomo / ATCjomo + EDDFjo + EDDFjo1 + EDDFjo2
ATC at EDDF Fr,Sa,Su,We from 20:00 to 24:00 CET/MEZ., see http://www.emmerich-j.de
User avatar
jomo
 
Posts: 1000
Joined: Thu Feb 12, 2009 7:46 pm
Location: Mainz, Germany
Callsign: jomo EDDFjo1+2
OS: UBUNTU 18.4

Re: Aircraft-model-MP-compatability

Postby Thorsten » Mon May 29, 2017 9:45 am

* use the planes from FGAddon, because that's where the vast majority of users downloads from
* take care to merge any additional work for aircraft back into FGAddon rather than keep it in your own repository

After all, FG's philosophy of trying to merge all changes into centralized repositories rather than produce a gazillion of mutually incompatible addons isn't there for nothing.
Thorsten
 
Posts: 12490
Joined: Mon Nov 02, 2009 9:33 am

Re: Aircraft-model-MP-compatability

Postby jomo » Mon May 29, 2017 10:49 am

Thorsten wrote in Mon May 29, 2017 9:45 am:* use the planes from FGAddon, because that's where the vast majority of users downloads from
* take care to merge any additional work for aircraft back into FGAddon rather than keep it in your own repository

Well - yes - I saw that - and agree. And I do not see a difference to my proposal: Use the Formal Library -- but if it is not there (e.g. it is still in test) I only search one single "Development" library - not 50.

BTW: Is there anywhere described how a Hangar-Designer gets his model into the FGAddon - and why he should? I was asked that several times. Maybe on http://www.flightgear.org/download/download-aircraft/ there could be pointed out more realistic what the difference between FGFS-lib and hangars is - especially for pilots wanting to use "hanger-models" during MP-events! To most people that listing of "formal" and "hangar" looks to most people as "one as good as the other".

Right now I have at least once a week the problem that a guy believes he has the newest/best model - but often he even does not know were he has it from. I would like to push pilots and designers more into a more formal way of release - means into your direction! That would help a lot for MP-events.
jomo / ATCjomo + EDDFjo + EDDFjo1 + EDDFjo2
ATC at EDDF Fr,Sa,Su,We from 20:00 to 24:00 CET/MEZ., see http://www.emmerich-j.de
User avatar
jomo
 
Posts: 1000
Joined: Thu Feb 12, 2009 7:46 pm
Location: Mainz, Germany
Callsign: jomo EDDFjo1+2
OS: UBUNTU 18.4

Re: Aircraft-model-MP-compatability

Postby Thorsten » Mon May 29, 2017 11:01 am

BTW: Is there anywhere described how a Hangar-Designer gets his model into the FGAddon - and why he should?


http://wiki.flightgear.org/FGAddon

As to the why - simply put, because what's on FGAddon gets taken care of by the FG developers in case of a core change that causes breakage - what's elsewhere just breaks. For the same reason, bug reports are only accepted by the FG developers for FGAddon planes. Additional eyes watching out for license violations and wasteful coding.

That sort of thing. In addition to your MP-related reasons.
Thorsten
 
Posts: 12490
Joined: Mon Nov 02, 2009 9:33 am


Return to Flying

Who is online

Users browsing this forum: No registered users and 4 guests