71st_Mastiff

yea did what someone stated and run from the MT folder and the shader box is gone.

I have a shader box in my cockpit view VR PiMax 8K, this happened before when they did an update a year ago for VR. I pretty sure its not hard to fix. Ok used the Mt folder DCS exe worked

Installed played good results but now I have a weird shade box around my cockpit. it's like the one bug we had for VR maybe 2 years ago?

You kidding right they just announced MT last November, so I wouldn’t count my chickens just yet, I think there going to release the F15E

who died the day it was due out? " only thing is certain, death and taxes, but a patch you will never see; when due on the day they state."

Have they implemented the pimax tool for this new version of there’s?

Same it’s hit or miss, sometimes not responding which causes me to kill process DCS. In the openxr tool I uncheck the games

make sure this is unchecked. finally working.

drivers updated today from NVIDIA was today. new versions. 528.24 DCS Was working fine until todays open update; now I just crash to desktop, run repair doesnt do anything. pulling my hair out now.

I only get to 100% then crashes. PiMaxian user. game is broke with this .

tried and only UI works DCS works UI only, try to start a game and it crashes to desktop or stops responding, getting D3D 3090TI dll errors. from the pimax log.

same here, will probably have to wait until tomorrow to hear anything on it. 2023-01-25 16:15:50 -0800: PimaxXR - v0.2.8 2023-01-25 16:15:50 -0800: PVR: 1.23.1 2023-01-25 16:15:50 -0800: Application: OpenComposite_Steam; Engine: 2023-01-25 16:15:50 -0800: xrGetSystem: pvrResult failure [6] Origin: pvr_createSession(m_pvr, &m_pvrSession) Source: D:\a\Pimax-OpenXR\Pimax-OpenXR\pimax-openxr\system.cpp:55 2023-01-25 16:15:50 -0800: xrGetSystem failed with XR_ERROR_RUNTIME_FAILURE

my open xc no longer works dcs freezes at 5%. yes all usually repairs done reboot dcs will no work. in vr.

open XR will not open when stuck on UI front screen I have no mouse control in UI; the keyboard not working with the UI with the Open XR try "cntrl+2" to open is not working. 2023-01-25 16:15:50 -0800: PimaxXR - v0.2.8 2023-01-25 16:15:50 -0800: PVR: 1.23.1 2023-01-25 16:15:50 -0800: Application: OpenComposite_Steam; Engine: 2023-01-25 16:15:50 -0800: xrGetSystem: pvrResult failure [6] Origin: pvr_createSession(m_pvr, &m_pvrSession) Source: D:\a\Pimax-OpenXR\Pimax-OpenXR\pimax-openxr\system.cpp:55 2023-01-25 16:15:50 -0800: xrGetSystem failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:24:20 -0800: PimaxXR - v0.2.8 2023-01-25 16:24:20 -0800: PVR: 1.23.1 2023-01-25 16:24:20 -0800: Hidden area mesh is not enabled 2023-01-25 16:24:20 -0800: Application: DCS World; Engine: 2023-01-25 16:24:20 -0800: Requested extension: XR_KHR_D3D11_enable 2023-01-25 16:24:20 -0800: Requested extension: XR_KHR_visibility_mask 2023-01-25 16:24:20 -0800: Device is: Pimax Vision 8K X 2023-01-25 16:24:20 -0800: Recommended resolution: 3842x3160 2023-01-25 16:24:24 -0800: Using Direct3D 11 on adapter: NVIDIA GeForce RTX 3090 Ti 2023-01-25 16:24:37 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:24:40 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:24:43 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:24:46 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:24:49 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:24:52 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:24:55 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:24:58 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:01 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:04 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:07 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:15 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:18 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:21 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:24 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:27 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:30 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:33 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:36 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:39 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:42 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:45 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:48 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:51 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:54 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:25:57 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:00 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:03 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:06 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:09 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:12 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:15 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:18 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:21 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:24 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:27 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:30 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:33 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:36 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:39 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:42 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:45 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:48 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:51 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:54 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:26:57 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:27:00 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:27:03 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:27:06 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:27:09 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:27:12 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:27:15 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE 2023-01-25 16:27:18 -0800: xrWaitFrame failed with XR_ERROR_RUNTIME_FAILURE

I don't expect any patches until February. due to Chinees new year last 2 weeks this year.

ok it was the special tabs setting, for FFB center trim settings, for some reason the update changed my setting to FFB...

click bait...

me pushing it full forward, other guys say there was something changed and they had to put advanced curves for forward push 50% more. ok its fine in SP, but in MP its not. might be wind?

Work with the EVGA LCD Boards? Z10 Keyboards?

I'm having an issue since one of the new patches, I cant get AOA nose down on the apache when taking off, Im at full on foward on the stick and still no way to level the nose. Virpil T50 M2.

I fixed it by replacing with the Ka52-2 inputs.

guess I ll have to delete my keybinds for DCS again because you guys can't seem to fix it, when you employ a new module this happens every time. I spend hours re-keybinding...

yes this KA-50-2 is working no issues.

yea no double keybinds, the space bar isn't working in this KA52 III, it will not assign it is not double in the default area there is keybinds missing. this is a new install of this upgraded KA 52 III. so repaired didn't work and controls function fine in the other Ka 52 2.

will not continue when Spacebar presses.