Jump to content

Recommended Posts

PatrickAWlson
Posted (edited)

After a pretty long break I'm trying to fly again.  My HP reverb 2 becomes a slide show in combat.  I am flying FC2.  There were maybe 15 planes in the air, 10 in close proximity.  The FPS was saying 30 but in many cases there was extremely noticeable stutter, so maybe 30 was an average but not constant.  When I last played consistently I was not experiencing this.

 

This is the only game that I use VR for, so I don't have any really good references.  

 

OS Name    Microsoft Windows 11 Pro

Processor    Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
Installed Physical Memory (RAM)    32.0 GB
Adapter Description    NVIDIA GeForce RTX 2080 Ti

HP Reverb G2

 

Edited by PatrickAWlson
[CPT]Crunch
Posted

Need to know what hardware your driving it with, not all is equal.

PatrickAWlson
Posted
1 hour ago, [CPT]Crunch said:

Need to know what hardware your driving it with, not all is equal.

 

Added to the OP

Posted
7 minutes ago, PatrickAWlson said:

 

Added to the OP


PM sent, mentioned here in case your PM box is full. :)

ZiggyZiggyStar
Posted

I'm far from an technical whizz at this type of thing but I have a 2080Ti also (with a lesser i7 something CPU) and found OpenXR toolkit when I finally decided I was brave enough to implement it made quite a worthwhile improvement and was not as scary and difficult to get working as I feared. 

PatrickAWlson
Posted

I just tried OpenXR with Open Component.  Initial efforts fail.  When I start the game I get OpenXR Call failed error -13.  The only thing that I saw in the troubleshooting guide that came close was to install an updated VC++ redistribution, which I did, but no luck.

firdimigdi
Posted
4 hours ago, PatrickAWlson said:

I just tried OpenXR with Open Component.  Initial efforts fail.  When I start the game I get OpenXR Call failed error -13.  The only thing that I saw in the troubleshooting guide that came close was to install an updated VC++ redistribution, which I did, but no luck.

 

https://mbucchia.github.io/OpenXR-Toolkit/opencomposite.html#the-game-will-not-start-with-error--13--xr_error_instance_lost

PatrickAWlson
Posted
10 minutes ago, firdimigdi said:

 

Appreciate the attempt, but I'm afraid it doesn't provide a solution.  The instructions are as simple as run Open Composite and press the "switch to Open Composite" button.  When I  open the registry editor the appropriate entries indicating a proper OpenXR install are in place.  The last bit in the instructions is around 32 bit support but that's not a concern.

 

For OpenRX install I just downloaded and executed the MSI.  When I open the OpenRX toolkit I don't see much.

 

There is another error that precedes the -13:

image.jpeg.c7476e143042725bd4d86906c1c74e80.jpeg

 

That one implies that I have to update WMR, but I would think that WMR would auto update.  Googling "createdirect3d11surfacefromdxgisurface winxrruntime" didn't give me anything useful.

Then there is the -13 that follows.

 

image.jpeg.9d35b9862c420f985bc9302eae5047de.jpeg

Varibraun
Posted
On 5/7/2023 at 7:01 PM, PatrickAWlson said:

I am flying FC2.  There were maybe 15 planes in the air, 10 in close proximity.

 

Pat, have you tried the G2 in BoS, or in FC2 not in PWCGFC?

 

I ask because in the little time I have had to try the updated PWCGFC Beta, I was getting some noticeable time dilation with my 13900/4090 in my G2 that I was not seeing in FC Career Mode (or in WWII PWCG).  I wanted to give it some more flying in 15.1 and some config tweaking before mentioning it to you.

 

5 hours ago, PatrickAWlson said:

That one implies that I have to update WMR, but I would think that WMR would auto update

 

Regarding OpenXR, I am tech challenged and need very specific instructions, so FWIW I found this step by step setup video very helpful and at around 6:46 he talks about WMR not auto updating:

 

 

PatrickAWlson
Posted

@Varibraun Thanks for the video.  Didn't help in getting OpenRX to work but it did have some good VR tips.  It also nudged me to update my drivers.  I'll watch it again to see what I might have missed.  

firdimigdi
Posted
11 hours ago, PatrickAWlson said:

For OpenRX install I just downloaded and executed the MSI.  When I open the OpenRX toolkit I don't see much.

 

There is nothing to see when in desktop mode, the OpenXR Toolkit's companion app is just for setting up the options it presents, it won't do anything in your headset.

 

Another crucial tool is this: https://apps.microsoft.com/store/detail/openxr-tools-for-windows-mixed-reality/9N5CVVL23QBT?hl=en-us&gl=us

This allows you to switch the OpenXR runtime versions and also get some troubleshooting information about your OpenXR installation (not to be confused with the OpenXR Toolkit - despite the poorly chosen name, OpenXR != OpenXR Tools != OpenXR Toolkit).

 

Make sure that there is no modified openvr_api.dll, unless you are manually installing one for OpenComposite's per-app installation method, installed in your bin/game directory or any mod that hijacks d3d - 3dmigoto, reshade and I believe the VREM : VR enhancer mod found on this forum do such things (if so you'll likely find d3d11.dll or dxgi.dll files in your bin/game directory, remove them).

Posted
On 5/8/2023 at 9:39 PM, PatrickAWlson said:

