RagnarDa

Hey do you have any antivirus software installed? Make sure to put DCS World folder in white-lists. After that I would maybe not only repair but complete wipe and reinstall of DCS...

Thanks for the reports and video! I narrowed the issue down and fixed it. The fix won't be in next patch of DCS though but probably in one after that.

There are reports elsewhere that DCS will hang if activating autopilot a couple of times when standing still on the ground in Viggen. I haven't been able to replicate it myself, could it be something mission specific possibly? Like wind? Could you upload a mission that demonstrates the issue? Do you have any mods installed?

"2020-07-09 23:31:29.690 ERROR SECURITYCONTROL: failed to decode ./Mods/aircraft/Mi-8MTV2/bin/Mi8.dll.crypt 2020-07-09 23:31:29.690 ERROR WorldPlugIns: Can't load plugin module Mi8.dll" Looks like some issue with activation of the Mi-8 module I guess. Since I doubt I can help you with this and I don't think it's related to the Viggen module specificially I am going to move this thread to the relevant section of the forums. I would try going into the module manager (at the top in the main menu of DCS) and removing modules and re-install Mi-8 that way.

Thanks for the very detailed report! I've addressed the biggest issues noted here, hopefully it won't break something else...

Ok do this: - Start DCS - In the Main Menu click the sprocket at the top: OPTIONS - Select submenu GAMEPLAY - Find "Game Avionics Mode" and deselect it. Tell me how it works for you. To stop crashes post landing: switch to open beta version: https://forums.eagle.ru/showthread.php?t=114030

Fixed in internal version, awaiting patch of DCS.

Thanks for the report and for including dcs.log! Can you give me some more context?

Ok glad it is working now :)

By 2.5.6 do you mean latest stable branch or open beta? You can find the file dcs.log in C:\Users\YourName\DCS World\logs

Hi! Thanks for the report and videos. I am unable to replicate this. What version of DCS are you running? Could you send a track file of when you try this? Also, dcs.log ?

Try starting Mi-8, then exit DCS. Go into you Saved Games folder and find DCS World Open Beta (if that is the version you are using) and then go into logs folder. Upload a file called dcs.log to this post.

Hi! Thanks for the report! This issue has been solved about a month ago and reported among other places here: https://forums.eagle.ru/showthread.php?t=274875 . The fix is in open beta though so you'll need to change to open beta branch, or alternatively you can just wait for the analysis to finish which might take several minutes. Don't know when stable branch will be updated.

Thanks for the report and for including the crash logs! The issue was that you where able to fire the Rb05 in a incompatible J/A selector mode (it's supposed to set the fuzing, ie air ground or sea but it was in something else and should'nt be able to launch). Fix probably in coming patch.

[FIXED] Rockets going long We believe it was a bug that was introduced to the atmospheric model in DCS and we adapted our model to the bugged one and then they fixed the bug so I had to revert to the old model :)

I don’t know how a module would be able to crash the server in DCS so probably not Viggen-related

"2020-07-01 21:38:27.427 INFO DCS: DCS/2.5.6.49798 (x86_64; Windows NT 10.0.18363)" You are running stable version of DCS. The fix for this crash has been in open beta for a while now, but hasn't been updated to stable branch yet. You'll need to switch to open beta. The fix was released in open beta a month ago: https://forums.eagle.ru/showpost.php?p=4366643&postcount=98

A log file is always generated even if you have to restart your computer. After you have started your computer, look into Saved Games folder in windows and DCS Open Beta then Logs and you will find a file call dcs.log. Please upload that file and I would be very grateful.

Atmospheric model had changed in DCS (which you can tell by looking at the target marker ring), the sight was calculated from middle of burst both lengthwise and height wise, and sight used non-calibrated IAS to solve ballistic calculations.

Thanks for the report. Found the issue and fixed it.

Could you please post a dcs.log file?

Thanks for the report! I was able to replicate the issue. Will have to ask ED if they changed something with the atmospheric model or ballistics.

You are supposed to pull the trigger 0.5 seconds _after_ the wings appear

Obvious question but do you pull the trigger on the signal (wings)?

Probably some process that got exclusive access to the file and then hung.