yogiklatt

This definitely worked for me. I have a rather weak CPU (an old i7-6700K overclocked to 4.6 and a 2080ti) and the fps now pushed it well above the 45 fps in VR.

Yeah for some reason that worked for me as well. Having motion reprojection in the OpenXR toolkit crashes DCS on startup. Enforcing it with the OpenXR toolkit companion app however works.

Heya, I am getting drastic FPS drops in 4K from 60, 70 down to single digits when I fly the Apache over placed castles in the Syria map. I assume it has to do with altimeter raycast because it does not happen with the Huey. nullAn example is the castle in Kyrenia in North of Cyprus X+00045803 Z-00233346 36 S WE 29363 10897 Same issue happens with the fortifications in Famagusta (WD88). Not sure if that is a problem with the Syria map itself, but given that I could only see this in the Apache I thought I should post it here. Edit: Added use case, spawn a player Apache (0 knots, 100 feet AGL) at these coordinates (screenshot added): X+00018766 Z-00178089 36 S WD 85990 87321 Once ingame immediately hit active pause and you should see the fps drop.

In general having the radar on drops a lot of frames for me ...

The radar itself seems to be a huge frame hog. Turn off your radar in flight and you'll see quite a big jump in FPS.

Heya, to simulate holding the upper or lower collective grip I tried to use the boat switch on my Warthog throttle (buttons 9 and 10) as a modifier to e.g. assign the sight selection (no modifier) and the search light movement (modifier on button 10) to the coolie hat. A thing that seems to happen on the Warthog throttle though is that although the boat switch keeps the signal active it acts more like a toggle. Meaning if I push the boat switch backwards (button 10) and press then use coolie hat, the search light movement is called (which is correct). However if I then reset the boat switch to the center position (thus not sending the button 10 signal anymore), the coolie will still trigger the search light movement (which is incorrect). Only if I pull the boat switch backwards a second time the modifier on button 10 counts as released, so it acts more like a modifier toggle instead of a modifier hold. Crosschecking it with USB Game Controller interface shows that button 10 is correctly released when I recenter the boat switch so I don't think anything is wrong with the throttle itself. It also happens with the other buttons on the Warthog. I am not sure if this is a AH-64D specific bug as it can be easily reproduced on the binding screen itself by pressing the button combinations with the modifiers. I also have a lot of modifier bindings on a gamepad (for the TEDAC) where I use the D-PAD to bind the complete TEDAC on the gamepad but I did not come across the same issue there.

I also fly mostly in VR but just as the channel map the Marianna's map is not usable for me. While the northern islands is mostly okay-ish flying in a Hornet in low altitude around the Internation Airport in central Guam drops the frames massively. Even if I turn on active pause and put the headset down to keep the viewport steady, the frame rate will still be very unstable between and jump between 40 and 47 fps ... that is with trees visibility, detail, etc on minimum which is not needed on the Syria map. It's a bit of a bummer, I have an overclocked RTX 2080 Ti and run it with an old Oculus CV1, PD at 0.5 and OTT SS 1.4 ... which is perfectly fine in Syria, but on Mariannas the fps are not stable enough to stay above 45. And it's the GPU not finishing up in time, the CPU itself is well below 20 ms frame time. It would actually be really helpful to see a graph in the fps counter screen showing the differences between GPU and CPU times. Edit: I just noticed that setting the VR prerendered frames up to 4 (from 1) in the NVIDIA control panel comes with quite a bit of a performance boost. Sitting in a cockpit I do not really feel much of a latency difference.

I saw that kind of lighting only in VR with stereo parser enabled ... turning it off fixed my lighting issues.

Complete reinstall fixed the issues ... also somewhat improved the frame rate. Guess it was about time after two years.

Cheers, if the re-install doesn't fix it (I assume the whole world is downloading free modules atm, it's a rather slow DL atm), I'll give that a go! Thanks @Flappie!

Heya, since the latest update I am getting a crash in wRadio.DLL. It goes all fine until I actually go into a seat or commander position in MULTIPLAYER ONLY and then I am always getting the same crash. I removed all mods I could find (Tacview, SRS, Kneeboard Builder, etc.), even reverted latest NVIDIA drivers to rule out any issues with the audio drivers. The voice chat check box in the options was off but I also tried to completely wipe the user folder which didn't make a difference. I remember that I initially had an issue with the auto updater but I did a full repair which only prompted me to delete some older plane texture mods. 2020-12-22 16:50:04.474 ERROR WRADIO: CommandDialogsPanel: RadioCommandDialogsPanel.addSomeSubmenu error 2020-12-22 16:50:04.475 INFO EDCORE: try to write dump information 2020-12-22 16:50:04.476 INFO EDCORE: # -------------- 20201222-165005 -------------- 2020-12-22 16:50:04.477 INFO EDCORE: DCS/2.5.6.59398 (x86_64; Windows NT 10.0.19041) 2020-12-22 16:50:04.478 INFO EDCORE: E:\Games\DCS World OpenBeta\bin\wRadio.dll 2020-12-22 16:50:04.479 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 127FD8D6 00:00000000 2020-12-22 16:50:04.482 INFO EDCORE: SymInit: Symbol-SearchPath: '.;E:\Games\DCS World OpenBeta;E:\Games\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'yogik' 2020-12-22 16:50:04.483 INFO EDCORE: OS-Version: 10.0.19041 () 0x300-0x1 What I am trying now is to just revert to the previous Open Beta and updating from there again ... sadly that's at least 120 gb of traffic ... but any pointers are welcome. dcs.log-20201222-165005.zip

I have the same issue. I love the plane but I am finding it odd that there are no separate controls for both cockpits.

I sorted it out. I forgot I had VR shaders mod running and had older NVIDIA drivers. The crash was pretty much in line what was reported in other threads (https://forums.eagle.ru/showthread.php?t=268986). So I updated the drivers and removed the mod. All was working then. :)

Whoops, forgot to upload the attachment, here we go. Edit: Actually reading other posts in the forums, I'll try first to update the NVIDIA drivers PG_OperationBaguette_GM_bug.miz

It seems DCS OB is crashing for me whenever I changed the weather. Here are my repro steps: 1) Launch game 2) Select editor 3) Launch the mission from editor 4) Go into game 5) Press ESC and go back to editor 6) Change any weather setting (e.g. density) 7) Launch the mission from editor again 8) Observe crash during loading process The used mission has been attached. NEVER MIND: Updated the drivers and I had forgotten that I had the VR shaders enabled. Everything runs again :)