Switching from Reverb to Q3... could use some pointers WRT OpenXR, etc

[1Sascha]

Q3 is in the mail and will arrive here today, so... anything I need to be wary of when I do the update? I want to continue to use OpenXR as I've yet again read that SteamVR is still a performance hog, so... how do I go about this?

 

Do I need to uninstall and re-install OpenXR or is it just a matter of installing the Oculus app, plugging in the new HMD and then bypassing SteamVR in OpenXR tools?

 

 

Any pointers would be appreciated.

 

 

S.

Edited October 2, 2024 by 1Sascha

[1Sascha]

OK.. had to do all this in a bit of a hurry, but I've only gotten so far before things stopped working.

 

- Managed to link up the Q3 via cable (2.9 Gbps connection, so pretty good I reckon)

- Double-checked OpenComposite to see that it, not SteamVR, was still set as default. Also updated OpenComposite while I was at it.

- set Oculus as default OpenXR runtime (was on WMR before)

- downloaded that stupid Horizon App they seem to force on you during the Q3 setup, etc, etc

- went into OpenXR Tools and verified that IL-2 and DCS were still on the list of games

-went into Nvidia settings and Oculus Debug to make my adjustments

 

- finally managed to get that silly desktop-link to work, so I started IL-2 through there via Steam, choosing VR mode (it says it will launch in SteamVR, but I guess that's not true in this case?).

 

And then the game started to load but never got anywhere... all I got was a placeholder loading window (no IL-2 artwork). I tried to cancel/kill IL-2 after 5 minutes of "loading" and couldn't even get that to work. Couldn't exit out of Oculus app because it gave me a "are you sure?" dialogue which I couldn't confirm with either the mouse or the VR controllers, so I ended up re-starting the whole PC.

 

Now... what steps did I miss here... does anyone know?

 

 

S.

 

[Aapje]

Opencomposite is a bridge from SteamVR to OpenXR, so from the games' perspective it is indeed running in SteamVR. However, it's not actually the real SteamVR, but OpenComposite pretending to be SteamVR.

 

Anyway, I don't see any obvious issues with what you did. I personally almost completely copied Sherrifs setup for now, which works quite well for me. Perhaps taking a look at the video helps with spotting any issues:

 

[1Sascha]

Yeah.. that's what I used, too... well that and Virtual Warbirds' guide that he based his video on.

 

I did manage to get it to run. Might have been me not restarting the PC after Oculus/Meta installation - lol!

 

Funny thing is that when I switch to that... err.. Open Link Quest Link mode to get to my PC's desktop and Steam, an IL-2 icon will appear in the head-set app for me to click on, but when I do, it behaves like the stand-alone version (asking me to log in). Only when I go to my desktop "all the way", open Steam and click on the "play"-button will everything work as expected.

 

Been a while since I've used an Oculus set, so I forgot everything about how this stuff worked.. 😄

 

 

All that said: Wow! I can't believe how much better things looks through the Q3 and how much better performance is for me now. I went and started a career mission my G2 would've struggled with in certain situations (Kuban map, airfield defense, a bunch of friendlies and at least 12 enemy planes showing up) and ... no hiccups whatsoever.. nothing. Just steady 90/91 FPS all day long on a 30 minute mission. Plus those lenses really put the Reverb to shame. I can actually glance down at my instruments to check them where on the G2 I would have to move my entire head to see them clearly (dang sweetspot! 😄 ).

 

I went up to 1.3x resolution only in the Oculus app, and I don't rightly know how many pixels I'm gettig in-game (don't think I have a way to check this), but the results are pretty fantastic already. Everything is so clear and crisp and the game runs so much smoother now. I didn't override res in OpenXR tools and only activated CAS under "performance" (no NIS or FSR). I wonder how much higher I can push things with this GPU, but even if I can't push any further, the results I'm getting now are already sweet enough to justify the switch away from the G2.

 

 

S.

Edited October 2, 2024 by 1Sascha

[=420=Syphen]

On 10/2/2024 at 9:34 AM, 1Sascha said:

Yeah.. that's what I used, too... well that and Virtual Warbirds' guide that he based his video on.

 

I did manage to get it to run. Might have been me not restarting the PC after Oculus/Meta installation - lol!

 

Funny thing is that when I switch to that... err.. Open Link Quest Link mode to get to my PC's desktop and Steam, an IL-2 icon will appear in the head-set app for me to click on, but when I do, it behaves like the stand-alone version (asking me to log in). Only when I go to my desktop "all the way", open Steam and click on the "play"-button will everything work as expected.

 

Been a while since I've used an Oculus set, so I forgot everything about how this stuff worked.. 😄

 

 

All that said: Wow! I can't believe how much better things looks through the Q3 and how much better performance is for me now. I went and started a career mission my G2 would've struggled with in certain situations (Kuban map, airfield defense, a bunch of friendlies and at least 12 enemy planes showing up) and ... no hiccups whatsoever.. nothing. Just steady 90/91 FPS all day long on a 30 minute mission. Plus those lenses really put the Reverb to shame. I can actually glance down at my instruments to check them where on the G2 I would have to move my entire head to see them clearly (dang sweetspot! 😄 ).

 

I went up to 1.3x resolution only in the Oculus app, and I don't rightly know how many pixels I'm gettig in-game (don't think I have a way to check this), but the results are pretty fantastic already. Everything is so clear and crisp and the game runs so much smoother now. I didn't override res in OpenXR tools and only activated CAS under "performance" (no NIS or FSR). I wonder how much higher I can push things with this GPU, but even if I can't push any further, the results I'm getting now are already sweet enough to justify the switch away from the G2.

 

 

S.

 

I have both G2 and Q3 here - the Q3 lenses are quite nice and certainly make the cockpit look great. But I find long range spotting is a little reduced on the Q3.  I have better luck spotting long range on the G2, often spotting before my TrackIR wingmen can see stuff. Otherwise the Q3 works great.  I'll be running the G2 till it's officially dead next year, and then move to the Q3 full-time. 

 

For offline foolery in IL2, I've been having good luck with Virtual Desktop wired on 2.5gpbs to an Asus Wifi 6E router. I am shocked at how good VD works with nice networking kit. Darn near as good as a usb cable.

[1Sascha]

43 minutes ago, =420=Syphen said:

For offline foolery in IL2, I've been having good luck with Virtual Desktop wired on 2.5gpbs to an Asus Wifi 6E router. I am shocked at how good VD works with nice networking kit. Darn near as good as a usb cable.

Yeah... like I mentioned in another thread, I'm on a router that, while adequate for my needs, is pretty old and I have to connect my PC to it via a power-line adapter. Which works surprisingly well and has been super stable for over a year now, but I'm not sure that combination would work well to connect the Q3.

 

I did get a €20 cable with a "smart" charging module built in from amazon ("Syntech", IIRC) and that thing's pretty fast:

 

 

Buddy of mine, idiotically, bought the "official" USB-C to USB-C cable for €100 and the app rated it at "only" 2.4 Gbps... 😄

 

Anyway: With 500 Mbps set in ODT and some other tweaks in there I copied from other users, connection is very stable and picture quality is excellent. Still not sure if I should leave the Q3 on max render resolution and 80 Hz and keep using MSAA x2 (which looks awesome) or go back to 90 Hz, ditch MSAA and crank up some other stuff instead. MSAA really pushes my card to its limits (only 8 - 12% headroom left in busy career missions) but from what I've read, using super sampling in ODT is even more demanding.

 

Guess I'll just have to wait for 50xx GPUs to come along and hope that Nvidia won't go nuts again with their pricing... 😄

 

I reckon I'd need 4070 Ti Super or probably 4080/Super levels of GPU power to run 90 Hz and max 5000-something Render Res and MSAA x2 enabled.

 

 

 

S.

 

 

[dgiatr]

1 hour ago, =420=Syphen said:

 

I have both G2 and Q3 here - the Q3 lenses are quite nice and certainly make the cockpit look great. But I find long range spotting is a little reduced on the Q3.  I have better luck spotting long range on the G2, often spotting before my TrackIR wingmen can see stuff. Otherwise the Q3 works great.  I'll be running the G2 till it's officially dead next year, and then move to the Q3 full-time. 

 

For offline foolery in IL2, I've been having good luck with Virtual Desktop wired on 2.5gpbs to an Asus Wifi 6E router. I am shocked at how good VD works with nice networking kit. Darn near as good as a usb cable.

Yeah the same is for me between Q2 and G2 , better long range spotting with G2..

[1Sascha]

On 10/5/2024 at 2:24 PM, dgiatr said:

Yeah the same is for me between Q2 and G2 , better long range spotting with G2..

Funny... I don't fly icon-less in VR often, but I've done so now with the Q3 to test what it was like with the new set and if there was a difference to my experience with the G2.

I found that, for me, certain in-game settings seem to make more of a difference... plus the fact that you don't have to worry about that tiny sweet-spot seems to make things easier for me compared to the G2.

For example: I did run MSAA x2 for a while to bask in the visual glory it provides - but I found that it made it *harder* to spot. Switched to FXAA x4 and I could see the dots out there sometimes even when they were just around max icon-range, so... 10km? With MSAA x2, they had to be much closer for me to reliably see them.

Heck... even spotting my own wingmen at anything further than 2.5k could be a challenge.

 

All that said: The squishy bit in the cockpit (me) could play just as large a role as the hardware or settings here as I don't have *that* much experience with no-icons.

 

S.

Edited October 7, 2024 by 1Sascha

[ATAG_Deacon]

I just picked up the Quest 3. The headset works fine, followed Sheriff's settings for the Quest. When I try to start the game I get the below error message:

 

 

I am losing my mind.

[Aapje]

Did you try this?

 

Or this:

 

https://old.reddit.com/r/il2sturmovik/comments/1epnmml/opencomposite_error/

[ATAG_Deacon]

On 10/16/2024 at 7:17 AM, Aapje said:

Did you try this?

 

Or this:

 

https://old.reddit.com/r/il2sturmovik/comments/1epnmml/opencomposite_error/

Yes, I've downloaded and reinstalled. I can only play the steam version at the moment in VR, not stand alone. It's working well with my current settings, I just wanted to thank you for the reply.

[SvAF/F16_RedChrille]

On 10/21/2024 at 12:47 AM, ATAG_Deacon said:

Yes, I've downloaded and reinstalled. I can only play the steam version at the moment in VR, not stand alone. It's working well with my current settings, I just wanted to thank you for the reply.

Is there a way to play Il2 standalone on the quest 3, I have tried everything soon now but get the openxr error everytime?

[Aapje]

It works for me standalone, with the OpenXR Toolkit.

[SvAF/F16_RedChrille]

On 10/29/2024 at 10:27 PM, Aapje said:

It works for me standalone, with the OpenXR Toolkit.

Well lucky you, I get this error note  whatever I do.....

 

 

[2024-10-31 22:49:21.291] Config::Config:207    - Checking for global config file...
[2024-10-31 22:49:21.291] wini_parse:167    - No config file found at C:\Users\cbrch\Desktop\OpenComposite\Runtime\bin\opencomposite.ini
[2024-10-31 22:49:21.291] Config::Config:226    - Checking for app specific config file...
[2024-10-31 22:49:21.291] wini_parse:167    - No config file found at C:\IL-2 Sturmovik Great Battles\data\opencomposite.ini
[2024-10-31 22:49:21.291] VR_InitInternal2:223    - [once] Initializing OpenComposite - revision e162c7e9be2521a357fba4bee13af85437a1027b (1.0.1399, Remove leftover definitions, 2024-10-28T02:06:38.0000000Z)
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_D3D11_enable
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_D3D12_enable
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_opengl_enable
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_vulkan_enable
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_vulkan_enable2
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_composition_layer_depth
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_win32_convert_performance_counter_time
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_convert_timespec_time
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_composition_layer_cube
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_composition_layer_cylinder
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_composition_layer_equirect
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_visibility_mask
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_KHR_composition_layer_color_scale_bias
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_EXT_win32_appcontainer_compatible
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_EXT_debug_utils
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_OCULUS_recenter_event
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_OCULUS_audio_device_guid
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_FB_color_space
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_FB_display_refresh_rate
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_META_performance_metrics
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_META_headset_id
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_OCULUS_ovrsession_handle
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_EXT_local_floor
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_EXT_active_action_set_priority
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_FB_haptic_amplitude_envelope
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_FB_haptic_pcm
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_FB_touch_controller_pro
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_META_touch_controller_plus
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_FB_touch_controller_proximity
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_OCULUS_external_camera
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_META_detached_controllers
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:149    - Extension: XR_LOGITECH_mx_ink_stylus_interaction
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:154    - Num layers available: 2
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:162    - Layer: XR_APILAYER_NOVENDOR_XRNeckSafer
[2024-10-31 22:49:21.851] DrvOpenXR::CreateOpenXRBackend:162    - Layer: XR_APILAYER_NOVENDOR_XRNeckSafer
[2024-10-31 22:49:21.851] DrvOpenXR::GetXRAppName:59    - Setting application name to OpenComposite_Il-2
[2024-10-31 22:49:21.883] oovr_abort_raw_va:206    - Abort!
[2024-10-31 22:49:21.883] CreateSystemID:86    - OpenXR Call failed, aborting. C:\projects\openovr\DrvOpenXR\DrvOpenXR.cpp:86 CreateSystemID. Error code: XR_ERROR_FORM_FACTOR_UNAVAILABLE
xrGetSystem(xr_instance, &systemInfo, &xr_system)

 

Edited October 31, 2024 by SvAF/F16_RedChrille

[SvAF/F16_RedChrille]

Finally I get the quest 3 working(becuase I am stupid), I am very impressed of the quest 3(going from Hp reverb G1). The sound is weaker but still okay but image is really great. I am glad that I choose quest 3. Now set up everthing else and go flying