Eldur Posted January 19, 2019 Author Posted January 19, 2019 I might have nailed it down to something, but I need more testing to verify the cause. In the first place I noticed this issue and then tried to reproduce it - in the same instance of DCS runtime, with no luck. Now I noticed that whenever I was in the ME and loaded up the map (to do some changes to my testing mission, but that doesn't matter) prior to starting the mission, the retice was fine. But when I fired up DCS and instantly went into the mission, the error occured. Note that in my case all missions are cold'n'dark and the plane is a selectable client (not set to player). As soon as this came to my mind I started to always load up the map I was going to fly on (basically the mission itself) in the ME prior to flying and I didn't have the error once again. But well, I'll have to do some more tests (especially without going to the ME first) to verify this assumption.
Sandman1330 Posted February 18, 2019 Posted February 18, 2019 Happened to me again today. I had previously dropped 2xMK82 and fired several rockets. Only happens once in a blue moon... latest open beta. Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2
Recommended Posts