Forum Replies Created
-
Posts
-
Ok, thanks again. DLSS does give a good fps boost even when set to quality unless that is because only one eye is displaying of course.
DLSS: Usually works for Z3D, but not for G3D most of the time. I have looking into that on my nice-to-have list, but realistically I can’t tell when I get to that.
Also mentioned here –
@Ralf
Do you think there’s any chance you might get DLSS working with G3D or is it still way down your todo list ?
I’ve tried mouse tracking because trackir does increase stutter but when I look up beyond a certain point, the whole view moves aswell. So it seems to raise the default seat view up. That doesn’t seem right Ralf ?
Ok, thanks again. DLSS does give a good fps boost even when set to quality unless that is because only one eye is displaying of course.
It works fine now thank you. Is there any reason why the default res is 1600×1200 @ 120% scaling because I’m finding the performance better at 1920×1440 @ 100% scaling. Any scaling above 100% kills performance for my system, 5800x, 3080ti.
Also, is DLAA or DLSS ever likely to work ? It’s only displaying in the left eye currently.Thank You. I downloaded the temp profile when you created it so is this new profile part of the update rather than having to be downloaded again ?
Hi @Ralf
I know we aren’t using an official profile yet because you said that had to be done during the next vorpx update but I have a couple of questions.
Selecting the oculus API and forced 45fps ASW does not work (locks 45fps but stutters/double vision, no ASW) but it does work fine using the openxr API. Would there be any reason for that ? openxr has this bug when using it –
https://forums.oculusvr.com/t5/Oculus-Quest-2-and-Quest/White-horizontal-stripe-across-screen-while-using-link/m-p/848398#M30934
That’s why I’m asking.Also, would you recommend using trackir or mouse tracking ? Trackir seems to give a pulsing on the fps during sharp turns every second. Mouse tracking is a pain because if you move the mouse or access menus, the seating position changes.
FS19 was the same, stuttering until the map had been explored and FS22 is the same. If you change any graphics settings, the same applies and I think it is probably cache related. My system, 5800x/3800ti is running 50 to 90fps, 1920×1440, very high setting with mirrors off. Mirrors really hit fps, cause stutter and for me in cab view, add nothing anyway. I have a quest2 and for some reason, I have to select openxr rather than oculus as the device otherwise I get micro stutter when turning corners in vehicles. I’ve locked the frame rate at 45, ASW enabled via the oculus debug tool for a near constant smooth experience. FS22 runs much better than FS19 did with vorpx.
I understand the game is new and I’m not rushing you :p . If I edit the ini to DX11 and copy over the FS19 profile for now, is that likely to work in G3d or would the ini hack work with the current FS22 profile?
Hi Ralf. FS22 now works on my system but Geometry 3D mode is not in the selection list, only Z-Normal. As with FS19, Z-Normal looks really odd in that the vehicle cabs are huge/out of proportion regardless of tweaking. Geometry 3D mode in FS19 runs good on my system, 5800x/3800ti. Is there a way to get Geometry 3D mode working in FS22 ?