• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    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.

I just edited an approach; how do I save to FSX?

Messages
7
Country
unitedstates
I saved the XML file to desktop. Trying to Compile but getting error message "ERROR: Unable to find BglComp.exe"

Is there something I am doing wrong?
Please help, so changes can get saved to FSX and I can see the changes while flying the simulator.

Thanks.
 
Are you doing this by hand or are you using an application to do it?
 
Thank you for your response.
I am using FSX Planner. I attached a screen shot.
I have no idea how to compile any edits that I do. Please help.
 

Attachments

I think we need the xml file please. That gives no indication of what the error is. If you post the XML file or email it to me (jon AT fsdeveloper.com) then I will take a look at it for you.
 
OK that seems to indicate that FSX Planner cannot find BglComp although you have set the path.

I have your xml file and will check it.
 
I managed to fix the xml to get it to compile. I guess you are re-writing the approaches to this airport? since the stock airport does have approaches.

Unfortunately there are a number of problems - although the approaches might compile they will not work as things stand. for Example this is your R09 ILS

screenshot_20.png


The initial problem is that you must start the approach legs with an IF. Next the racetrack patterns do not have a time or distance value which is why they appear as little circles.

The other approaches have similar problems

This is not the issue shown in your picture of the error since that seems to say that BglComp.exe cannot be found
 
I have no idea what to do on that screen. That path was there already (with SDK in it) so I tried new paths. I have no idea what the two path windows are for.
Thanks for your help!
 
The changes I made were to "try" to make ATC vector me into the Final Approach Fix instead of the Initial Approach Fix (which is too far out-ATC makes me go way past the IAF so I wanted to start approach closer). I changed TOBBY to Type: HA just to get it our of the way hoping HA and Fix Type: ---- would have ATC ignore TOBBY altogether.
As long as ATC vectors me to WOLFF I am happy.
Hope that helps.
 
Should I delete TOBBY? I don't need it.
If yes then after deleting it and saving the XML, how do I compile it successfully? Thanks. Oh by the way, I am working on my instrument rating. I want to eliminate ATC from sending me ridiculously far out to align me with approaches. What am I doing wrong?
 
OK the truth is that writing approach code is not an easy task. The best person to help you is Jim Vile. Perhaps he will spot this thread and chip in with some practical help.

I am not running FSX Planner so I am not sure what to suggest on the compiler error. Certainly the compile would also fail in any case since you have several missing entries in your approach xml.
 
Back
Top