dwaldrop

I have had an issue with DCS VR for a while now and have finally gotten tired enough of it to try and figure it out. I am running a Pimax Crystal Light with an NVIDIA 4090RTX on an Intel 149000kf. Almost everything is DCS VR looks awesome: cockpit is crystal clear, terrain and clouds look almost real life, other aircraft (when I hit F2 to look at them) are amazingly sharp, ground vehicles and ships are perfect, smoke, rain, waves, etc are almost real life. The problem is when I am fighting another aircraft, whether it is AI or another player, the aircraft looks shimmery. Sometimes streaks come off of the trailing edges and looks like the plane is melting or in warp drive. Other times I see what I figure is called ghosting, like I see a ghost image of the entire wing as the plane maneuvers. When I click to the F2 vies of the same plane, it looks prefect. I have spent a lot of time fiddling with all of the settings and have just about gotten the shimmering and ghosting removed but it is still noticeable. Sometimes it is worse than other times but there seems to be no pattern as to why it gets worse and then gets better, never going away completely. I understand that DCS VR is very resource intensive even for a 4090 but one would think that it could do better, especially given that all of the other visuals look so good. Any help or ideas would be appreciated greatly. My specs are listed below. Thanks! PC Specs: Windows 11 Pro Intel i9-149000kf 3200MHz 24 core 32 logical processors 64GB RAM NVIDIA 4090 RTX Pimax Crystal Light DCS Settings: Upscaling: DLSS DLSS Pref/Quality: Quality Sharpening: 0.75 Textures: High Terrain Textures: High Shadows: High Flat Shadows Blur: On Secondary Shadows: On SSS: Off Visib Range: Extreme Clouds: Ultra Water: High SSAO: Off SSLR: Off Preload Radius: 150000 MAX FPS: 120 Anisotropic Filtering: 16x Scale GUI: 1 Rain Droplets: High Enable VR Headset Pixel Density: 1 MSAA Mask Size: 0.52 Enable HMD Mask: Checked Pimax Device Settings Refresh Rate: 90Hz Upscale (Lab) Render Quality: 0.90 Running Pimax Runtime and QuadViews Companion NVIDIA Settings Image Sharpening: Off Ambient Occlusion: Off Anisotropic Filtering: 16x Antialiasing - FXAA: On Antialiasing - Gamma Correction: On Antialiasing - Mode: Application Controlled Antialiasing - Setting" Application Controlled Antialiasing - Transparency: Off Background Application MAX Frame Rate: Off CUDA - GPUs: All CUDA - Sysmen Fallback Policy: Driver Default DSR - Factors: Off DSR - Smoothness: Off Low Latency Mode: Ultra Max Frame Rate: 90FPS MFAA: Off OpenGL GDI Compatibility: Auto OpenGL rendering GPU: Auto-Select Power Management Mode: Prefer maximum performance Shader Cache Size: Driver default Texture Filtering - Anisotropic sample opti...: Off Texture Filtering - Negative LOD bias: Clamp Texture Filtering - Quality: Quality Texture Filtering - Trilinear optimization: On Threaded Optimization: Auto Triple Buffering: Off Vertical Sync: Use the 3D application settings Virtual Reality pre rendered frames: 3 Virtual Reality - Variable Rate Super Sampling: Off Vulkan/OpenGL present method: Auto

sleighzy, thank you for the input. I did another DDU wipe in safe mode and started over. This time I installed Steam VR (don't use it) and Pimax Play pickled it right up. I had looked through the DCS log too and saw the runtime errors but just hadn't put two and two together. Thanks again for the assist!

DCS.LOG attached. Skyrim VR and Fallout 4 VR work The log file reflects the following settings: Pimax Play - OpenXR Runtime is Pimax OpenXR PimaxXR Runtime is active Quadviews is active SteamVR is not installed (never has been installed) I had an XR 7900XTX with all of the drivers updated and DCS ran like a champ in VR. Launched Win11Pro in safe mode and ran DDU to remove all AMD drivers. Installed the 4080 and loaded latest NVIDIA drivers along with NVIDIA app DCS now will not run in VR Another anomaly is now when I open PIMAX XR Control Center I get the following popup messages: Failed to Query Version Failed to locate SteamVR. Switching to the SteamVR runtime will not be offered. Unable to identify the active OpenXR runtime: C:\Program Files\Pimax\Runtime\PiOpenXR_64.json After I acknowledge those three messages PimaxXR Runtime opens and I am able to select PimaxVR as the active runtime. If I close it, I go through the same process again. Nothing has changed except the removal of the AMD GPU with drivers and the installation of the NVIDIA GPU and drivers. dcs.log

Running an Intel 149000KF with 64GB RAM, 4080 Super OC, and Pimax Crystal Light. All NVIDIA and Pimax drivers are up to date. I had a Radeon 7900XTX in the same system and everything worked great. Removed the AMD drivers with DDU and put the 4080 in. Installed and updated all NVIDIA drivers. Now DCS will not launch into VR. Pimax OpenXR and Pimax Play are both set to use Pimax OpenXR. When I open DCS in Steam and click Use Open XR it tries to go into VR. The box in the taskbar is black, then at the same time the NVIDIA screen pops up, the DCS box turns yellow and it opens in 2D. I’ve verified file integrity and then uninstalled and reinstalled DCS along with all of the other software. Nada. Maybe it’s something with NVIDIA? Any help or insights would be appreciated.

I have an OnYourTwelve master arm panel that is conflicting with WinWing MFDs. The MFDs work great as long as the master arm panel is not connected. When I connect the master arm panel, the MFD #3 quits working. Here is the setup I have: Three powered USB hubs. Hub #1: All of the WinWing devices - 3x MFDs, UFC, and Hud controller Hub #2: WinWing throttle, Thrustmaster Warthog joystick Hub #3: Tek Creations right panel, keyboard, trackball mouse, and a USB powered light All of the devices are on separate powered USB hubs and work well with each other. When I throw the OnYourTwelve master arm panel in the mix things stop working. I have tried the master arm panel on each of the three USB hubs as well as plugged it directly into a USB port on the PC. Result is the same. I have disabled selective suspend in the Windows 11 Pro registry so all of the USB devices remain powered on and never go to sleep. Anyone else having this kind of issue? Thanks!

I set up my two Cougar MFDs for F/A-18C and had them correctly identified as left and right using USB controllers in Windows. Everything worked like a champ. A few weeks ago, I loaded A-10CII and the MFDs were reversed. In the Thrustmaster software, they correctly identify as RIGHT and LEFT, as they do in Windows USB controllers. In the DCS settings, there is no option for me to assign left MFD buttons to the physical left MFD. A couple of questions here: Why would the MFDs work correctly on one aircraft but be reversed on another? I read somewhere that the MFDs are hard coded as left and right but do not know how true that is. Short of pulling my simpit apart and swapping the actual MFDs (don't want to have to do that) is there any other solution? Maybe there is a setting within DCS that will allow the left MFD to actually use left MFD keys instead of being grayed out? Any assistance or insight would be appreciated!