Resrob66

Cool, thanks for the replies! I’ll give it a shot.

On any mission I’ve noticed that the F10 comms menu works properly on the ground before takeoff, but won’t pop up after takeoff at any time in flight. So can’t make any communication calls in flight to anyone. It’s not a key bind issue.

Well, after some more investigating I realized openXR toolkit was active when launching dcs. When I turned that off I got my VR view back.

Hi, prior to the latest update DCS was working fine for me in VR. Now after the update I ran the program once successfully on my monitor. Enabled VR and now when I launch it the program starts, I get the title screen, then it goes away, the sound starts playing as if it has launched and I have a black screen in VR with nothing but my desktop on the monitor. Prior to this I'd see quadview on my monitor emulating the VR view. I have to use task manager to kill the program. I've run the cleanup and repair. My windows and graphics are up to date. I'm using Varjo Aero with Varjo Base, all up to date there too. Havent changed anything with that. Only mod is DCS-SRS. Since the latest patch/hot fix I get the same result but when I try to kill the program with task manager I get a game crash box popping up. AMD Ryzen9 5850, 128gb ram, game drive 2tb nvme SSD, MSI rtx 4090. attached are a couple of log files from todays attempt to run. dcs.log-20240803-193506.zip dcs.log-20240803-192947.zip

Updated the sim today, the new update made MT unplayable for me with wildly erratic frame times/stuttering/fps. Went from GPU bound pre-update to CPU bound without changing settings on my side. Didn’t have the time/motivation to try to tweak things to remedy it. However; on open beta ST the new Normandy 2.0 was working very well. FPS dropped at low altitudes over Paris, but was stable at 40-45. Other areas 70-80 FPS. High preset. Tried it on instant action-free flight. AMD Ryzen9 5950, 128gb ram, rtx 4090, Valve Index @80hz.