12 hours ago, jfri said:

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.

Something is not right. I only have 1070 and I get acceptable performance in P3Dv5 with higher settings than v4.5. I have a Rift S, though, which is less taxing on the system than your HMD. But you should be more than ok with 2070 super.

Reflections, shadows, draw distance, HD textures, AA too high etc. seem to be the main culprits for VR. I've found that autogen and traffic aren't as much of a problem as they were in the past. Are you using single pass? Stereo is very expensive.

MSFS is a different story. It's ok for low and slow but the airliners, nope.

3 hours ago, andreh said:

MSFS is a different story. It's ok for low and slow but the airliners, nope.

Don't agree, I run the FBW A20N comfortably with fairly high settings.

1 hour ago, SierraDelta said:

Don't agree, I run the FBW A20N comfortably with fairly high settings.

With a 1070? I obviously meant with my hardware since I quoted what I had earlier in the post.

5 hours ago, andreh said:

Something is not right. I only have 1070 and I get acceptable performance in P3Dv5 with higher settings than v4.5. I have a Rift S, though, which is less taxing on the system than your HMD. But you should be more than ok with 2070 super.

Reflections, shadows, draw distance, HD textures, AA too high etc. seem to be the main culprits for VR. I've found that autogen and traffic aren't as much of a problem as they were in the past. Are you using single pass? Stereo is very expensive.

MSFS is a different story. It's ok for low and slow but the airliners, nope.

Yes I discovered on thing that must be wrong. I have followed this guide
https://www.prepar3d.com/SDKv5/prepar3d/virtual_reality/virtual_reality_tuning_guide.html

There I am told to edid P3D config to set fps to 90. And in windows I had it set to 60. But after changing that to 90 in Windows. Unfortunately this was not the cause of my problem. I still have the same problem with shaking display.

And also other problems
First after loading up a flight in P3D my view point is above the plane so hight that it can't be corrected with Chase Plane. Do I really need to reset viewpoint in SteamVr every time ? Also last time even the plane was placed a bit above the ground.
How do we set up VR in P3D 5 so things get correct in the first place ?

19 hours ago, jfri said:

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.

"Fine" is a relative term. My 2080Ti is a lot better in VR than my 1080Ti. But whatever hardware you have, you adjust your settings, your aircraft choices and the places you fly to make the sim work. 

I get significantly better performance in P3D than MSFS with VR - I enjoy flying tubeliners in P3D VR, not so much in MSFS. The Maddog is a great choice if you want a framerate friendly airliner for VR flying.

13 hours ago, andreh said:

 

Reflections, shadows, draw distance, HD textures, AA too high etc. seem to be the main culprits for VR. I've found that autogen and traffic aren't as much of a problem as they were in the past. Are you using single pass? Stereo is very expensive.

 

In P3D I have these VR settings single double update. And the severe shaking when moving the head is gone now. AA is of AF is 4x

Those using the HP G2, do you have the mouse dot visible in the VR cockpit?  I can see the dot on screen, but, not in the VR cockpit.

2 hours ago, DannyR said:

Those using the HP G2, do you have the mouse dot visible in the VR cockpit?  I can see the dot on screen, but, not in the VR cockpit.

I am not able to see thé cockpit at all, the game stay on loading when i put my g2, and i my screen become black.

Edited March 10, 20215 yr by grandfred29

It works for me: VC is sharp, the dot is there and I can use the mouse buttons. What I do not like is that there is no way to switch to the desktop while flying. The Rift-S makes this very easy, you just press the Oculus button on the right controller. In contrast, if I try to invoke the G2 WMR-menu, SteamVR quits and P3D closes. I have informed LM. Why does P3D need SteamVR to control the G2? (MSFS has very good G2 support without SteamVR).

Michael

4 minutes ago, michaelth said:

Why does P3D need SteamVR to control the G2? (MSFS has very good G2 support without SteamVR).

Exactly - and yesterday's MSFS update brought us a good number of VR-specific improvements and fixes.

12 hours ago, grandfred29 said:

I am not able to see thé cockpit at all, the game stay on loading when i put my g2, and i my screen become black.

Have you by any chance used EnvShade and is running VR with single pass? If so, Envshade breaks single pass. You can restore it by reinstalling the client.

5 minutes ago, andreh said:

Have you by any chance used EnvShade and is running VR with single pass? If so, Envshade breaks single pass. You can restore it by reinstalling the client.

Not necessarily. I installed EnvShade 2 days back and, as expected, it killed single pass in non-EA mode. Interestingly, it also wrecked single pass in EA mode, which i was not anticipating.

A complete reinstall of p3d did not fix the issue (i’m sure there are some files somewhere that i need to delete, but it’s not the shader folder in the p3d root directory, because i did manually delete that).

If anyone knows how exactly envshade wrecks single pass, let me know.

And to the VR users out there - stay away from EnvShade, good in v4, not worth the bother in v5.

2 minutes ago, OzWhitey said:

Not necessarily. I installed EnvShade 2 days back and, as expected, it killed single pass in non-EA mode. Interestingly, it also wrecked single pass in EA mode, which i was not anticipating.

A complete reinstall of p3d did not fix the issue (i’m sure there are some files somewhere that i need to delete, but it’s not the shader folder in the p3d root directory, because i did manually delete that).

If anyone knows how exactly envshade wrecks single pass, let me know.

And to the VR users out there - stay away from EnvShade, good in v4, not worth the bother in v5.

If I recall correctly it works like this.

Envshade is installed as an addon. There are several location on your PC where they "put some files" (ProgrammData?, AppData Roaming? AppData Local?? Documents??). I don´t recall them exactly. But you have to look and search for TOGA.

As long as they stay on your PC, they inject their lines of shadercode in the "P3DInstallDirectory\ShadersHLSL\FuncLibrary.fxh" file.

So everytime you delete those HLSL files and set them back to default, they will get enhanced again via reinjected TOGA code when P3D gets started.

That is nasty and the main reason I uninstalled Envshade. I expect, if I uninstall a product, that everything gets "as it was before installing it". 

Search for TOGA directories....you will have to find some and delete them manually.

Then delete ShadersHLSL again, repair your client and that should be it.

Marcus

1 hour ago, mpo910 said:

If I recall correctly it works like this.

Envshade is installed as an addon. There are several location on your PC where they "put some files" (ProgrammData?, AppData Roaming? AppData Local?? Documents??). I don´t recall them exactly. But you have to look and search for TOGA.

As long as they stay on your PC, they inject their lines of shadercode in the "P3DInstallDirectory\ShadersHLSL\FuncLibrary.fxh" file.

So everytime you delete those HLSL files and set them back to default, they will get enhanced again via reinjected TOGA code when P3D gets started.

That is nasty and the main reason I uninstalled Envshade. I expect, if I uninstall a product, that everything gets "as it was before installing it". 

Search for TOGA directories....you will have to find some and delete them manually.

Then delete ShadersHLSL again, repair your client and that should be it.

Marcus

I reinstalled the client and it brought back single pass. I've done it a few times, actually. Worked every time.

But as stated above, no point in bothering with envshade for v5.

Edited March 10, 20215 yr by andreh

4 hours ago, andreh said:

Have you by any chance used EnvShade and is running VR with single pass? If so, Envshade breaks single pass. You can restore it by reinstalling the client.

I use it, i will try to reinstall the client.

Thanks