On 2/11/2021 at 3:06 PM, mpo910 said:

Confirmed! 

How about 461.72? Did you try it? Render option is back to Reverb without jiterry?

Edited March 3, 20215 yr by YoYo

7 minutes ago, YoYo said:

How about 461.72? Did you try it? Render option is back to Reverb without jiterry?

Yes I have this one installed (461.72).

The jitter with Pre-Render is still existing. I talked to the devs of LM and they told me that WMR does not support this (they never did actually).

They are looking into this. 

Marcus

This is on Microsoft latest virtual show XBOX holding one later this month.

 Microsoft's Big Step Forward in Mixed Reality - YouTube

Could LM implement this in a future update.

I experience a problem in P3D 5.1 with my new HP Reverb G2. When looking around outside the cockpit it sometimes seem like the world is shaking slightly. What could it be ? I don't see this in DCS and X plane.

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).

5 hours ago, jfri said:

I experience a problem in P3D 5.1 with my new HP Reverb G2. When looking around outside the cockpit it sometimes seem like the world is shaking slightly. What could it be ? I don't see this in DCS and X plane.

It is P3D....for sure. 

They need to optimize. That would be great. I hope it becomes more smooth. This stuttering is not good. 

1 hour ago, mpo910 said:

It is P3D....for sure. 

They need to optimize. That would be great. I hope it becomes more smooth. This stuttering is not good. 

I actually think P3D's implementation of VR is decently optimised by flight sim standards.

I've been flying in VR close to 100% of the time since it was introduced to P3D late in the V3 era (and was using flyinside prior to that).

Using a 2080TI, 9900K @ 5 Ghz and Oculus HMDs (currently Quest 2 and Rift S, previously DK2, Rift CV1, Quest 1).

I find Oculus HMDs are better than my WMR headset. Don't own Vive for comparison.

If your VR is not smooth - turn settings down (traffic, shadows, dynamic reflections). Disable supersampling, it's not really necessary on a modern headset. Stick to Oculus. Choose a plane that has good and stable frame rates (Maddog = YES! FSL bus = NO! PMDG 747-8, NGXu, T7 - OK).

I tend to VR fly heavies, so I normally sim with orthoscenery (best for high-altitude flight), autogen off, using payware airports. And I basically always fly with EA on, because the clouds are so much better in VR, and it's 2021 so we really should not be flying with 2D sprites for clouds! Also, EA makes the scenery look very next-gen, as opposed to legacy mode which looks very cartoon-like wonce you get used to EA or MSFS.

When I'm in a GA mood, I normally use A2A planes which work great in the sim. 

For me at the moment it's 90% P3D VR, 5% MSFS VR GA, and 5% DCS and X-plane for me.

I'd definitely like to see some further improvements, but at the moment P3D remains my favorite sim for VR flight.

 

 

10 minutes ago, OzWhitey said:

P3D's implementation of VR is decently optimised

THIS

Beau Hollis (Dev at LM) is aware of these things.

On 3/3/2021 at 8:26 AM, mpo910 said:

Yes I have this one installed (461.72).

The jitter with Pre-Render is still existing. I talked to the devs of LM and they told me that WMR does not support this (they never did actually).

They are looking into this. 

Marcus

Thx. Maybe something new in 5.2 patch... I hope .

Chaps, wondering if anyone else has noticed this problem:

1. I usually fly with Oculus HMD, using Steam mode in P3D for VR. This has always given the smoothest tracking.

2. Since returning from vacation, I've noticed a new problem. When using VR in steam mode, VR only works when the Steam VR app has focus priority. So if you click on the P3D window (which you obviously need to do to to push buttons etc), VR goes haywire and starts to crash.

3. This never used to happen - I've put in  hundreds of hours of VR time with Oculus in Steam VR mode in this sim - and I didn't make any sim changes that I know of between this working and not working. Therefore, it logically has to be an issue with either an NVidia driver update, a Windows update or a Steam VR update.

Questions:

1. Have other people experienced this?

2. Is there a setting in P3D, Steam VR or the Nvidia app that can be modified to solve this problem? Or do I need to use an older version of Steam VR etc?

Thanks for any advice!

8 minutes ago, OzWhitey said:

Chaps, wondering if anyone else has noticed this problem:

1. I usually fly with Oculus HMD, using Steam mode in P3D for VR. This has always given the smoothest tracking.

