• 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.

FSXA How can I exclude a stock VOR?

Messages
217
Country
azerbaijan
The latest posts regarding this type of exclusion date back to 2009. Is there any progress in ADE re: excluding FSX default navaids?
The latest beta I'm using doesn't mention navaids as objects eligible for exclusion. The closest is library objects but "excludeLibraryObjects="TRUE" returns nothing in FSX as far as the navaids are concerned.

I understand that navaids are sort of glued to airways, hence moving/relocating them or changing their properties is not recommended. But if I cannot exclude them, what else can be done to completely disable or relocate the stock VOR?

You can also see on the image that VOR sits just on the bottom end of Rwy30 and makes the whole picture ugly...

Thanks!
 

Attachments

  • Capture-1.jpg
    Capture-1.jpg
    237.2 KB · Views: 413
You cannot exclude stocknavaids. Microsoft did not give us the tools to do that. you might be able to move it a bit but that it is also not recommended. This is not the visual navaid however. You can remove any visual object associated with the Navaid in ADE by just deleting it. I am not sure what you mean by makes the whole picture ugly. It is not going to be visible in the sim on the ground.
 
It is possible to delete stock navaids etc, (although not using ADE), by decompiling the appropriate default scenery bgl, deleting the xml navaid entry and then recompiling the bgl. If you do this though you will break airways which rely on and are tied to that navaid, potentially causing CTDs and loss of builtin flight planner functionality and maybe other things as well :/

I havent tried it but it should theoretically be possible to replace the navaid with a waypoint of your choice instead, leaving you with working airways but without the navaid, as long as you replaced every reference to that navaid in every route with one for your new waypoint.

All this is of course predicated on the navaid in question being non-existent in rl, otherwise why would you want to delete it?!
 
Thank you, guys!

Well, the thing is the navaid in question sits just on the runway, as shown on the image. Being aware of what you've said above, I don't really want to touch the stock items and instead am interested in exploring the avenues and existing tools that would help to solve this problem.
I could add a custom navaid at a different location but I'm afraid this won't help because the GPS will still show duplicate navaids with the same frequency, name and ID (I wouldn't change real-world properties of the navaid) even if the stock navaid will be invisible in the sim.
 
The default VOR is IGR. You can remove the model with a simple exclusion rectangle (Library Objects). (You can't use <Delete> since there is no default airport from which to import).

 
bina

That airport does not look like a stock airport and one you are adding.

Is that VOR the IGR at Igarka, Russia?


EDIT-----------------------------

George beat me to it
 
Yes, it is. FSX doesn't have this airport but it nevertheless includes the VOR though located improperly.


Sent from my Galaxy S4 using Tapatalk
 
bina

This picture shows the actual location of the IGR VOR in respect to the runway (+ sign).

fsscr010.jpg


If you have the ADE Pro Key you can move the VOR radio NAVAID (blue symbol) to the correct location and then drag the library scenery object to the same location.

FSX allows a small amount of navaid movement before the navaid will duplicate. Also there is no Victor airway attached to the VOR in the database. The Airways are all Jet type and use the IGR Intersection WAYPOINT which does not need to be moved.
 
Hi,

As mentioned above, you can move the VOR library object on the runway to its correct position using ADE (it is not the blue polygon, but should be a yellow rectangle) - the very small error in the location of the VOR shouldn't matter for most purposes.
 
It is possible to delete stock navaids etc, (although not using ADE), by decompiling the appropriate default scenery bgl, deleting the xml navaid entry and then recompiling the bgl. If you do this though you will break airways which rely on and are tied to that navaid, potentially causing CTDs and loss of builtin flight planner functionality and maybe other things as well :/

I havent tried it but it should theoretically be possible to replace the navaid with a waypoint of your choice instead, leaving you with working airways but without the navaid, as long as you replaced every reference to that navaid in every route with one for your new waypoint.

All this is of course predicated on the navaid in question being non-existent in rl, otherwise why would you want to delete it?!

I have to apply the warning that we do not ever recommend modifying stock files. People do it and that is their privilege providing they don't distribute such changes or provide an easy way to restore the stock files. As Kevin says removing a stock fix is likely to mess up routes and also potentially approach code and may indeed break things rather badly
 
Im currently working on the O'hare OMP and while doing so, the stock o'hare vor+dme was in the middle of a taxiway. I simply moved the whole airport using the tool built in ade (using the feet distance move instead of coordinate option). Every object including buildings, taxiways, runways, signs were all moved making the vor+dme look like it was the only thing that moved. Now the VOR+DME is right where it should be relative to where the taviways, ect are.
 
Back
Top