HP Reverb G2 and iL2 with Openxr tool kit and some Start up changes I made and wow

[firdimigdi]

9 minutes ago, McFly60 said:

after running Dependencies, here below the report

 

As expected, the Vulkan runtime is not properly installed - this is usually installed by the GPU drivers.

 

Try expanding the vulkan-1.dll node and see if it's a dependency of that which is missing - normally it should show up like this:

 

A clean re-installation of the GPU drivers might sort it out however if any of its dependencies are missing or is corrupted you can initiate a system scan from a command line opened up with administrator privileges and typing sfc /scannow in it - it can take a while to complete - this is required since it only depends on OS-related libraries.

[OG__Iceman_VR]

I have had 2 people with crazy issues like this. One had 2 copies of the game installed one steam one website. They bought the steam copy because they didn't know how to tell steam to show " non steam games " for their VR in steam. The other just didn't have their WMR and the composite set to the correct settings. I am working on a new film today that goes step by step on getting this to work. I had made to many assumptions about the basic computer knowledge that left big gaps for someone who was not familiar with how apps work in general. So, I want to make it very organized setups so anyone can understand what they need to do to setup this correctly. 

[OG__Iceman_VR]

Ok I hope this helps. If I missed a step or it doesn't work for you still take you time on the Openxr toolkit website Quickstart | OpenXR Toolkit (mbucchia.github.io) and go step by step. If you still have issues let me know and I will get on discord and walk you through this like I did a few other members already. 

Driver Version 516.59 Nvidia drivers. 

Il2 updated as of 7.1.2022

Edited July 1, 2022 by BlindedVR_The_SUN_isBroken

[McFly60]

On 7/1/2022 at 1:06 PM, Firdimigdi said:

 

As expected, the Vulkan runtime is not properly installed - this is usually installed by the GPU drivers.

 

Try expanding the vulkan-1.dll node and see if it's a dependency of that which is missing - normally it should show up like this:

 

A clean re-installation of the GPU drivers might sort it out however if any of its dependencies are missing or is corrupted you can initiate a system scan from a command line opened up with administrator privileges and typing sfc /scannow in it - it can take a while to complete - this is required since it only depends on OS-related libraries.

 

I have expanded the vulkan-1.dll node. I only noticed that I have five files, while you have three ... I honestly didn't have that clear what I was looking for, so I moved on.

 

So I typed sfc / scannow. At the end the program wrote that it found some corrupted files and fixed them. I tried running IL-2 and it got the usual error message.

Last chance, I visited the NVIDIA site, found the drivers for my GPU (latest relise 3 days ago!), selected "clean install" and installed it.
I restarted the PC, ran IL-2 and ...

It finally works!!

I have only tested the game for a few minutes, but it seems to work better than with SteamVR. At least with a better frame rate with the same game settings.
From now on I will try to optimize performance and quality, but the biggest problem has passed.

 

Thank you very much sir, your support has been very valuable.

 

[firdimigdi]

1 hour ago, McFly60 said:

It finally works!!

 

Excellent news, enjoy.

 

  

1 hour ago, McFly60 said:

I have expanded the vulkan-1.dll node. I only noticed that I have five files, while you have three ... I honestly didn't have that clear what I was looking for, so I moved on.

 

Just to be clear on the methodology:

What we were looking for in that step was to see if any of the other .dll files that vulkan-1.dll depended on were marked with an exclamation mark. That way we'd know where to look next, if they were not marked as problematic or if any of them belonged to the GPU driver package then the GPU driver re-installation would be enough (as it turned out), otherwise an sfc /scannow would be in order and if that was unable to restore them then you could resort to dism (Deployment Image Servicing and Management) to restore them from MS servers.

[OG__Iceman_VR]

So I have a Question. How many of you are using the HP Reverb G2 with HDR setting on and are running a Nvidia card ( 3080 ) or better or less? So Does the new sun hurt your eyes? Mainly when the time of day in game is early sun or late sun is where I can't even fly due to eye strain form light exposure. Leaving me when the same head ach you can get in real life driving into the setting sun with no eye protection. On snow maps its 20x worse for me. I do know I am light sensitive but after this patch I can't enjoy the game much and limited to time of day and weather. Where before it was just a game not a form of torcher. 