2. Since returning from vacation, I've noticed a new problem. When using VR in steam mode, VR only works when the Steam VR app has focus priority. So if you click on the P3D window (which you obviously need to do to to push buttons etc), VR goes haywire and starts to crash.

3. This never used to happen - I've put in  hundreds of hours of VR time with Oculus in Steam VR mode in this sim - and I didn't make any sim changes that I know of between this working and not working. Therefore, it logically has to be an issue with either an NVidia driver update, a Windows update or a Steam VR update.

Questions:

1. Have other people experienced this?

2. Is there a setting in P3D, Steam VR or the Nvidia app that can be modified to solve this problem? Or do I need to use an older version of Steam VR etc?

Thanks for any advice!

Hi Rob.

I have not had this issue even once. I am using SteamVR BETA 1.16.8 with WMR and a HP Reverb G2. So not exactly your setup.

I have set turned on "SteamVR Always on Top" here:

-Settings (click left upper corner in STEAMVR)

-General TAB

At the Developer Tab everything is set to "off".

I have the small  steamvr window on my 2d screen visible. But also "minimizing" it makes no difference. Also playing with the P3D window, pushing buttons, switching fullscreen to windowed mode and vv, while VR is on, does not do any harm.

The only difference I noticed with P3D V5 is, closing SteamVR, after VR in P3D is disabled, does prompt me to close P3D. LM is aware of this. They had to make a workaround to avoid a memoryleak within SteamVR (ticket is active at STEAM/VALVE).

Marcus 

 

2 hours ago, OzWhitey said:

I actually think P3D's implementation of VR is decently optimised by flight sim standards.

I've been flying in VR close to 100% of the time since it was introduced to P3D late in the V3 era (and was using flyinside prior to that).

Using a 2080TI, 9900K @ 5 Ghz and Oculus HMDs (currently Quest 2 and Rift S, previously DK2, Rift CV1, Quest 1).

I find Oculus HMDs are better than my WMR headset. Don't own Vive for comparison.

If your VR is not smooth - turn settings down (traffic, shadows, dynamic reflections). Disable supersampling, it's not really necessary on a modern headset. Stick to Oculus. Choose a plane that has good and stable frame rates (Maddog = YES! FSL bus = NO! PMDG 747-8, NGXu, T7 - OK).

I tend to VR fly heavies, so I normally sim with orthoscenery (best for high-altitude flight), autogen off, using payware airports. And I basically always fly with EA on, because the clouds are so much better in VR, and it's 2021 so we really should not be flying with 2D sprites for clouds! Also, EA makes the scenery look very next-gen, as opposed to legacy mode which looks very cartoon-like wonce you get used to EA or MSFS.

When I'm in a GA mood, I normally use A2A planes which work great in the sim. 

For me at the moment it's 90% P3D VR, 5% MSFS VR GA, and 5% DCS and X-plane for me.

I'd definitely like to see some further improvements, but at the moment P3D remains my favorite sim for VR flight.

 

 

I agree. Compared to MSFS the performance in P3D v5 is phenomenal. I get jitter every once in while but with SteamVR, it's very smooth between jitters. I belive these occur when scenery is loaded.

I just whish I could make the night darker with the Rift S. It's dark enough on the monitor but in the headset it's way too bright. I suppose this is a limitation of Rfit S rather than P3D, though.

5 hours ago, mpo910 said:

Hi Rob.

I have not had this issue even once. I am using SteamVR BETA 1.16.8 with WMR and a HP Reverb G2. So not exactly your setup.

I have set turned on "SteamVR Always on Top" here:

-Settings (click left upper corner in STEAMVR)

-General TAB

At the Developer Tab everything is set to "off".

I have the small  steamvr window on my 2d screen visible. But also "minimizing" it makes no difference. Also playing with the P3D window, pushing buttons, switching fullscreen to windowed mode and vv, while VR is on, does not do any harm.

The only difference I noticed with P3D V5 is, closing SteamVR, after VR in P3D is disabled, does prompt me to close P3D. LM is aware of this. They had to make a workaround to avoid a memoryleak within SteamVR (ticket is active at STEAM/VALVE).

Marcus 

 

Thanks Marcus, I have the same settings that you mention, but - as noted - once the small 2D steam VR window is not in focus, my VR crashes. This never used to be a problem on my system.

