Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

VR performance on high end System

Featured Replies

17 hours ago, blueshark747 said:

You guys are starting off with some awfully high supersampling.....I wouldn't expect to keep performance stable past 1.3  personally

Personal choice I brought V5 day 1 and started on 1.3 , 1.4 would crash my old 2080. After HF1 I could mange 1.5 to 1.6 . Changing to higher vram card  allowed me to take it higher settled on 1.7 mainly due to sharpness V performance plus 1.6 for some reason I get graphic corruption on 1.6 from time to time. If you are happy with 1.3 great lower vram and better performance way to go. Disabling adaptive gpu  performace scale helped a lot via OTT never seemed to do anything with Ccculus debug tool. Then along came 2 days ago a compulsory Occulus performance went down and no longer able to set   adaptive gpu  performace scale. Upshot occulus now control my SS again , sometimes looks great sometimes rubbish . Wish I could set this and make it stick. Makes a big difference to picture quality when it works .

My understanding is  If it's on adaptive, then if performance falls too low, it will dynamically scale back the resolution of what is being rendered to keep performance at the desired level, but at the cost of visual clarity.

Sorry I want to make that choice myself P3D is not a FPS and I tune my system to run on low smooth FPS

Edited by cannow

Colin hodds

I7 9700K,nvidia 3090 ,ssd ,32gig 3200mhz ram ,win10,prep3d

Noticing that users get performance problems, even with 2080 GPU's,  while using Supersampling above 1.3 are most of the time Rift-S users.

V5 is also vram hungry so combining with "only" 8Gb Vram and High settings in the sim you can quickly encounter problems.

It seems that WMR VR headsets with the new DX12 engine have less problems or do I have to say, better performance?

I can imagine that 1.5 SS in OTT is the same as 1.5 SS in SteamVR and I can use SS at 200% (my optimum default is 180%) without any problem and high sim settings even with inside 8xSSAA and reaching 45 fps. 

For the record, I'm NOT using EA, shadows, reflection  and dynamic lights because that are real performance killers in High Res. VR.

Monitoring with VRfps I'm using most of the time 9 Gb and in areas like ORBX TE The Netherlands with Tampa EHAM 10,5Gb Vram 

I'm using the Reverb on a i5-9600K (4,6Ghz) 32Gb ram and Titan XP Pascal 12Gb.

As mentioned earlier in these post, for me there is a hugh performance boost compared to the V5 HF1 version.

Happy landings...

Edited by simba_nl

On 7/4/2020 at 5:40 AM, cannow said:

Personal choice I brought V5 day 1 and started on 1.3 , 1.4 would crash my old 2080. After HF1 I could mange 1.5 to 1.6 . Changing to higher vram card  allowed me to take it higher settled on 1.7 mainly due to sharpness V performance plus 1.6 for some reason I get graphic corruption on 1.6 from time to time. If you are happy with 1.3 great lower vram and better performance way to go. Disabling adaptive gpu  performace scale helped a lot via OTT never seemed to do anything with Ccculus debug tool. Then along came 2 days ago a compulsory Occulus performance went down and no longer able to set   adaptive gpu  performace scale. Upshot occulus now control my SS again , sometimes looks great sometimes rubbish . Wish I could set this and make it stick. Makes a big difference to picture quality when it works .

My understanding is  If it's on adaptive, then if performance falls too low, it will dynamically scale back the resolution of what is being rendered to keep performance at the desired level, but at the cost of visual clarity.

Sorry I want to make that choice myself P3D is not a FPS and I tune my system to run on low smooth FPS

Absolutely solid info!

I'm on a Rift S also

Asus Maximus X Hero Z370/ Windows 10
MSI Gaming X 1080Ti (2100 mhz OC Watercooled)
8700k (4.7ghz OC Watercooled)
32GB DDR4 3000 Ram
500GB SAMSUNG 860 EVO SERIES SSD M.2

Xplane 11 with Vulcan works with VR.  P3D is okay with VR with light addons, start adding good addons, well there it goes.  It is the engine.  It works great in 2D Monitor mode but VR it is just crappy.

I am just blown away with Orbx TE in Xplane 11.50Beta13+Vulcan; nothing like that is in P3D VR.  

6 hours ago, Skywolf said:

Xplane 11 with Vulcan works with VR.  P3D is okay with VR with light addons, start adding good addons, well there it goes.  It is the engine.  It works great in 2D Monitor mode but VR it is just crappy.

I am just blown away with Orbx TE in Xplane 11.50Beta13+Vulcan; nothing like that is in P3D VR.  

Yep, you know what you are talking about. A few light addons like ORBX TE Netherlands in tandem with Tampa's EHAM and 8xSSAA is giving me only 45 fps and a shimmer free experience so I think I will deactivate and go back to Shimmer paradise XP11.

Oh, I'm sorry, I think it's my HiRes Reverb WMR headset that creates a shimmer problem with Xplane11,  silly me, I better have chosen a Rift-S for Xplane for getting a shimmer free experience. 

But let's get serious and let me make a educated guess.... You are a cheerleader of Xplane11...  but I am more curious how MSFS 2020 will catch the VR sim pilots.

Happy landings...

Edited by simba_nl

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.