dutchili
-
Posts
387 -
Joined
-
Last visited
Community Answers
-
dutchili's post in ERROR DX11BACKEND (25524): DX device removed. Reason: 0x887A0007 was marked as the answer
@BIGNEWYThis thread can be closed. The root cause was incompatibility between the Nvidia driver (regardless the version) and Windows 11 core isolation.
-
dutchili's post in bullseye --- off the map? was marked as the answer
Temp fix is to:
- rename mission to .zip
- copy the mission file to your desktop
- edit the mission file
- search for bullseye
- replace the x and y location for the 'blue' to
["y"] = -823001.91645693,
["x"] = -482860.00940784,
- save the file
- copy the file back to the zip archive
- rename the .zip to .miz again
- your blue bullseye will show-up near Wiesbaden
-
dutchili's post in DCS won't start oculus ptc was marked as the answer
16:54: both server and client are working again.
Next dcs server entry is ASYNCNET (13684): Login success.
I guess there was a authentication issue
-
dutchili's post in MT: Steam will not launch MT version in VR (for Oculus Quest) was marked as the answer
i just fixed it for Oculus.
Previously i had installed OpenXR tools for WMR to get the openxr runtime. I now uninstalled it and used the '--force_openXR' parameter in steam to prevent using OculusVR.
In steam i launch DCS with the 'MT preview' option. The in-game fps counter now shows the CPU/GPU bound text which confirms it is working with the MT version.
Performance i quite comparable to non-MT....on my i7 and RTX 3070. Was expecting a lot more, but apparently there is still to much going on on the main thread.