nsproles Posted April 4, 2021 Share Posted April 4, 2021 (edited) ESL VOR DME 108.100 cannot be used as a VOR which is very misleading. Shouldn't it be then shown as a DME? Or am I not understanding something? No, I think that your understanding is correct. In a perfect world, MSFS would show it as a DME only for non-military users, but it seems that MSFS does not necessarily make that distinction. On other sites, there are similar comments that something shown as a VOR in MSFS only works as a DME; presumably because it is a TACAN. One suggestion I have seen is that, when flight planning, to only use VORs that are shown as such on other applications, e.g. Sky Vector or Little Navmap. What is interesting is that MSFS performs correctly in flight in not recognizing the TACANs as VOR, while (incorrectly) showing them as VORs for flight planning purposes. Edited April 4, 2021 by nsproles Windows 11, GeForce GTX 1660ti; 3.60 gigahertz AMD Ryzen 5 3600 6-Core; Kingston SA2000M81000G SSD; 16 gb RAM; CH yoke; Saitek pedals; Three monitors; TrackIR 3. Link to comment Share on other sites More sharing options...
jparnold Posted April 4, 2021 Author Share Posted April 4, 2021 One suggestion I have seen is that, when flight planning, to only use VORs that are shown as such on other applications, e.g. Sky Vector or Little Navmap. What a great suggestion. Actually thinking about it I did see a tutorial video on VOR flights which used Sky Vector. I will use that in future. I have learned a lesson - don't rely on MSFS ! :( John Gigabyte Z390 UD Intel Core i7-9700K 3.60 Ghz Dual 16Gb DDR4 2666 Gigabyte RTX2060 OC 6GB 2 X 256MB SSD drives 1 X 500GB HDD Windows 10 64bit Home Logitech Extreme 3D Pro joystick Link to comment Share on other sites More sharing options...
jparnold Posted April 6, 2021 Author Share Posted April 6, 2021 (edited) In a perfect world, MSFS would show it as a DME only for non-military users, but it seems that MSFS does not necessarily make that distinction. I don't want to labor on this but MSFS shows TACANs as VOR DME yet treats them as a DME (the CDI does not work when the frequency is correct and as such appears to only use them as a DME). That is they 'half' treat them as a TACAN. ALSO the SYMBOL they display is that of a VOR (see below). If MSFS is supposed to be a true flight simulator then surely this needs to be changed so that beginners like me don't get 'trapped'. Edited April 6, 2021 by jparnold John Gigabyte Z390 UD Intel Core i7-9700K 3.60 Ghz Dual 16Gb DDR4 2666 Gigabyte RTX2060 OC 6GB 2 X 256MB SSD drives 1 X 500GB HDD Windows 10 64bit Home Logitech Extreme 3D Pro joystick Link to comment Share on other sites More sharing options...
LanPartyPizza Posted August 6, 2021 Share Posted August 6, 2021 If MSFS is supposed to be a true flight simulator then surely this needs to be changed so that beginners like me don't get 'trapped'. Hi, I think this is a bug. Lets see if we can repeat these across platforms? I am flying from YARM and tuning Nav 1 to 112.60 with no success. No audio signal, no update to VOR/OBS. This is the correct frequency in MSFS and on SkyVector but in game there is no result. Flying into YMLM I also get nothing on 113.3 which is what SkyVector puts as a NavAid (don't know what type, I'm not familiar enough with thing and this is a military airport used for commercial). However MSFS2020 reports a Localizer DME Navaid on Frequency 110.500 Mhz. Identification is IWM. This one works in game but this navaid is not shown on SkyVector. So, after much frustration, I think the input data MS has used is trash. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now