Spacehamster Posted October 5, 2016 Posted October 5, 2016 The compass appears to be bugged. I flew from a southern airfield to Sochi. After some flying, it picked up the signal, it played the morse beep. However then suddenly the compass reset itself to a weird angle, but the morse code was still playing. It happened randomly, about 85km away, and the plane was at 9km altitude, so terrain obstruction could not have caused it.
Art-J Posted October 5, 2016 Posted October 5, 2016 You have to be a bit more clear than that. Picking up signal of Batumi or Sochi? Did the morse code change? I ask, because since latest update, both codes from NDBs and RSBN stations can be heard at the same time (when both systems are turned on), so even if You loose signal from one (pointer on the compass locks at 45 degrees), there might still be beeping from the other. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Spacehamster Posted October 5, 2016 Author Posted October 5, 2016 The morse code was the same all the time. And I switched it to NDB on the left side of the cockpit and selected the correct ARK channel for Sochi. It was not a Batumi signal because it appeared only when I was around 130km away from sochi, and I took off at one the airports close to batumi. And after take-off there was no signal. (And how would rsbn and ADF work at the same time in a mig21? There is a switch that has an ARK or RSBN.)
Art-J Posted October 5, 2016 Posted October 5, 2016 I should be more clear - nowadays, when both systems are powered up via CBs on the right side, the code signal from both can be heard at the same time (quite a mess actually, but maybe it's correct implementation, I don't know), while the ARK/RSBN switch on the left controls the homing pointer on compass I believe. Just trying to repeat the whole scenario in my head, but something doesn't add up. We might have some ARK/RSBN terminology misunderstanding here. If I understand correctly, You took off from one of southern airbases (Kobuleti or Senaki) and wanted to fly northwest towards Sochi using ARC+NDB's only. Is that right? Max range for NDB signal reception in DCS MiG is 120 km (only at very high altitudes), so You wouldn't pick it up immediately after takeoff (too far away), only after some time while flying towards Sochi. About 85 km sounds about right then, no bug here. Was RSBN turned off the whole time? Your first and second post contradict each other a bit and I'm trying to figure out what the hell You were doing :D. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Spacehamster Posted October 5, 2016 Author Posted October 5, 2016 (edited) I have added a track replay in this post. What I know is that the left side RSBN/ADF switch controls not just the compass but also the audio. For example when you enable all the switches on the right hand cockpit side after powering the engines, then you will hear white noise until you switch the left hand switch to the other mode. To respond to your post: I took of at one of the airfields near batumi, but not batumi itself. Can't remember the name. Around 240km away from sochi. Then I dialed in the correct ARK channel for Sochi and took off. After about halfway, I got a signal. But that signal suddenly was lost on the compass about 80 or so km out. But the morse tone was uninterrupted. I have used ARK and RSBN many times over 2 years and only recently I kept getting this problem of the compass suddenly losing signal. That is why it looks like a bug to me.Virtual Aerobatics public server v1.5.4u7-20161005-063638.zip Edited October 5, 2016 by Spacehamster
Recommended Posts