I need to correct you in something you misinformed in the Curtis' Forum
You implied that FGMEMBERS' Aircrafts only work for 3.7.
That is just not quite true.
1. FGMEMBERS has [for many of its aircrafts] released versions for 3.4 and 3.6 (even thou FG never released 3.6)
Go to the repository page, click on "releases"
example
https://github.com/FGMEMBERS/737-200
https://github.com/FGMEMBERS/737-200/releases
Downloading the corresponding release (example FG3.2) will get you a "past" aircraft, that was known to be functional on 3.2 (and it does not have any of the bling of newest development!)
2. Of almost 700 aircrafts, only a handful (maybe up to 20) have code that requires a higher version, so it is tipically not a bad idea to just try the tip of the master branch for a more advanced aircraft. It might just work; If it does nt there is no problem for the user to ask. We may advise to get a released (older) version matched, (only if) in case that new code is incompatible
3. FGDATA with submodules. A release branch exists for FG 3.4 and FG 3.6 that permits getting the aircrafts existing / working on the release date (FG 3.4) or freeze date (FG 3.6). This way, FGDATA with submodules can be used to install/deinstall functional aircrafts, without following the development tip.
So, really, FGMEMBERS is more compatible with FG than what you think, and lead others to believe
Why not for FG 2.12; 3.0 and 3.2?
There are nt releases of FGMEMBERS aircrafts before 3.4, because FGMEMBERS was created while FG was versioned 3.2
Although possible to use the git history to backtrack older aircraft versions, it really much cumbrsome than helpful.
Just clarifying...
(ask if in doubt)
I-COL
