- Messages
- 233
- Country
-
Just need the Patrick's magick touch then...They can be extracted
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
Just need the Patrick's magick touch then...They can be extracted
Thanks! Quick and dirty is fine! What I do is I just get the XML from the code generated by your tool and paste into the airport I'd be working on. Getting the XML for the taxi signs would be great.Hi all
Catching up on all the posts (for some reason, I did not subscribe to the notification process).
Anyway, I'll work on the taxisigns because, yes, they can be extracted, plus adding some configuration options.
I'll let you know when I'll have something new to share.
But don't forget that this app is a quick-and-dirty tool to help edit existing airport
Hi DickA suggestion to help Steam users would be to alter the <location>
%AppData%/Microsoft Flight Simulator/UserCfg.opt
The last line of the OPT file (TXT file) is the <location> of the MSFS data
For steam, the directory of the files within the data is <location>\Official\Steam\
"D:\MSFS\Official\Steam" in my case. I believe <location>\Official\OneStore\ is the directory for the MSStore version.
No, it's not found.Hi Dick
You mean that with version 1.0.0.3 of the Airport2Project, the path is still not found for the Steam version ?
According to Zendesk (https://flightsimulator.zendesk.com...-D-drive-instead-of-the-C-drive-for-instance-),A suggestion to help Steam users would be to alter the <location>
%AppData%/Microsoft Flight Simulator/UserCfg.opt
The last line of the OPT file (TXT file) is the <location> of the MSFS data
For steam, the directory of the files within the data is <location>\Official\Steam\
"D:\MSFS\Official\Steam" in my case. I believe <location>\Official\OneStore\ is the directory for the MSStore version.
Yep. C:\Users\dickl\AppData\Roaming\Microsoft Flight Simulator in my case. Also %AppData%\Microsoft Flight Simulator gets me there.According to Zendesk (https://flightsimulator.zendesk.com...-D-drive-instead-of-the-C-drive-for-instance-),
the location of the UserCfg.opt file for Steam users is : C:\Users\YourUsername\AppData\Roaming\Microsoft Flight Simulator
Can you confirm it ?
ok, I changed the path to <location>\Official\Steam\ when the UserCfg.opt is found in the Steam folder.Yep. C:\Users\dickl\AppData\Roaming\Microsoft Flight Simulator in my case. Also %AppData%\Microsoft Flight Simulator gets me there.
The 'breizh' prefix can be changed in the generated xml filesAlright, after a little trial and error, got it to work. Looking in the EG07_Scene.xml I do see runways, three as expected, so I assume Patrick must have meant something else by "jetway".
I also note the use of the "breizh-airport" that others have and assume that this can be changed. For my purposes, something like "401st_WWII_EG07_" or similar.
Looks like the first thing for me to try is to increase the length of the shortest runway since I know it's was much longer in the past.
Let the learning curve continue! (And thanks for the tool.)![]()
Glad it helped!This tool is amazing. Was able to fix all my home airports taxiways, signs, removed a tree from the taxiway and a few other minor updates. Only thing I can't seem to fix are the comms names. I doesn't extract for some reason.
Is that option not available?
Comms would be nice... The one I'm working on is CYOW Ottawa. Thanks again for this utility, it's a great help!Glad it helped!
The Comm option is not available...yet. Now if you give me the name (and path) of one airport that could be used as a test airport, I'll be glad to implement the Comms
See https://www.fsdeveloper.com/forum/attachments/airport2project_1_0_0_4-zip.68619Comms would be nice... The one I'm working on is CYOW Ottawa. Thanks again for this utility, it's a great help!