[Charlo-VR]

I have a Reverb G2 and a 3090 GPU and leave HDR on (I tried OpenXr but found my long-distance spotting slightly better with SteamVR). I do not find the sun terribly blinding any more than in real life, though I do think the sun was a little less blinding a few patches ago.

 

Either way I use the frame of the canopy or changing the direction I fly to reduce the glare, and use the sun to bounce when I can. I fly almost exclusively Finnish VP MP.

[Youtch]

The consensus is that HDR is bad for spotting, and recommended to be turned off.

[OG__Iceman_VR]

20 hours ago, Youtch said:

The consensus is that HDR is bad for spotting, and recommended to be turned off.

Yes, but we paid for the HDR just like every other player, yet we have to turn the game graphics back 15 years to avoid eye damage.  I don't understand why they don't fix this...

[Youtch]

8 hours ago, OG__Iceman_VR said:

Yes, but we paid for the HDR just like every other player, yet we have to turn the game graphics back 15 years to avoid eye damage.  I don't understand why they don't fix this...

My understanding is that it is not a matter of fixing it, it works well, it just make the spotting harder. So, you can have nice visual with HDR or easier spotting, your choice.

[OG__Iceman_VR]

My issue is with the Sun not spotting. 

12 hours ago, Youtch said:

My understanding is that it is not a matter of fixing it, it works well, it just make the spotting harder. So, you can have nice visual with HDR or easier spotting, your choice.

 

[Chilli_40]

Has anyone had the problem of not being able to stop steam-vr from starting when loading IL-2? All my settings are set for open xr yet no matter how I try and start the game it starts steamvr. I have tried with the steam version and the stand-alone version no difference. The really weird thing is 2 days ago I was able to start the game in openxr from the apps menu in WMR, but that doesn't work now either. 

[firdimigdi]

12 hours ago, Raven4 said:

Has anyone had the problem of not being able to stop steam-vr from starting when loading IL-2? All my settings are set for open xr yet no matter how I try and start the game it starts steamvr. I have tried with the steam version and the stand-alone version no difference. The really weird thing is 2 days ago I was able to start the game in openxr from the apps menu in WMR, but that doesn't work now either. 

 

Make sure that the path to your opencomposite directory is the first one listed in the runtime paths found in c:\program files\openvr\openvrpaths.vrpath

[McFly60]

I had the same problem. Because I'm not an informatical expert, I solved it unistalling Steam and SteamVR... now I'm happy to play by OpenXR, thanks to the help of this fantastic community. No more Steam stuff, and immediated gain in framerate. Then I downloaded OpenXRToolkit, and now I'm searching the best setting for my not excellent hardware. If someone would suggest me from where to start, he will be wellcome!

[Gryphon_VR]

On 7/9/2022 at 9:29 AM, McFly60 said:

I had the same problem. Because I'm not an informatical expert, I solved it unistalling Steam and SteamVR... now I'm happy to play by OpenXR, thanks to the help of this fantastic community. No more Steam stuff, and immediated gain in framerate. Then I downloaded OpenXRToolkit, and now I'm searching the best setting for my not excellent hardware. If someone would suggest me from where to start, he will be wellcome!

My non-excellent hardware is an 8600k and GTX1070. With OpenXR toolkit set to Custom Render of 100% (which is the recommended setting) I got the Tools overlay running in VR and played around with Upscaling using NIS. I settled on 80% with 30% sharpening. Result, 50fps in a dogfight with medium settings, which is way better than I expected with a 1070.

 

Note that every change you make to the Upscaling resolution requires you to restart IL2 before it is effective. Restarting the Mission isn't good enough.

 

All I have to do now is cure the periodic blue screen crashes that dump me back to Mixed Reality home. Sigh...

 

[Gryphon_VR]

On 7/21/2022 at 3:32 PM, Gryphon962 said:

All I have to do now is cure the periodic blue screen crashes that dump me back to Mixed Reality home. Sigh...

I think I fixed the blue screens of death. Well, I've had none in 3 hours today so I might be right. All I did was to put a ziptie around the read headband about 3 inches right of the cable loop, and tightened it so the cable couldn't move. That holds the cable with just the right amount of slack exactly where it needs to be on headset and runs no risk of tweaking the socket. Time will tell...

 