One thing I'm wondering, is whether it is something to do with my OpenXR runtime. Is anyone able to tell me what this is set to on their system:

1. Go to Steam VR --> Settings --> Developer, and see what it says under "Current OpenXR runtime". Mine says "Oculus", and I have the option to set it back to SteamVR (which doesn't seem to help).

2. Also, check the registry: Open regedit, and go to computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1. If you click on the ActiveRuntime REG_SZ, what is the value? Mine is currently set to C:\Program Files\Oculus\Support\oculus-runtime\oculus_openxr_64.json

The reason I'm suspicious that this may be the problem is that it was necessary to change the ActiveRuntime value in the registry (as above) to get MSFS VR working. I wonder if I may have wrecked P3D v5 SteamVR in the process, but I'm not 100% sure what the normal default settings are.

Any help greatly appreciated! 🙂

 

 

 

 

43 minutes ago, OzWhitey said:

 

1. Go to Steam VR --> Settings --> Developer, and see what it says under "Current OpenXR runtime". Mine says "Oculus", and I have the option to set it back to SteamVR (which doesn't seem to help).

2. Also, check the registry: Open regedit, and go to computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1. If you click on the ActiveRuntime REG_SZ, what is the value? Mine is currently set to C:\Program Files\Oculus\Support\oculus-runtime\oculus_openxr_64.json

 

 

 

 

 

Hi Rob!

1. I have SteamVR active and I am currently not using OpenXR. 

2. Corresponding to 1. my value is set to I:\Steam\steamapps\common\SteamVR\steamxr_win64.json

You can switch in SteamVR very simple between the values Oculus and OpenXR runtimes. IF it does not help, just return by clicking "Default" again. Oculus should be set again (as your Default)

If the issue is not solved I would proceed as follow:

1.  Uninstall SteamVR (within Steam -> uninstall)
2.  Uninstall OpenXR (via MS Store -> uninstall)
3.  Uninstall WMR (via Device Manager)
4.  Uninstall the Oculus software
5.  Install WMR
6.  Install Oculus software
7.  Install OpenXR
8.  Install SteamVR

I hope this will help.

Also trying

-sfc /scannow or even

-dism /Online /Cleanup-Image /RestoreHealth

in Admin Powershell to find and repair any corrupted files which may cause the issue is very save to run! I use it very very often (1x a week or more often if I think something is wrong).

EDIT 1: I will test OPENXR runtimes now to see if "your" issue occurs on my end too.....give me a minute or 5

EDIT 2: Tested with OPENXR set as Active runtime.....no issues on my end.

Marcus

Edited March 4, 20215 yr by mpo910

15 hours ago, OzWhitey said:

I actually think P3D's implementation of VR is decently optimised by flight sim standards.

I've been flying in VR close to 100% of the time since it was introduced to P3D late in the V3 era (and was using flyinside prior to that).

Using a 2080TI, 9900K @ 5 Ghz and Oculus HMDs (currently Quest 2 and Rift S, previously DK2, Rift CV1, Quest 1).

I find Oculus HMDs are better than my WMR headset. Don't own Vive for comparison.

If your VR is not smooth - turn settings down (traffic, shadows, dynamic reflections). Disable supersampling, it's not really necessary on a modern headset. Stick to Oculus. Choose a plane that has good and stable frame rates (Maddog = YES! FSL bus = NO! PMDG 747-8, NGXu, T7 - OK).

I tend to VR fly heavies, so I normally sim with orthoscenery (best for high-altitude flight), autogen off, using payware airports. And I basically always fly with EA on, because the clouds are so much better in VR, and it's 2021 so we really should not be flying with 2D sprites for clouds! Also, EA makes the scenery look very next-gen, as opposed to legacy mode which looks very cartoon-like wonce you get used to EA or MSFS.

When I'm in a GA mood, I normally use A2A planes which work great in the sim. 

For me at the moment it's 90% P3D VR, 5% MSFS VR GA, and 5% DCS and X-plane for me.

I'd definitely like to see some further improvements, but at the moment P3D remains my favorite sim for VR flight.

 

 

I have tried lowering my settings and it helps very little if anything. I tried a flight from 3W5 Orbx airport and it was almost unusable. It was somewhat better at another airport PAGO Int NSTU. So maybe where I fly matters a lot. For me P3D hit performance very much in VR (have the same experience in MSFS).
I was told that with my 2070 Super video card I should be fine.