nigelmcelwee Posted December 4, 2015 Posted December 4, 2015 I tuned to klas vortac on the vhf radio 116.90 and turned radio on. Switched compass to VOR and it doesnt capture. Core i7 7700K @ 4.5 GTX 1080ti OC 11gb DDR 5 16 GB pc 3200 DDR with XMP Crucial 500GB SSD Crucial 1TB SSD Asus 31.5" @ 1920x1080 Track IR Thurstmaster pedals Thurstmaster HOTAS Warthog
Cibit Posted December 4, 2015 Posted December 4, 2015 Will try tomorow, late here. The FM homing works just included it in a mission i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64 [sIGPIC][/sIGPIC] Adding JTAC Guide //My Vid's//229th AHB
Flagrum Posted December 4, 2015 Posted December 4, 2015 (edited) http://forums.eagle.ru/showthread.php?t=135283 http://forums.eagle.ru/showthread.php?t=148083 Edited December 5, 2015 by derelor Fixed link
nigelmcelwee Posted December 7, 2015 Author Posted December 7, 2015 ahhh thanks, glad it has been reported. Makes it hard to navigate without the VOR/VORTAC. Core i7 7700K @ 4.5 GTX 1080ti OC 11gb DDR 5 16 GB pc 3200 DDR with XMP Crucial 500GB SSD Crucial 1TB SSD Asus 31.5" @ 1920x1080 Track IR Thurstmaster pedals Thurstmaster HOTAS Warthog
Havner Posted December 9, 2015 Posted December 9, 2015 I think this actually might be a separate issue. The above links are about VOR working in a inverted manner on the Black Sea map. It works only when it shouldn't, when you don't have LOS or are too low. Knowing that (and being able to make VOR work this way on BS map) I didn't manage to make 116.90 work at all in Nevada. The VOR stations might not be functional yet there. Sent from my iPad using Tapatalk [sIGPIC][/sIGPIC]
Wichid Posted December 12, 2015 Posted December 12, 2015 If you look in F10 the frequencies listed on the map are different to the editor. Like 1177.00 MHZ. Lyndiman AMD Ryzen 3600 / RTX 2070 Super / 32G Ram / Win10 / TrackIR 5 Pro / Thrustmaster Warthog HOTAS & MFG Crosswind Rudder Pedals
Havner Posted December 12, 2015 Posted December 12, 2015 (edited) 2.0 - Uh1 VOR not honing in Firstly the Huey bug itself on the Black Sea map has been fixed with 1.5.2. About Nevada the 1170.00 is not VOR frequency. I've tried frequencies taken from the game files, as provided elsewhere on this forum. Someone made a PDF with them. Like mentioned above 116.90 for Las Vegas. Sent from my iPhone using Tapatalk Edited December 12, 2015 by Havner [sIGPIC][/sIGPIC]
gospadin Posted December 12, 2015 Posted December 12, 2015 If you look in F10 the frequencies listed on the map are different to the editor. Like 1177.00 MHZ. Displayed frequences are sometimes rounded. Not sure what the exact rules are for rounding. My kneeboard frequencies (linked in my sig) are from the map but double-checked in beacons.lua, using 2.0.0 for NTTR and 1.5.1 for Caucasus. My liveries, mods, and missions for DCS:World M-2000C English Cockpit | Extra Beacons Mod | Nav Kneeboard | Community A-4E
Tarres Posted December 12, 2015 Posted December 12, 2015 1170 and similars are the equivalent frequencies of the TACAN signals. TACAN signals work in the 960-1215mhz. Example: 1170 is the frequency of the TACAN 93X It´s a bug that shows the TACAN (93X) and the TACAN frequency (1170) but not the VOR frequency (116.9) in the VORTACs of the F10 map
gospadin Posted December 14, 2015 Posted December 14, 2015 1170 and similars are the equivalent frequencies of the TACAN signals. TACAN signals work in the 960-1215mhz. Example: 1170 is the frequency of the TACAN 93X It´s a bug that shows the TACAN (93X) and the TACAN frequency (1170) but not the VOR frequency (116.9) in the VORTACs of the F10 map I thought a VORTAC was exactly that, a VOR + TACAN, that broadcasts on a single frequency that can be picked up by either type of receiver. My liveries, mods, and missions for DCS:World M-2000C English Cockpit | Extra Beacons Mod | Nav Kneeboard | Community A-4E
Tarres Posted December 14, 2015 Posted December 14, 2015 (edited) No. It's a "common facility" that houses both systems. VOR frequencies range: 108-117 .95MHz, Civilian Tacan frequencies range: 960-1215 MHz, Military only, greater accuracy, greater "confusion cone or death signal zone" Edited December 14, 2015 by Tarres
Cibit Posted December 14, 2015 Posted December 14, 2015 Quick question you clever folks may help with. Tuning to a VOR the HSI with the switch to VOR is what you use to navigate. why does the PLB locator indicator move too? (FM) i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64 [sIGPIC][/sIGPIC] Adding JTAC Guide //My Vid's//229th AHB
Cibit Posted December 14, 2015 Posted December 14, 2015 Yeah sorry I suck with acronyms :) i5 8600k@5.2Ghz, Asus Prime A Z370, 32Gb DDR4 3000, GTX1080 SC, Oculus Rift CV1, Modded TM Warthog Modded X52 Collective, Jetseat, W10 Pro 64 [sIGPIC][/sIGPIC] Adding JTAC Guide //My Vid's//229th AHB
Wichid Posted December 15, 2015 Posted December 15, 2015 Hmm what am I missing, in DCS 2.0 I tune to frequencies with the nav radio, turn it on, switch the senstitivity switch to high, flip the HSI from ADF to VOR but I can't get any life from the steering bars. I don't hear any beacon active. Am I missing something? Are you guys able to get live VOR navigation in Nevada? Lyndiman AMD Ryzen 3600 / RTX 2070 Super / 32G Ram / Win10 / TrackIR 5 Pro / Thrustmaster Warthog HOTAS & MFG Crosswind Rudder Pedals
Tarres Posted December 15, 2015 Posted December 15, 2015 (edited) The "vor bug" has been solved in the 1.5.2 Until we get a 2.0.x update, the VOR bug is still present in the 2.0 @Cibit, the Loc part of the CDI is linked to the nav system, VOR and ILS-loc shares frequencies. So the CDI works with the Nav system (VOR and ILS) and for the homing features of the radios. Sorry for my english Edited December 15, 2015 by Tarres
Recommended Posts