Thanks Hooray, that actually works, but I really would like to know why the other quit working?
EDIT prior to posting:
The reason for changing to this system and getting rid of the old --console option, was to make the error reporting (STDERR) work properly.
Alan, a much quicker and more convenient method is to create a bat file with the following.
- Code: Select all
"C:\Program Files\FlightGear 2016.3.0\bin\fgfs.exe" --launcher
Obviously using whatever options you want or need.
Can you point out the commit that changed the old behavior?
I don't understand how removing an optional startup parameter was needed to make error reporting work? Maybe to make it work if someone was using that option, but that seems unnecessary to limit options for a subset of potential error reports.
Thank you for verifying that it is a change in the code.
Also I have one other problem. All my osm2city scenery no longer works. It acts like it recognizes it, It's set up identical to the way I did it before. It just doesn't show up in the scenery.Console shows the correct paths- Code: Select all
F:\FlightGear>"C:\Program Files\FlightGear 2016.3.0\bin\fgfs.exe" --launcher
option:fg-scenery = F:/fgdev/scenery/kansas/output
option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Butler
option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Douglas
option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Greenwood
option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Lyon
option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Sedgwick
option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Shawnee
option:terrasync-dir = C:\ProgramData\flightgear.org\TerraSync
terrasync-dir = "C:/ProgramData/flightgear.org/TerraSync"
aircraft-search-paths =
F:/FlightGear/Custom Aircrafts
scenery-search-paths =
F:/fgdev/scenery/kansas/output
F:/fgdev/scenery/kansas/output/Terrain
F:/fgdev/scenery/kansas/output/Objects
D:/FlightGear/osm2city/Kansas/custom/Butler
D:/FlightGear/osm2city/Kansas/custom/Butler/Objects
D:/FlightGear/osm2city/Kansas/custom/Douglas
D:/FlightGear/osm2city/Kansas/custom/Douglas/Objects
D:/FlightGear/osm2city/Kansas/custom/Greenwood
D:/FlightGear/osm2city/Kansas/custom/Greenwood/Objects
D:/FlightGear/osm2city/Kansas/custom/Lyon
D:/FlightGear/osm2city/Kansas/custom/Lyon/Objects
D:/FlightGear/osm2city/Kansas/custom/Sedgwick
D:/FlightGear/osm2city/Kansas/custom/Sedgwick/Objects
D:/FlightGear/osm2city/Kansas/custom/Shawnee
D:/FlightGear/osm2city/Kansas/custom/Shawnee/Objects
C:/ProgramData/flightgear.org/TerraSync
C:/ProgramData/flightgear.org/TerraSync/Terrain
C:/ProgramData/flightgear.org/TerraSync/Objects
Looks correct in the log- Code: Select all
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2338: option:fg-scenery = F:/fgdev/scenery/kansas/output
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2338: option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Butler
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2338: option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Douglas
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2338: option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Greenwood
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2338: option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Lyon
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2338: option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Sedgwick
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2338: option:fg-scenery = D:/FlightGear/osm2city/Kansas/custom/Shawnee
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\options.cxx:2338: option:terrasync-dir = C:\ProgramData\flightgear.org\TerraSync
general:3:G:\Jenkins\workspace\Windows-nightly\flightgear\src\Main\fg_init.cxx:676:scenery-search-paths =
F:/fgdev/scenery/kansas/output
F:/fgdev/scenery/kansas/output/Terrain
F:/fgdev/scenery/kansas/output/Objects
D:/FlightGear/osm2city/Kansas/custom/Butler
D:/FlightGear/osm2city/Kansas/custom/Butler/Objects
D:/FlightGear/osm2city/Kansas/custom/Douglas
D:/FlightGear/osm2city/Kansas/custom/Douglas/Objects
D:/FlightGear/osm2city/Kansas/custom/Greenwood
D:/FlightGear/osm2city/Kansas/custom/Greenwood/Objects
D:/FlightGear/osm2city/Kansas/custom/Lyon
D:/FlightGear/osm2city/Kansas/custom/Lyon/Objects
D:/FlightGear/osm2city/Kansas/custom/Sedgwick
D:/FlightGear/osm2city/Kansas/custom/Sedgwick/Objects
D:/FlightGear/osm2city/Kansas/custom/Shawnee
D:/FlightGear/osm2city/Kansas/custom/Shawnee/Objects
C:/ProgramData/flightgear.org/TerraSync
C:/ProgramData/flightgear.org/TerraSync/Terrain
C:/ProgramData/flightgear.org/TerraSync/Objects
I'm stumped?LATE EDIT:
Now I suppose I could try to add the additional/optional scenery to the bat file switches, but again, what changed in the launcher to cause this no longer to work especially as the launcher actually has a place for optional scenery params.I guess using the --console option was causing failure. I forgot to remove it from the above bat file also and it was causing the osm2city load failure.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q