EDIT: I've had one brief blue screen and one blue screen followed by crash. I am now certain that the cause is a loss of head tracking by the headset when I turn head to extreme angles. My next solution is to pull blinds down over a window on the affected side of me to avoid any reflections confusing the tracking cameras. 

 

I've also noticed that by using the Zoom function in OpenXR tools overlay to zoom everything by 1.2x, not only does the cockpit look a more realistic size to me, but the sweet spot seems bigger. Now getting constant 48-50fps in Quick Missions on my 8600k/1070 rig.

Edited July 23, 2022 by Gryphon962

[McFly60]

On 7/22/2022 at 12:32 AM, Gryphon962 said:

My non-excellent hardware is an 8600k and GTX1070. With OpenXR toolkit set to Custom Render of 100% (which is the recommended setting) I got the Tools overlay running in VR and played around with Upscaling using NIS. I settled on 80% with 30% sharpening. Result, 50fps in a dogfight with medium settings, which is way better than I expected with a 1070.

 

Note that every change you make to the Upscaling resolution requires you to restart IL2 before it is effective. Restarting the Mission isn't good enough.

 

All I have to do now is cure the periodic blue screen crashes that dump me back to Mixed Reality home. Sigh...

 

Thanks for the tips.
I tried to adopt them and I think I have achieved an appreciable result, with fps> 40 in a dense scenario and sufficient image quality. But I'm not sure I understand your settings exactly. Could you attach the main screenshots of your settings in the OpenXR Toolkit, at least the ones where you changed the settings?

 

P.S.: This is my hardware composition 

 

 

[Gryphon_VR]

On 7/25/2022 at 1:40 AM, McFly60 said:

Thanks for the tips.
I tried to adopt them and I think I have achieved an appreciable result, with fps> 40 in a dense scenario and sufficient image quality. But I'm not sure I understand your settings exactly. Could you attach the main screenshots of your settings in the OpenXR Toolkit, at least the ones where you changed the settings?

 

 

For some reason I can't capture the toolkit overlay settings in a screenshot, not using the IL2 screenshot key, or the openxr screenshot key. How is this done?

[Gryphon_VR]

Is there an overlay app I can use (while IL2 running via OpenXR / Opencomposite) that gives me GPU and CPU performance data?

[Drano]

OpenXR Toolkit will show frame times in ms for each if that was what you were looking for in an overlay while running IL-2. Will give you a good idea of how much, if any, overhead you might have. Without having that in front of me it's in the first menu in the toolkit where the FPS display is. Think it's called expert settings or something like that. It'll show more things. All the menu items are described in iceman's video further up the thread.

[Gryphon_VR]

I think the cause of my occasional blue screen crash was that I had the 'Use Latest Preview OpenXR Runtime' switch OFF in OpenXR Tools for WMR. With it on, I seem to not be getting crashes anymore. 

 

However, with switch on, using the preview runtime (111.2206.16002), I notice it loses me about 5-8 fps and gives more horizon shimmering than with the legacy runtime (110.2204.7007). So I hope they fix it..!

 

 

Edited July 31, 2022 by Gryphon962

[mbucchia]

1 hour ago, Gryphon962 said:

However, with switch on, using the preview runtime (111.2206.16002), I notice it loses me about 5-8 fps and gives more horizon shimmering than with the legacy runtime (110.2204.7007). So I hope they fix it..!

 

 

Hello,

 

That seems unlikely related since there are no changes relevant to performance with OpenComposite between 110 and 111. I've run several performance benchmarks before green-lighting the release of 111, and there was no performance regression with any of them. There are also no changes that would cause a difference in quality like you have described. The preview 111 has been out for several weeks, and nobody has reported such issues so far.

 

Are you sure you have not altered other things on your setup? Drivers, software updates or settings changes?

 

I will try specifically IL-2 next week and compare 110 and 111, and report back. 

 

Thank you.

[Gryphon_VR]

4 hours ago, mbucchia said:

Hello,

 

That seems unlikely related since there are no changes relevant to performance with OpenComposite between 110 and 111. I've run several performance benchmarks before green-lighting the release of 111, and there was no performance regression with any of them. There are also no changes that would cause a difference in quality like you have described. The preview 111 has been out for several weeks, and nobody has reported such issues so far.

 

