Balzarog Posted February 1, 2018 Posted February 1, 2018 Just ran the first mission of the campaign with both the F-86 and the MiG-15 to check it with 2.5 OB. When I set the receivers in both to 420 (not easy to screw up that setting) for the first NDB in the briefing, the Morse code identifier was different. I don't remember if I received a reply from the tower after requesting startup in the campaign, but I don't think I did. I had issues earlier in Normandy when I used the Azeville frequency for the ATC, and it called Krymsk in the Caucuses. Is it possible that frequencies and codes changed during the update. When all else fails, READ THE INSTRUCTIONS! i-7 8700K Coffee Lake 5 GHz OC CPU, 32GB Corsair 3200 RAM, GTX1080 Ti 11Gb VRAM. Controls - Thrustmaster Warthog H.O.T.A.S., Saitek Pro rudder pedals, TrackIR 5, Oculus Rift S, Rift CV1
Apache600 Posted February 2, 2018 Posted February 2, 2018 Yikes, that would all be beyond the control of a mission builder. I just tested the mission on the MiG-15 side. No problem with the ATC communication, and 420 had no issue with tracking, though you are correct, the Morse Code identifier was incorrect in my flight plan. 307 (the next waypoint) had the correct ID though. I'm sure it's an error on my part. Thanks for finding that one! - Apache600 [sIGPIC][/sIGPIC] The Museum Relic Campaign: --> http://forums.eagle.ru/showthread.php?t=164322 Community Missions (SP & MP) --> https://forums.eagle.ru/showthread.php?t=205546
QuiGon Posted February 2, 2018 Posted February 2, 2018 Just yesterday, I played the mission where you have to accompany some F-16s to Sukhumi, do a low fly over and then fly through some valley to hunt an enemy tanker/transport plane. In the first part of the mission you have to work with NDB 480 IIRC and it worked just fine. The ID was correct and the morse code was correct as well. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
tintifaxl Posted February 3, 2018 Posted February 3, 2018 Sochi Adler seems to have a different morse code, too: "-.-. ---" instead of "... ---". Maybe you could put that into the mission briefing? Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.
Apache600 Posted March 6, 2018 Posted March 6, 2018 I've been looking through the NDB's, and have noticed a bunch of disparities. The upcoming patch will address the issue with the MiG-15 campaign mission 4 progression issue. These NDB's will have to wait for the next patch after that. It'll be a lot of work, and take more time than I have right now, to update all the flight plan briefing pages, kneeboards, and offline pages. But it will happen! [sIGPIC][/sIGPIC] The Museum Relic Campaign: --> http://forums.eagle.ru/showthread.php?t=164322 Community Missions (SP & MP) --> https://forums.eagle.ru/showthread.php?t=205546
tintifaxl Posted March 7, 2018 Posted March 7, 2018 Thanks for looking into the NDB issue :thumbup: Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.
Recommended Posts