Didn't help in getting OpenRX to work

 

Sorry there were no magic bullets in the video.  I know that @firdimigdi is one of our true resident experts on VR, hopefully his advice will get you there.

Posted

It is certainly worth the effort to get Openxr  and the toolkit working. My system is very similar as yours Pat and it made a big difference in performance in the G2. That said it is t the only thing I needed to do to get good performance in IL2 GB. I have to reduce the resolution of the G2 to 70% and make a few concessions in the game graphics settings. Lower shadows, 70 distance mostly. I also set most pwcg settings to low or medium and reduce the number of flights for both sides. With these I get a pretty consistent 90 fps other than a few instances when it drops for a few seconds when a lot is going on. 

PatrickAWlson
Posted (edited)

There is definitely a problem with my OpenRX install.  The CreateDirect3D11SurfaceFromDXGISurface issue posted above is almost certainly the root cause.  Just not sure what to do about it.


Steps:

  1. Download OpenXR-Toolkit-1.3.2.msi  and install
  2. Download Open Composite and unzip
  3. Run Open Composite
    1. Press Switch to Open Composite
  4. Download the OpenRX Toolkit
    1. And ... ?  Everything looked like it was set up
    2. I ran the WMR demo and it worked.  IL2 does not work.

 

 

 

image.thumb.jpeg.1d11e1e2675357c06cae640ca55fb54a.jpeg

Edited by PatrickAWlson
Posted

This rings a bell. Something stupid but this has happened to me a couple of times--after updates to IL-2. The fix? Bring up the Opencomposite switcher and switch IL-2 back to Steam in the configure tab. Start IL-2 with SteamVR. Now close out of it. (might not have to do any of that, I foget really)Now... switch it back to Opencomposite. That should work. Might have to do a restart of the PC before it "sticks" but give that a try before doing anything major.

 

You obviously have OpenXR running in general as the toolkit menu wouldn't generally just show up on it's own.

PatrickAWlson
Posted

@Drano Tried that several times over the past couple of days - mostly on accident :) .  Switch to Steam because I give up, switch back to try again, turn the computer off because I'm going to bed.  Wake up and turn it back on.

NiiranenVR
Posted

Have you put the openxr driver in the il2 mapp - you shall do that manually

( I'm at job so ..... ) 

PatrickAWlson
Posted
5 hours ago, NiiranenVR said:

Have you put the openxr driver in the il2 mapp - you shall do that manually

( I'm at job so ..... ) 

 

No.  Wasn't aware that was a step.  When you get a moment can you post instructions?  Appreciate it.

firdimigdi
Posted

There is no "openxr driver", what Niieraven probably means is the per-app installation of OpenComposite by overwriting the openvr_api.dll in the bin/game dir.

 

OpenXR is an API for which each headset manufacturer provides a runtime implementation of, removing the burden of dealing with different ecosystems and dependencies from game developers and only having to abide with the OpenXR API calls. IL-2 relies on OpenVR(SteamVR) and OpenComposite sits between IL-2 and the OpenXR runtime (provided by the WMR framework in this case) translating OpenVR calls to OpenXR.

 

Since your error message is coming from WinXrRuntime.dll it's safe to assume that OpenComposite is properly installed. There are two possibilities that I can think of: 1. the residual d3d related dll files I mentioned above and 2. long shot, but a borked vulkan installation can cause cryptic messages like that since OpenComposite relies on it for some initialization steps. You can re-install Vulkan related files with a GPU driver rre-installation.

  • Like 1
  • Thanks 1
  • Upvote 1
PatrickAWlson
Posted
2 hours ago, firdimigdi said:

There is no "openxr driver", what Niieraven probably means is the per-app installation of OpenComposite by overwriting the openvr_api.dll in the bin/game dir.

 

OpenXR is an API for which each headset manufacturer provides a runtime implementation of, removing the burden of dealing with different ecosystems and dependencies from game developers and only having to abide with the OpenXR API calls. IL-2 relies on OpenVR(SteamVR) and OpenComposite sits between IL-2 and the OpenXR runtime (provided by the WMR framework in this case) translating OpenVR calls to OpenXR.

 

Since your error message is coming from WinXrRuntime.dll it's safe to assume that OpenComposite is properly installed. There are two possibilities that I can think of: 1. the residual d3d related dll files I mentioned above and 2. long shot, but a borked vulkan installation can cause cryptic messages like that since OpenComposite relies on it for some initialization steps. You can re-install Vulkan related files with a GPU driver rre-installation.

 

I must learn to read more carefully.  You gave me the answer yesterday two days ago and I didn't see it.  The problem was d3d11.dll.  All set.  Thanks.

  • Like 1
  • Upvote 1
PatrickAWlson
Posted

One mission in and it's a definite improvement.  FPS in the mid 40s.   Good enough not to get a really awful stutter.

  • Like 3
Posted
5 hours ago, PatrickAWlson said:

One mission in and it's a definite improvement.  FPS in the mid 40s.   Good enough not to get a really awful stutter.


As expected from a GTX2080ti and the reason why I skipped that tier from my 1080ti (the minimal extra performance vs the extra heat wasn't remotely worth the extra munez, lol).

Glad you now have a playable game dude. :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...