Convexrook

it is the 9900K, I had the same issue and it wasn't resolved until I tried a different CPU. After that I upgraded to 11900K Sorry but re-installing windows won't fix it.

The Arrester Cable only renders on one eye in VR on all carriers. This happens when the arrester cable is retracting after landing.

Once a better downloader and verifier is available I will go on standalone, for now I am good with Steam version. I buy everything anyway

Same problem here, the AI keeps attacking my targets Second time around going through the campaign after 2.7 and same result

if you have a WMR (Reverb G2) you can now control the mast via the WMR for SteamVR settings: "Apply Hidden area stencil..." now you don't worry about the MSAA being on or off

next thing you know you are going to request to be able to wash your planes!! hahahah

Windows Explorer Freezes and no interaction can be made about 15-20 into playing, DCS with HP reverb G2. Tested other VR games and no Crashes of the sort. Tested 2D Games and no crashes. No logs to show as there is no way to get one

Can I get a..... whuuuutt!!! Well done guys keep up the great work!

I have done so many repairs(steam) and still getting crashes to the point where I have to click the reset button to overcome them.

need some help, I cannot get the text for the Case 3 approach via the ATC. It always stops here. Any ideas

They did

Thanks all. I took some measurements from the real F/A 18 cockpit and it matches the default 68 IPD for the G2 in terms of scale. I basically used lifted the headset and compared to a cardboard cutout of the cockpit. I sit pretty now

I noticed the same crashes with the 9900K on Aorus Z390 Ultra. I just bought a z590 with the 11900K and all the crashing stopped. Played 3 hrs straight multiple missions not one crash. Could this come down to CPU microcode? Just speculating!

can someone help me. I do not get the entire 9 line or ATC tab text readout on the kneeboard . I only get the first line of the text. Any way that can be fixed? this is the only line that pops up after Case 3 readout!

The migs never take off for me. just stuck flying around waypoint 2-3

same, it broke again.

I would like to know from a real F/A 18 Pilot, what is the accurate scale in VR for the hornet. Devices: HP reverb G2 - G2 Vive Pro - VP Valve Index - VI currently I use: G2 - 68 IPD - in game default IPD VP - 70 - in game default IPD VI -70 - in game 73 IPD

for BDA window or chat window or some text window? here you go ----------------------------- imgui.ini ------------------------------ just incase it gets flagged like yours here's the content ----------------------------- [Window][Debug##Default] Pos=60,60 Size=400,400 Collapsed=0 imgui.ini

I never use mods, base game always. Compatibility mode enabled still crashes BTW. These crashes only started with 2.7. Prior to that I could play extensive hrs on end with no issues other that the dreaded windows 10 lag spike. I have tried different VR headsets: Vive Pro, Valve Index, Original Vive and Reverb G2, I only get crashes with the G2. maybe that is something to look into? Could be Microcode with the CPU: 9900K as well : my other computer a 6600K works with no crashes. Right now I am just throwing thing out there to help troubleshooting Thanks

I set MSAA to 4X. there seems to be a conflict or a restriction when rendering clouds. this is the means of all my crashes even with MSAA off dcs.log-20210514-144425.zip dcs.log-20210513-151717.zip dcs.log-20210510-042617.zip

After the update and I started my game, My profile got wiped. no saved mission, no log book, nothing, just NEW PILOT

+1, to add I lost all my saved missions and configs after restarting the game. I checked the saved folder and nothing was under mission editor. seems like a magic bug wiped my progress 4800+ hours of flight time gone .

if you turn MSAA to 2X the blue tint turns to black. so much better

Coming from a Vive pro it is very noticeable to me. It is similar to turning on legacy reprojection on the Vive ( choppy )