Thorsten, and the UFO..
Posted: Sun Aug 14, 2016 4:38 pm
..or why there are always unintended consequences of 'fixing things' upstream of the last working version.
https://forum.flightgear.org/viewtopic.php?f=19&t=29819&p=292561#p292561
Start with my post #34 and read Thorsten's responses to me. He's providing a very valuable example of https://en.wikipedia.org/wiki/Plausible_deniability. " Oh well, we didn't think at the time that this change would cause problems."
As a retrospect, back in fall/winter 2014, I started my Belfort custom scenery experiment.
I had FG 2.11.0 something installed at the time, and the UFO was my go-to tool for making this new, (old) historical aerodrome a reality. One thing led to another, 'til I had the misfortune of one day wanting the new bells and whistles of 3.4. So I installed 3.4 and wanted to use the UFO to adjust and add to the scenery. Well the file/object select GUI window for the UFO had been disabled by the pointy heads at FG Development Corp, because it was imagined that there was some sort of some "possibility of misuse" security problem, and they 'fixed' it in the fgfs.exe coding for any instance of this possible 'misuse' of a work and time saving GUI window.
I know a lot of the UFO's functions are now more streamlined through WED and other TerrGear fixes, but with my liking my old school approach to model addition, ( I don't think that Corcieux would have been possible with TerraGear or WED...), and also for road rebuilding for the race courses Marc Kraus has done, and for my own custom roads, the UFO is the bee's knees, especially when you need to change in midstream the scenery folder the files are pulled from. As of now and, at least from what I can tell, (i.e. FG 3.4.0..) the UFO is only able to place model files by opening the Advanced tab in FGRun and doing a --prop XXXXXXXX edit to change the default model folder. Yup, really sucks.
So I'm considering a reinstall of 2.8 as a revert to use this function, which is BS.
I'm also awaiting a replay from Thorsten about if it's possible to revert the 2016.1 fgfs.exe with a hex editor, so I can have the UFO back to working again. Frankly, I kinda think I'll be told to suck an egg.
https://forum.flightgear.org/viewtopic.php?f=19&t=29819&p=292561#p292561
Start with my post #34 and read Thorsten's responses to me. He's providing a very valuable example of https://en.wikipedia.org/wiki/Plausible_deniability. " Oh well, we didn't think at the time that this change would cause problems."
As a retrospect, back in fall/winter 2014, I started my Belfort custom scenery experiment.
I had FG 2.11.0 something installed at the time, and the UFO was my go-to tool for making this new, (old) historical aerodrome a reality. One thing led to another, 'til I had the misfortune of one day wanting the new bells and whistles of 3.4. So I installed 3.4 and wanted to use the UFO to adjust and add to the scenery. Well the file/object select GUI window for the UFO had been disabled by the pointy heads at FG Development Corp, because it was imagined that there was some sort of some "possibility of misuse" security problem, and they 'fixed' it in the fgfs.exe coding for any instance of this possible 'misuse' of a work and time saving GUI window.
I know a lot of the UFO's functions are now more streamlined through WED and other TerrGear fixes, but with my liking my old school approach to model addition, ( I don't think that Corcieux would have been possible with TerraGear or WED...), and also for road rebuilding for the race courses Marc Kraus has done, and for my own custom roads, the UFO is the bee's knees, especially when you need to change in midstream the scenery folder the files are pulled from. As of now and, at least from what I can tell, (i.e. FG 3.4.0..) the UFO is only able to place model files by opening the Advanced tab in FGRun and doing a --prop XXXXXXXX edit to change the default model folder. Yup, really sucks.
So I'm considering a reinstall of 2.8 as a revert to use this function, which is BS.
I'm also awaiting a replay from Thorsten about if it's possible to revert the 2016.1 fgfs.exe with a hex editor, so I can have the UFO back to working again. Frankly, I kinda think I'll be told to suck an egg.