Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

90 Good

About glider1

  • Rank

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

2,188 profile views
  1. Add this strange message to the list on the default scenario on a default plane:
  2. Had the same thing happen to me on almost same spec machine and Reverb 1. Not 100% sure how I fixed it but at least try these two: - switch "hardware accelerated GPU scheduling" to off in windows 10 settings - default all your nvidia GPU settings - also make sure that no overlays like windows game overlay (win-G key) aren't running At some point the problem disappeared from my system. A week ago I was getting headset stuttering tracking my head movements. It would happen in P3D or not. Wasted my time reinstalling WMR, SteamVR etc. Turned out defaulting all the Nvidia GPU settings fixed it.
  3. Yeah I used to get that too - annoying. Something is wrong with the installation. Try re-installing as administrator and read their forums for help but support is slow. It is a layered install too. You need Envdir installed first before Envshade.
  4. Did you try the funclibrary.fxh file replacement fix that used to *sort of* work with previous envshade?
  5. Since the latest versions of either SteamVR, WMR or Nvidia drivers (not sure which), not only does pre-render no longer work but also I'm getting stuttering even on the desktop whenever the CPU is slightly busy. It has to be a threading bug. (System 9700K, Reverb, 2080TI, 32GB, W10).
  6. Thanks Robmw glad you got it going. CumulusX as an addon works even better in v5 than v4 because the general performance of the sim is better. Thermalling in a tight turn produces less stuttering. It is important since I do the gliding in VR. CumulusX even works in Enhanced Atmospherics mode but it tends to hide the CumulusX clouds a lot which makes thermals harder to spot. The only problem I haven't solved, wonder if you have, is that even though I have a registered version of CumulusX I can't find a way to get it to display "CumulusXDLL true" in the debug menu. I think the DLL used to be an asset that CuX used in DLL.xml to fix a bug that existed in Vista and Windows 7 but it isn't technically needed for us in later versions. The best fun I'm having right now with it is to use Simlogger as an addon to replay recordings of real world flights that pilots have uploaded to OLC gliding website and then fly the same task over the same scenery with the playback running and compare results. Simlogger is still an amazing app. Let me know if you need any information on anything to do with gliding in P3D. I still do a lot of gliding in it and will continue to until MS2020 produces a better thermal simulation than CumulusX.
  7. I had the same problem P3D doesn't switch over automatically to VR on wireless. Assuming you have got Virtual Desktop working and are playing other games wirelessly on the quest-2 make sure SteamVR is already running start P3D enable SteamVR in the menu when in the cockpit on the 2D desktop screen short click the button on the left controller for the Quest-2 that has the three lines stamped on it. This will bring up the Virtual desktop menu select switch to VR in virtual desktop then it will cause P3D to switch to full virtual reality
  8. The compression over wireless degrades quality a bit depending on how good your router is. You may have 5G but that doesn't necessarily make it a good router. A good router has extra dedicated processing. People on wireless gaming tend to go for dedicated routers and the developer of Virtual Desktop that makes this all possible has said this himself. But if you are getting it to work good! The image quality on a Quest-2 over a dedicated quality wifi5- or 6 router is much better than Oculus CV1 comparable with a Rift-S but not as good as a Reverb. Instruments in GA aircraft are readable. You have to lean forward a bit to read the really small text. All depends on how good your GPU is too.
  9. 5G router quality varies a lot. It isn't just that it is 5GHz but fast routers also have microprocessors inside to efficiently process the data packets. The easiest way to tell is to use Virtual Desktop which can show you statistics about your connection speed and latency.
  10. The only other thing is whether the VR software either WMR or SteamVR automatically changes some settings when a different headset is detected. You'd have to go through all the settings and verify that they are identical for each headset.
  11. Triple check that your max texture resolution is set to 1024 even if you have more than 8GB VRAM. Device hung has many causes. Check that you haven't unknowingly increased the load on your GPU more than you did with the G1. If the settings are identical the device hung problem should be the same on either headset.
  12. I've noticed recently been getting no device hung errors (fingers crossed) once I reduced texture resolution to 1024 which still produces acceptable visual quality in VR on my 2080TI.
  13. OVR Toolkit does the job for me but there is a bit of a learning curve. I find the native WMR desktop too unstable.
  14. I had P2A "freeze" recently. Everything responded slowly including the interface, recognition etc. It was because I had P2A running on the same cores as the sim that were already running at 100% usage. There was no CPU headroom left. The freeze disappeared Once I reduced the CPU core usage on the cores that P2A were on.
  • Create New...