GCDV31 Posted April 5, 2023 Posted April 5, 2023 (edited) Hello, I have a reveb G2 and when motion reprojection is on or auto in OpenXR for WMR DCS open beta craches. Same issue on ST or MT. It's strange because four weeks ago it seemed to work. Do you have the same Issue ? If I use reprojection in openXR toolkit no crashe but it's more ghosting. Other question in 2D I'm GPU bounding but in VR CPU with MT. Do you have the same? I hope in the futur we can choose to run DCS open beta with or without OpenXR. Edit : My ring : RTX3070TI ryzen 5 5600x 64Go RAM 3200Mhz Edited April 5, 2023 by GCDV31
Ulukai Posted April 5, 2023 Posted April 5, 2023 (edited) Hello, I can confirm your first issue. OpenXR Toolkit is working with Motion Reprojection ON (in locked 45fps) Only OpenXR Tools for WMR with "Motion Reprojection Always ON" is not stable. The Reprojection of both Options are different? I never realize or compare it. If its correct than its interesting! For me both looking unacceptable. The CPU bounding.... hmm its a thing.. I have the same message in MSFS2020 and no performance problems. Otherwise I could find improvements (for me and my System) last time: I disabled heatblur. An than I manipulate all the LOD ( lodMult = 0.5;) inside the "graphics.lua in the "config directory" by myself to "0.5". Since I changed it, I have playable Performance without Motion Reprojection and no 100% for one core utilization (its a bit less). I don't know if it is the key for all. PS: For sure not by 100% HP Reverb G2 Resolution . Im ok with 50% and msaa 2x. I have the same CPU (5600x). dcs.log dcs 2.log Edited April 5, 2023 by Ulukai
mbucchia Posted April 6, 2023 Posted April 6, 2023 (edited) 19 hours ago, GCDV31 said: Hello, I have a reveb G2 and when motion reprojection is on or auto in OpenXR for WMR DCS open beta craches Automatic in OpenXR Tools for WMR means "only MSFS2020". In other words, it does _absolutely nothing in DCS_. So I highly doubt your issue has anything to do with this setting... you probably should start looking elsewhere. PS: the "Automatic" is being remove in the next version of OpenXR Tools for WMR. Edited April 6, 2023 by mbucchia I wasn't banned, but this account is mostly inactive and not monitored.
GCDV31 Posted April 6, 2023 Author Posted April 6, 2023 9 hours ago, mbucchia said: Automatic in OpenXR Tools for WMR means "only MSFS2020". In other words, it does _absolutely nothing in DCS_. So I highly doubt your issue has anything to do with this setting... you probably should start looking elsewhere. PS: the "Automatic" is being remove in the next version of OpenXR Tools for WMR. Thank you for this information. I will check if I have the issue when OpenXR tools for WMR is on "automatic".
GCDV31 Posted April 6, 2023 Author Posted April 6, 2023 18 hours ago, Ulukai said: Otherwise I could find improvements (for me and my System) last time: I disabled heatblur. An than I manipulate all the LOD ( lodMult = 0.5;) inside the "graphics.lua in the "config directory" by myself to "0.5". Hi thank you for this tips I will try. What is the impact of LOD at 0.5 on A/A and A/G range visibility ?
Ulukai Posted April 6, 2023 Posted April 6, 2023 Hi, it is the Level of Detail for objects in distance. The higher distances the less you need the fully polygon count but it doesn't hide the Objects. Per now I didn't saw any restrictions in spotting. I'm still in a experimental phase. Maybe 0.7 or 0.6 is enough for my system who knows. Or maybe is placebo effect. I just notice it at the Aircraft Carrier last time. The Ground crew lost faster the maximum Texture/Polygon Detail. But totally acceptable in my opinion. At 50K feet I can spot detailed bunkers.
Recommended Posts