Are you sure you have not altered other things on your setup? Drivers, software updates or settings changes?

 

I will try specifically IL-2 next week and compare 110 and 111, and report back. 

 

Thank you.

I agree it seemed unlikely, but to double check before I posted here I ran a mission I'd played a few times - where I get about 48 fps - and with the preview runtime selected it gave me about 41 fps - very noticeable difference. I then left the game, turned the switch off so I was on the older runtime, then reran it - back to 48. Then put switch on to use newer runtime, ran mission again, back to 41. So no doubt in my mind at all that if I have the preview selected on I will get much lower fps.

 

I'd had the preview runtime deselected for about a week and in that time I'd noticed in general how good the landscape looked (no horizon flickering) and the frames were good, but almost every mission I played had crashed at some point. I spent ages monitoring hardware performance to try and find the cause of the crashes but had no joy until I noticed I'd had the preview switched off for about the same time I'd been getting the crashes. So, with preview back on I then had no more crashes. Now ok, that's only in a few hours of play so I cant be sure about the cause of the crashes. But my tests of the fps in same mission with preview on, off, then on again makes me sure there is a performance change - at least on my potato computer.

 

I will add that I think the work you've done is amazing - the performance I was getting with the graphics settings I had, on my computer, using the older runtime, was way better than I expected I'd get. I'm a retired military pilot / systems engineer so I'd be happy to run any specific tests you'd like done to assist you.

Edited July 31, 2022 by Gryphon962

[mbucchia]

Thanks, I will try specifically with IL2, and I'll let you know what I see and if I have follow-up questions. 

[Gryphon_VR]

17 hours ago, mbucchia said:

Thanks, I will try specifically with IL2, and I'll let you know what I see and if I have follow-up questions. 

I've since had a few crashes with the preview runtime, so that aspect of my post isn't relevant anymore.

[mbucchia]

Hi,

 

I have run testing with IL-2 Great Battles. I am using OpenComposite from Files · openxr · Campbell Suter (ZNix) / OpenComposite · GitLab, I did not use the very latest version, but the one just before they added support for F1 22.

 

I tried the game with the same mission, with my HP Reverb G2 in a stationary position (in order to always get the same exact view). I selected Quick Missions, and I picked one of the aerial mission (near the center, adjacent to a tank mission). I used the built-in WMR performance overlay to display the app frame times and the frame rate. I left the mission in Pause in order to get a consistent reading.

 

I have tested both 110.2204.7007 and 111.2206.16002. I repeated the test 4 times in each configuration (so a total of 8 runs). I am getting exactly the same frame rate (of 47 FPS in my case) for all 8 runs. Both CPU and GPU frame times were exactly the same between runs (about 11ms CPU and 20ms GPU, which is in line with a frame rate of 47 FPS).

 

I also tested with OpenXR Toolkit 1.1.4, and got the same exact results.

 

As far as I can tell, there is no performance difference observed between the two version. This is the same conclusion I've drawn from other benchmarks before we released 111.

 

Can you detail your methodology for measuring performance, so we can make sure that you are comparing apple-to-apple?

 

Thanks.

[Gryphon_VR]

Thanks for looking at this so quickly.

 

My fps numbers as quoted yesterday were obtained using the toolkit overlay fps. However, as your testing had more rigor I reran mine doing as close as I could to what you did. 

 

I don't know how to get FPS from WMR, so I use the toolkit fps and read it when the numbers are sitting over the gunsight in cockpit every time. 

 

I ran same quick mission 4 times, switching from 110, to 111, to 110, and 111 again. I closed WMR after every exit from IL2 and rebooted the headset. I got an exact 46 fps for all 4 runs, so I was feeling like an idiot when I remembered that the settings I have migrated to today (close to Default) aren't same as settings I had when this issue came up 2 days ago. I have a copy of the settings I used at that time, so I ran it all again, and this time I was able to reproduce the issue; the runs with 110 gave me 70 and 73 fps, and the runs with 111 gave me 60 and 61 fps. I did a full PC reboot between the first pair of runs 110/111 and the second. I could even see a difference in the hanger at game load - 110 gave 90 fps, 111 gave 81.

 

I attach the setting file that when used should show the difference.

 

