Nekativ

FPS Results Samsung Odyssey+ w/Steam VR + WMR Driver: 2.5.5.32299 (Open Beta) 60fps average 2.5.430386 (Stable) 60fps average HTC OG Vive: 2.5.5.32299 (Open Beta) 64fps average 2.5.430386 (Stable) 64fps average System Specs: Intel Core I9 9900K @ 4.8GHz EVGA GeForce RTX 2080 Ti FTW3 32 GB DDR 3200 Samsung SSD 850 EVO 500GB Nvidia Driver: 430.86 Windows Version: 1903 OS build: 18912.1001 SteamVR Version: 1.5.9 Graphics Settings: Nvidia Settings: Power Management Mode: Perfer Max Peformance Virtual Reality pre-rendered frames = 3 Vertical Sync: off Everything Else: Application Controlled ["graphics"] = { ["DOF"] = 0, ["LensEffects"] = 0, ["MSAA"] = 2, ["SSAA"] = 0, ["SSAO"] = 0, ["anisotropy"] = 3, ["aspect"] = 0.16649323621228, ["chimneySmokeDensity"] = 0, ["civTraffic"] = "", ["clouds"] = 1, ["clutterMaxDistance"] = 990, ["cockpitGI"] = 1, ["disableAero"] = false, ["effects"] = 3, ["flatTerrainShadows"] = 1, ["forestDistanceFactor"] = 0.3, ["fullScreen"] = false, ["heatBlr"] = 0, ["height"] = 7688, ["lights"] = 2, ["motionBlur"] = 0, ["multiMonitorSetup"] = "1camera", ["outputGamma"] = 2.2, ["preloadRadius"] = 102300, ["rainDroplets"] = false, ["scaleGui"] = false, ["shadowTree"] = false, ["shadows"] = 4, ["sync"] = false, ["terrainTextures"] = "max", ["textures"] = 2, ["treesVisibility"] = 5000, ["useDeferredShading"] = 1, ["visibRange"] = "Ultra", ["water"] = 0, ["width"] = 1280, }, VR Settings Samsung Odyssey Custom Res = 100% (Native Resolution, Confirmed) HTC Vive Custom Res = 100% (Native Resolution, Confirmed) Pixel Density on both is 1.4

Sorry for the late reply. My specs are as follows: -Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804) -Samsung SSD 850 EVO 500GB -Intel Core i7 3770k -NVIDIA GeForce GTX 1070 -32GB of RAM -32GB Pagefile -Nvidia Driver version 417.22 -DCS is Open Beta version 2.5.3.24984 DCS Settings: https://imgur.com/a/QQboRuQ I think the inconsistency is with the AI units staggering their shots, I went back and re ran some tests and had some problems with the AI sam units firing their shots at the same time while in the same group. I went ahead and made another couple of missions, this time with the SAM units not in the same group and managed to get 100% consistent results again on my end. I attached two files mission files, one with a M2000 and another with an F18, the M2000 mission crashes every time and the F18 mission does not. I also attached the crash report generated from one of the crashes. m2kbug.miz f18bug.miz dcs.log-20181214-072552.zip

Thanks for looking into this. I have some missions attached to the original post, does it not reproduce with those? I setup a mission, lay down 11 hostile SAM units in the same squad, say "SAM Roland ADS", make sure to set their skill level to excellent so they all fire at the same time instead of staggering their shots. Then simply fly the Mirage into them until they fire at you. I have handed the missions I made to 12 people so far and they all confirmed the crash, if its not reproducible on your end how can we help narrow this thing down further?

I noticed this way in the "In Test" stage on the bug tracker and the comment was "Tested while being fired at by 18 various sams with no crashes" I would like to reiterate that this bug occurs when 11 sam units or more fire at you at the same time. It does not matter the type, it happens with all of them. Also please note the sample missions that recreate the problem that I attached to the original post. I am running the latest open beta (2.5.3.2446) as of this date and I have confirmed the bug with 100% success rate across 10 people. I hope I was helpful.

This appears to be a slightly different bug, because some of those reports mention it's a possible problem with the launch warning system. This bug will happen even with all launch warning system and RWR turned off.

I have zero'd in on a bug that I have been encountering in multiplayer. When more than 10 surface to air missiles are fired at the Mirage at once it causes DCS to crash. The same cannot be reproduced for other aircraft. It does not seem to matter if the SAM is radar or IR guided and I have played in multiple states with the missile launch warning on and off. I have reproduced it in the attached single player missions. In the mission is a player Mirage flying towards more than 10 SAMs when they decide to launch it crashes. This has been verified with multiple users. m2k_11_SAMs_bug.zip