MSFS runwayDelete command not working

[jahurz93]

Hi

Was just wondering if anyone would help. Previously i have created a basic airport(WMGK) that did not exist on MSFS on SU10. Fast forward to SU11 it seems asobo has reinstate this airport but only the runway and it is not overriding my scenery. The runway asobo provide is inaccurate. Using the MSFS SDK and using the deleteallrunway command did not work the default runway would still be there. I restart the entire project from scratch and that didnt remove the runway as well. Is this a new bug with the SDK? My other projects the delete function always work but not for this specific scenery.

Scenery in question

Gong Kedak Airbase » Microsoft Flight Simulator

✓ Gong Kedak Airbase is a Microsoft Flight Simulator 2020 mod created by chinjh. Download for free to enhance your experience in MSFS 2020.

flightsim.to

Regards

 

[=rk=]

Ok no problem. Before, your project was an original airport. Now, your project must be structured as a "modification," of an existing airport. Once you establish that and bring this existing airport into your project, you should be able to replace the faulty runway.

 

[jahurz93]

Ok no problem. Before, your project was an original airport. Now, your project must be structured as a "modification," of an existing airport. Once you establish that and bring this existing airport into your project, you should be able to replace the faulty runway.

I have started everything from scratch as a new project and override WMGK ICAO which is now identified compared to before and i selected the the deleteallrunway MSFS SDK function. However when i build the package and setup myself on the airport the double runway runway is still there. I might be a bit inexperience with the SDK but could you explain how to structure the modification?

 

[rhumbaflappy]

There is no default MSFS WGMK. You have an addon conflict. I would rename my Community folder as CommunityOLD, and create a new (empty) Community folder, and copy the addon there. Restart MSFS.

 

[jahurz93]

There is no default MSFS WGMK. You have an addon conflict. I would rename my Community folder as CommunityOLD, and create a new (empty) Community folder, and copy the addon there. Restart MSFS.
View attachment 85192

Thanks for double confirming. Guess its back to trying each add-on one by one.

 

[jahurz93]

It has been narrowed down to navigraph airac 2211. Is there a possible fix without removing navigraph at the moment?

 

[=rk=]

Considering the fact that Navigraph is a navigational aid provider that charges subscribers based on its reputation of accuracy and Navigraph is not required to use your addon, I'd say the choice is clear. Having just completed my own addon in that part of the world, I can observe that simulating reality in a simulator that focuses on "the major routes," can be especially challenging. I'd had to abandon an entire location, a different island, because an MSFS update introduced a terrain irregularity I could not remove, that I could not even get a support report response over.

 

[rhumbaflappy]

It has been narrowed down to navigraph airac 2211. Is there a possible fix without removing navigraph at the moment?

It seems odd that Navigraph would include runways... but if MSFS doesn't include the runway as default, then what other choice would they have? IF there is a runway, there should be a bgl to create that runway. It should be excludable. The Community folder loads packages alpha-numerically. Make sure your package is loaded after the Navigraph bgl that contains the unwanted runway, and then delete all runways in your package.

Using BGLViewer, I see you have not deleted taxiways and aprons. Is it possible what you are seeing is an underlying apron ot taxiway? If so, you may be successfully deleting the runway, but not the apron that underlies it, and that give the appearance of a double runway.

 

[jahurz93]

It seems odd that Navigraph would include runways... but if MSFS doesn't include the runway as default, then what other choice would they have? IF there is a runway, there should be a bgl to create that runway. It should be excludable. The Community folder loads packages alpha-numerically. Make sure your package is loaded after the Navigraph bgl that contains the unwanted runway, and then delete all runways in your package.

Using BGLViewer, I see you have not deleted taxiways and aprons. Is it possible what you are seeing is an underlying apron ot taxiway? If so, you may be successfully deleting the runway, but not the apron that underlies it, and that give the appearance of a double runway.

I've gone through navigraph's forum it seems there is a priority listing issue on content.xml and the workaround is to reinstall navigraph database using nav data client and then only calling out all the deletefunctions using the msfs sdk with the project.