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.

Featured Replies

Started happening after the last service update. It'll be working fine for a long time then the display will go black for a second or two and start displaying properly again. 5-10 seconds later, it will do it again. After that, it doesn't do it for a long time.

It's a Reverb G2, Win10, 3070Ti. I think it's something other than the headset because other stuff works fine with no weird blanking. 

Any idea what's going on?

Ryzen 7 7800X3D/B650 X AX | 5090 | 32gig | Win10 | Pimax Crystal Light

I have had the same issue for a very long time with an RTX4090 and I913900k. I have given up on finding a solution and I’m just resigned to waiting for MSFS2024. Hopefully, this will not happen with the new sim.

i know this is not helping you, but at least you know you are not alone and it’s probably not a hardware issue. 😊

I9-13900K, RTX 4090, Reverb G2, Simrig Motion platform

Both myself and my brother-in-law have had exactly the same issue on our respective systems immediately after the SU15 upload.  We both use Reverb G2 headsets, my GPU is a 4080 and my b-i-l's is running on a 3080Ti.

I had updated the nVidia driver on mine immediately before and thought it might be that so I reverted to the previous version - but it made no difference.  I then found out that my B-i-l's was having the same issue with his unchanged driver.

With it being a Reverb G2, my next thought was 'cable!'.  But it would have been more than a coincidence for b-i-l's newer set would have the same issue at exactly the same time.  I did all the normal checks and concluded that the cable was fine.  

I then thought 'settings!'   Yup - even though my 'PC' graphics settings were unchanged from pre-update, nevertheless all of my 'VR' graphics settings had been switched back to default during the update.  And the trouble is that the default settings have a lot of stuff in them which makes little visual impact but a massive impact on the higher resolution headsets.  Luckily, I had a note of my previous settings, changed them back and, for me, it sorted it. 

I've done the same with b-i-l's (I built his gaming PC for him to be able to use MSFS in VR) and that particular issue is also now resolved, although he is still getting some full CTD's randomly in some flights which we haven't bottomed yet and which, presumably, is a different issue    

Edited by AJZip

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author

Hmm. That's interesting, and annoying because I was not smart enough to keep notes of my old settings. but I bet that's it, because all my controller and difficulty settings got blanked out awhile back too.

Ryzen 7 7800X3D/B650 X AX | 5090 | 32gig | Win10 | Pimax Crystal Light

17 hours ago, eslader said:

Hmm. That's interesting, and annoying because I was not smart enough to keep notes of my old settings. but I bet that's it, because all my controller and difficulty settings got blanked out awhile back too.

Well, it's certainly worth checking.  I'm sure that if this had happened to everyone there would have been an avsim post-fest - and that didn't happen.  But it certainly did with my statistically sound sample size of two 😄

 

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

I had this issue today combined with stuttering in urban areas.

Turned off the cache completely and all is well now.  Butter smooth in VR.  i7 11700K and 4070

My suspicion is that writing to the cache isn't queued for spare CPU time and as is the way with MSFSD, a bottleneck in the CPU load will take some time to clear.  A bit of overload results in stuttering, but as soon as there's a real bottleneck it has to sit back and clear the code.

This is my suspicion anyway.

Create an account or sign in to comment

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.