Hi. Two Pico4 screenshots inside cockpit of Icon Aircraft. The second image is a smaller section, but is NOT a VR zoom-in. The instrument labels are barely readable from my seating distance in cockpit! I have tried everything possible to try and get a sharper readable VR image. Tried all the VR add-ons and settings I can possible think of, to no avail. This is in VDXR (No Steam VR) FSVR settings Nvidia DLSS super res, et. Direct ethernet/power link to Pico. PC i9-11900K, 32GB Ram, RTX 30990. From what I have seen others are getting a much sharper FSVR on their Pico 4 with similar PC systems. I just can not work out why I can not? Any advice PLEASE.
Do you use the OpenXR Toolkit to ramp up resolution to something around 4500x4500 (also if I fear that’s not possible with a 3090)?
Try TAA and see how it goes.
1 Like
Thanks for reply. I will see if I can get up to 4500x4500 in OpenXR toolkit. What about yet another VR tweaking tool DCS 2.9? Worth a try or not? I have tried TAA mode but FS does not like it, and keeps CTD? Nvidia DLSS super res mode has been the most reliable. I cant remember any CTDs with that mode.
Thanks, as mentioned from another reply. FSVR does not like TAA mode and CTD too many times? Nvidia DLSS super res, is by far the most reliable mode.
Strange, never had a CTD due to using TAA. I’m on AMD, maybe a driver issue…
1 Like
I got decent sharpness with red Pico 4 with the following main settings although this was with a RTX4090. When I had my RTX3090, I needed to run things lower.
Pico 4:
90Hz
MSFS:
High quality preset
TAA mode @ 100%
Sharpness 0
OXRTK:
Fixed Foveated Rendering - Quality preset
CAS Sharpening @ 40%
Override resolution 4120x4120 per eye
Virtual Desktop:
VDXR runtime
HEVC 10 bit codec
Bitrate 150Mbps
Sharpening @ 70%
SSW disabled
With the RTX3090, from memory I had the following:
Pico 4:
72Hz
MSFS:
High quality preset
TAA mode @ 100%
Sharpness 0
OXRTK:
Fixed Foveated Rendering - Quality preset
CAS Sharpening @ 40%
Override resolution 4120x4120 per eye
Virtual Desktop:
VDXR runtime
HEVC 10 bit codec
Bitrate 150Mbps
Sharpening @ 70%
SSW Enabled
The biggest changes were 72Hz and SSW enabled for the RTX3090. After that, you can play with DLSS instead of TAA mode in MSFS and also look to lower the override resolution in OXRTK to 4000x4000 or lower but definitely do not go below 3120x3120 per eye as this setting has a big impact on actual resolution resolved in the headset. Also avoid over sharpening - I recommend disabling this in MSFS and use in Virtual Desktop or perhaps add a bit in OXRTK as I have. Overdo this and it will have a negative impact on visual clarity.
2 Likes
Wow! Thank you so much for all that in depth information. I will certainly try all your suggestions. I have tried TAA mode from Nvidia DLSS mode. The cockpit gauges are a little bit more clearer but not by much. However, TAA mode is less stable, and it has CTD a few times? It has never CTD with DLSS. It may be a few days before trying all your suggestions using OpenXR TK, and I will let you know my findings. Still waiting to find out what this other VR tweaking tool does DCS 2.9? Thanks again.
I may be wrong but isn’t DCS 2.9 for DCS? That’s a different sim.
My mistake sorry. There was a YouTube settings guide for DCS and I thought this was a VR tweaking tool like OXR Toolkit, not very explained. But I have just found out DCS is a Digital Combat Simulator. The settings are game settings,
Thanks again ‘donka73’. I tried all your suggested settings for my system. This is for MSFS, and VD only. I will try including OXRTK later as it is a bit fiddly to use. This a a Pico 4 screenshot (image section) Not VR zoom. From cockpit seat. It is noticeably clearer, but not a great deal. Maybe OXRTK will make it even clearer. I will try later. However, I have a returned ongoing problem with my throttle, unable to ‘take off’ to fly as the throttle keeps jerking. I keep on and on and on keep getting this problem re-occur? My Saitek X52 works fine in Windows 11 controller settings and also Aerofly Flightsim, and even in default mode it happens? I feel like like smashing the X52 to pieces, but I feel if I got another Flight Stick the problem would remain. I really do need help with this, as I have made many many posts about this problem. This is more important than getting a sharp image in VR.
Sure, if your fps are okay, you can try the OpenXR Toolkit to bump up the override resolution which will help with overall clarity but you really need a strong GPU to get the most out of that option.
As for your throttle, i’m assuming this affects all aircraft? If you unplug the throttle, the issue goes away? It could be competing binding for throttle axis or still potentially a hardware defect.
1 Like
Thanks again. The RTX3090 was expensive enough, no chance in upgrading to a RTX4090 at about £2000. High end GPU’s are outrageously over-priced, costing as much as the whole PC! Ultimate system for FSVR High End CPU, RTX4090, and a Varjo XR-4 , but costing thousands. My VR is now is respectable, even the scenery and airport buildings look sharper. I hope to try OKRTK sometime today. The Saitek X52 throttle must be conflicting again, but cant work out where or what to do, to finally cure it. The top pinky button (normally to operate brakes) has never been recognised by MSFS. It works fine in Win 11, and AeroFly. MSFS must still have conflict bugs? It does not like the X52?
The RTX3090 is a good card - you will get good performance out of it in VR as you are finding. It’s more about trying various combinations of settings with that card to find what works for you. I would recommend the 72Hz mode in the headset with SSW enabled so you only need to achieve 36fps in the sim to achieve a smooth 72fps in the headset and DLSS will certainly help here.
As for OpenXR Toolkit, that will let you select fixed foveated rendering with Quality preset which will give you another solid boost in frames and the degraded part of the image with this setting is pretty much obscured by the softer parts of the Pico lenses out towards the edges. This will hopefully provide enough headroom to bump up the override resolution a bit to add some more clarity to the image.
2 Likes
Sounds like the X52 is fine but another device is conflicting with it as mapped in MSFS. Do you have ANY other USB control devices plugged in (game pad, other joystick etc.)?
Thanks for reply about the X52. Other than the keyboard, mouse and Saitek X52 there are no other devices connected to any USB port. And why the top pinky button (normally brakes) has never worked in FS is a mystery? Sometime ago when I contacted FS Support, they said the X52 must be faulty, and dismissed the support, despite the fact that Win the11 controller setup, all controls switches and buttons work fine as they do in AeroFly Flightsim. It has to be something to do with FS. There has to be a bug in FS, that will not go away? I do not believe that buying another Flight Controller will solve the problem? It is a shame because this problem has preventing me from playing FS, and end up playing in AeroFly instead. Although a good Flightsim, it does not match up to MSFS.
Try deleting all your controller profiles and see if the issue remains?
System: 4090, 7800x3d. After about a week of fiddling and much frustration, I tried the following with very surprising results:
Dissable Open XR toolkit. Set up a dedicated router in AP mode. Set VDXR as the runtime in Virtual desktop. God mode in VD. Codec auto in VD. 150mb streaming. Timewarp always.
I can now run almost full ultra settings TAA with latency at around 45. Framerate at 90.I think a combination of the dedicated access point and limiting the programs involved in the process is the key. Good luck. Its worth the effort!