#2032 Launcher Won't Launch Float Versions of DeHavilland Aircraft
[code]FlightGear version: 2017.3.1
Revision: none
Build-Id: none
Build-Type: Dev
FG_ROOT=/usr/share/flightgear
FG_HOME=/root/.fgfs
FG_SCENERY=/root/.fgfs/TerraSync:/usr/share/flightgear/Scenery
SimGear version: 2017.3.1
OSG version: 3.4.1
PLIB version: 185 [/code]
FG launcher will not permit float versions of the DeHavilland DHC2 Beaver, DCH3 Otter or the DHC6 Twin Otters. Float option simply isn't there, and cannot be defined in Settings. Note, this is not an aircraft issue, but a launcher issue. Calling up Launcher, only Wheels versions of these planes are available, when a float version should also appear in the launcher. I tried aircraft=dhc2f in Settings, and Launcher ignored it and launched wheeled version instead; wonderful if you try this on a lake! Yet the Aircraft package ships with a float version, so why is that version not being read?
I'm able to select float-base aircraft such as the DHC6 floats and otter with floats using my development build. Are you able to test that version (or 2018.2.x?)
FlightGear version: 2017.3.1 -- Floats don't work in launcher.
You said:
"Are you able to test that version (or 2018.2.x?)"
Test? my test is whether it works or not with my current version, and it
doesn't, which is why I filed the bug report. I'm not using 2018.x.x yet,
I'm still on FC 27 and won't be upgrading for some time. Fedora repository
doesn't have 2018.x.x listed, and with the complexity of FG now, I'm not
compiling manually. Wouldn't it be easier to simply write a patch and add
it to the repository so this basic function is included?
On Mon, Jul 2, 2018 at 4:53 PM, James Turner <jmturner@users.sourceforge.net
Related
Tickets:
#2032I've GIVEN you the info I have! You're a Dev, now it's up to YOU to figure
it out, why the hell are you coming back to ME?! I'm not a geek! I've
reported what I've found. By the sounds of this you're not going to do
anything, are you?! For chrissakes, fire up a copy of
2017.3.whatever and test
it for yourself! That way, you're getting first hand information and
not relying on an unreliable non-geek to provide you with he knows not what
you want!!
Cya!
On Tue, Jul 3, 2018 at 2:01 AM, trennor trennor@users.sourceforge.net
wrote:
Related
Tickets:
#2032Hi Trennor,
Stepping in here as I think you are over-reacting to what was a
straightforward question. It’s quite OK to explain that you can’t check
against the latest version. What is not OK is swearing at volunteer
developers.
There are only a small number of developers of FlightGear and the more help
you can provide the more effective they can be. For example if you were
able to reproduce the problem on 2018.3 then we’d know that it hasn’t been
fixed already. However if it was fixed already in 2018.3 (as James can’t
reproduce himself) then we would know to look for an existing fix. Plus
you’d have it working :)
BTW - I don’t think we have way to patch the Fedora repository. And we
rarely back-apply fixes to old releases.
Hopefully this will explain the reason for James’s question.
Best regards,
Stuart Buchanan
On Tue, 3 Jul 2018 at 09:33, trennor trennor@users.sourceforge.net wrote:
Related
Tickets:
#2032i cannot confirm this bug in the latest development code for FG 2018.3.0... launcher development is moving too fast for problems reports related to it in older FG versions... FG 2017.3.1 is 10 months old and there's been two more releases since then... even the latest 2018.2.1 release has bugs in the launcher that are already fixed in the development code...
Since this cannot be reproduced with the most recent releases, we assume that this is fixed in the meantime. Please re-open if proven false.