NOTE 1: I'm running a GTX1070 - maybe this older GPU isnt playing nice with newer build?

 

NOTE 2: I must also add that as I'm getting game crashes after 10-30 minutes every time I play (but not during these tests) then I might have a config issue that is breaking things. I found my CrashDumps folder was full of il2 crash dumps. I downloaded the Windows Debugger and ran it on my latest crash, and even though I probably have no clue what its really telling me it seems that my crashes are coming from vrclient_x64.dll in the opencomposite runtime folder. I've copied the text of that debug report below and can supply the full dump file if you are interested. My vrclient_x64.dll file is dated 7/19/22.

 

Thanks again, let me know if you'd like me to run some other tests.

 

Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\pboyl\AppData\Local\CrashDumps\Il-2.exe.11732.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 22000 MP (6 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Debug session time: Mon Aug  1 15:07:58.000 2022 (UTC - 7:00)
System Uptime: not available
Process Uptime: 0 days 0:11:38.000
................................................................
................................................................
.....................................................
Loading unloaded module list
.........
This dump file has a breakpoint exception stored in it.
The stored exception information can be accessed via .ecxr.
For analysis of this file, run !analyze -v
ntdll!NtWaitForMultipleObjects+0x14:
00007ffc`9b664b84 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify checksum for common.dll
*** WARNING: Unable to verify checksum for gfxShared.dll
*** WARNING: Unable to verify checksum for fmod.dll
*** WARNING: Unable to verify checksum for fmodstudio.dll
*** WARNING: Unable to verify checksum for sceneman.dll
*** WARNING: Unable to verify checksum for inputinterface.dll
*** WARNING: Unable to verify checksum for landscape.dll

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4156

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 368719

    Key  : Analysis.Init.CPU.mSec
    Value: 312

    Key  : Analysis.Init.Elapsed.mSec
    Value: 124549

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 299

    Key  : Timeline.Process.Start.DeltaSec
    Value: 698

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1

    Key  : WER.Process.Version
    Value: 1.0.0.1


FILE_IN_CAB:  Il-2.exe.11732.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=0000000000000001 rbx=00000020c25ee048 rcx=000001e6aa090000
rdx=000001e6aa090000 rsi=00007ffc630af388 rdi=00007ffc630938b0
rip=00007ffc98fe90f2 rsp=00000020c25ed778 rbp=0000000000000029
 r8=000001e6a9fc30c0  r9=0000000000000001 r10=000001e6a9fc0000
r11=00000020c25ed670 r12=0000000000000001 r13=000001e9351ae8e0
r14=00007ffc630af3b0 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206
KERNELBASE!wil::details::DebugBreak+0x2:
00007ffc`98fe90f2 cc              int     3
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffc98fe90f2 (KERNELBASE!wil::details::DebugBreak+0x0000000000000002)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

PROCESS_NAME:  Il-2.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE_STR:  80000003

EXCEPTION_PARAMETER1:  0000000000000000

STACK_TEXT:  
00000020`c25ed778 00007ffc`62fe6996     : 00000020`c25ee048 00007ffc`630938b0 000001e6`d2557f90 000001e6`dbb1a198 : KERNELBASE!wil::details::DebugBreak+0x2
00000020`c25ed780 00007ffc`62fe68bd     : 00000000`00000001 00000000`00000000 000001e6`bcd532b0 00000000`00000001 : vrclient_x64!VR_Shutdown+0x19f6
00000020`c25edfe0 00007ffc`63058e61     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vrclient_x64!VR_Shutdown+0x191d
00000020`c25ee020 00007ffc`6301e2cc     : 00000000`00000001 3d09cb0d`3f4da996 7fc00000`3f183329 00004cce`bb0ba11b : vrclient_x64!VR_Shutdown+0x73ec1
00000020`c25ee2c0 00007ffc`63006b8f     : 00000020`c25ee380 3f800000`4639b470 00004cce`bb0ba07b 00000000`00000000 : vrclient_x64!VR_Shutdown+0x3932c
00000020`c25ee310 000001e6`abd573a1     : 000001e6`afb96150 00000001`800023b8 00000000`00000000 00000000`00000000 : vrclient_x64!VR_Shutdown+0x21bef
00000020`c25ee350 00007ff7`96639249     : 00000000`000000ff 00000000`000000ff 000001e6`afb96150 000001e9`351aed38 : input!input::InputListener::onAction+0x4251
00000020`c25ee3e0 00007ff7`965f8f25     : 000001e6`b0857170 0000000a`69e79f60 0000000a`69e79f5f 00000000`00000000 : Il_2!Scaleform::Render::Matrix4x4<float>::SetIdentity+0x80ba9
00000020`c25ee5b0 00007ff7`965f8090     : 000001e6`abd71338 000001e6`abd71338 000001e6`abd71338 000001e6`afb96150 : Il_2!Scaleform::Render::Matrix4x4<float>::SetIdentity+0x40885
00000020`c25eeb00 00007ff7`965f09ab     : 000001e6`af4d1900 000001e6`af4d1900 000001e6`af4d1900 00000020`c25eec49 : Il_2!Scaleform::Render::Matrix4x4<float>::SetIdentity+0x3f9f0
00000020`c25eebd0 00007ff7`965f0730     : 000001e6`af4d1900 00000000`00000000 000001e6`af4d1900 00007ff7`9736c710 : Il_2!Scaleform::Render::Matrix4x4<float>::SetIdentity+0x3830b
00000020`c25eecb0 00007ff7`96641f97     : 00007ff7`9736c710 00000000`00000000 00000000`00000000 00007ffc`98fd0e6b : Il_2!Scaleform::Render::Matrix4x4<float>::SetIdentity+0x38090
00000020`c25eed30 00007ff7`9664359f     : 00000020`c2002f2d 00000020`c25ef250 00007ff7`963e0000 00000000`00000000 : Il_2!Scaleform::Render::Matrix4x4<float>::SetIdentity+0x898f7
00000020`c25eee00 00007ff7`96f3cce2     : 00000000`0000000a 00000000`0000000a 00000000`00000000 00000000`00000000 : Il_2!Scaleform::Render::Matrix4x4<float>::SetIdentity+0x8aeff
00000020`c25efa80 00007ffc`9a0c54e0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Il_2!Scaleform::Render::Matrix4x4<float>::SetIdentity+0x984642
00000020`c25efac0 00007ffc`9b5c485b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x10
00000020`c25efaf0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b


STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  vrclient_x64+19f6

MODULE_NAME: vrclient_x64

IMAGE_NAME:  vrclient_x64.dll

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_vrclient_x64.dll!Unknown

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dbae9a22-091d-2e17-e0f2-b2255cce1a1b}

Followup:     MachineOwner

 

 

startup.zip

Edited August 2, 2022 by Gryphon962

[TP_Merlin]

On 6/24/2022 at 4:16 PM, [CPT]Crunch said:

Why are you guys replacing .dll's and not using the current all in one switcher app that updates automatically?  That old system of manual files swap is no longer supported any way.  Your confusing people, it's far simpler than this, and your losing the ability to instantly switch back to steamVR without doing any file swapping.  My game is all stock, no files added or swapped, and it runs just fine.  I can revert to steam with the opencomposite switcher app in a second, and it always auto updates to the current release. 

 

Why would you want to go that route?  What's the advantage?  Does sound like confusion to me.  Been an open composite user since day one.

I read all of the post here and installed  OpenComposite having saved the original .dll and ensuring the steam VR was not enabled and OpenComposite runtime was on, but the game would not run until I manually installed the OpenComposite .dll into the game folder.  Like you this is a vanilla install of IL2. Much quicker loading than SteamVR.

[Gryphon_VR]

Well still getting the once in a while blue screen crash but its rare enough now for it not to be a showstopper. The main thing I did was go through all my apps as listed in windows 11,  uninstalled all the ones I never used, set Let this App Run in Background (under Advanced Options) to NEVER for almost everything. That made a big difference, I was no longer getting a crash almost every Career sortie.

 

I also installed a PCIe USB hub to dedicate to the headset. I don't think that made a difference.

 

At the end of the day I think the PC is losing the thread sometimes as I'm working it real hard. I was surprised to learn from the OpenXR Toolkit overlay that in Career missions I'm getting 'CPU Bound' a fair bit of the time. What settings are most likely to be consuming my CPU cycles?