HP Reverb G2 Display Stops Working

[Ryu8200]

Ever since the latest patch I have an issue where my HP Reverb G2 stops working when switching between different views (F1 to F2,F6, F10 and back to F1)

The desktop re-projection is still working and the sound is still on but the screen just goes blank. 

i-9900K

2080Ti

64GB Ram

Seems other are having the same issue but I have yet to find a solution

dcs.log DxDiag.txt

Edited July 12, 2023 by Ryu8200

[BIGNEWY]

Hi check the timeout settings on your headset and pc displays, see if adjusting it helps. 

[Ryu8200]

No difference @BIGNEWY.

This seems to be directly related to the F15E and how many threads I use in the special menu options.

If I go above the base unit of 4 threads such as up to 6 or 8, this will cause the screen to desync and turn off the display at some point when switching between views. But the rest of the head unit is still working such as the before mentioned sound and head tracking on the main monitor.

Also I can still navigate the sim such as using the menus to exit the sim to the desktop.

[BIGNEWY]

2 hours ago, Ryu8200 said:

No difference @BIGNEWY.

This seems to be directly related to the F15E and how many threads I use in the special menu options.

If I go above the base unit of 4 threads such as up to 6 or 8, this will cause the screen to desync and turn off the display at some point when switching between views. But the rest of the head unit is still working such as the before mentioned sound and head tracking on the main monitor.

Also I can still navigate the sim such as using the menus to exit the sim to the desktop.

Interesting, I would wait for the next update in July, there are some tweaks coming from RAZBAM that may help. 

thank you

[Varry007]

44 minutes ago, BIGNEWY said:

Interesting, I would wait for the next update in July, there are some tweaks coming from RAZBAM that may help. 

thank you

Since we're the 13th of July today, that means the next update will be released in the next "two weeks"? 

[BIGNEWY]

22 minutes ago, Varry007 said:

Since we're the 13th of July today, that means the next update will be released in the next "two weeks"? 

as soon as I have the date I will update the patch status post on the forum. It all depends on internal testing results. 

thanks

[Varry007]

23 hours ago, BIGNEWY said:

as soon as I have the date I will update the patch status post on the forum. It all depends on internal testing results. 

thanks

thx, but i was trying my luck with a witty joke

[Whiskey11]

On 7/12/2023 at 11:52 PM, Ryu8200 said:

No difference @BIGNEWY.

This seems to be directly related to the F15E and how many threads I use in the special menu options.

If I go above the base unit of 4 threads such as up to 6 or 8, this will cause the screen to desync and turn off the display at some point when switching between views. But the rest of the head unit is still working such as the before mentioned sound and head tracking on the main monitor.

Also I can still navigate the sim such as using the menus to exit the sim to the desktop.

This issue existed in the patch after the Sinai was released and I was getting it flying in the F-14.  I am still having this issue in the F-14 and F-15E both on both Sinai and Syria (haven't tested others).  VR Headset goes to sleep when switching from F-10 to anything else a few times.  This problem used to exist "back in ye olden days," went away, and is back again.  I think last time it was a memory leak...

[The_Nephilim]

On 7/30/2023 at 7:56 PM, Whiskey11 said:

This issue existed in the patch after the Sinai was released and I was getting it flying in the F-14.  I am still having this issue in the F-14 and F-15E both on both Sinai and Syria (haven't tested others).  VR Headset goes to sleep when switching from F-10 to anything else a few times.  This problem used to exist "back in ye olden days," went away, and is back again.  I think last time it was a memory leak...

If you want I can test the f14 in Sinai or syria and see if I have it happen? if you guys want me to check but I don't have the F15E.

 

 

EDIT: Well I just was flying the F14 in the Sinai and Syria switching from F10 and F2 and such. I did not have the G2 turn off at anytime.. here is my log incase it might help..

dcs.log

Edited August 3, 2023 by The_Nephilim

[Ryu8200]

Still fighting this issue where when I change views such as from the F10 map to the F1 view causes the headset display to have a hiccup and then the headset display stays black. 

As example this last time there was a quick flash of blue, followed by a quick glimpse of the cockpit and then it black screened the display. Audio still works and the tracking is still working as showed on the desktop monitor. 

Unfortunately the headset does not recover until I exit DCS “to desktop”  by navigating the menus with the head tracking and desktop monitor. 

Any ideas on how to fix this? I know an old firmware the volume was an issue so just incase I turned all volume settings to 90% but this didn’t solve the issue. If it helps I’m using the MT open beta. 

Any ideas on where to start?

[The_Nephilim]

can you take some pics of your mixed reality settings in Windows?

[Ryu8200]

dcs.log

Last log file from OpenXR Toolkit

 

[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_spatial_anchor
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_perception_anchor_interop
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_win32_appcontainer_compatible
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_conformance_automation
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_composition_layer_reprojection
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_spatial_graph_bridge
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_spatial_anchor_persistence
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_palm_pose
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_active_action_set_priority
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_scene_understanding
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_scene_understanding_serialization
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_scene_marker
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_FB_display_refresh_rate
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_eye_gaze_interaction
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_hand_interaction
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_hand_interaction
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_hand_tracking
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_hand_joints_motion_range
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_hand_tracking_mesh
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_MSFT_controller_model
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_KHR_visibility_mask
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_samsung_odyssey_controller
[OXRTK] 2023-12-27 21:22:39 -0800: Runtime supports extension: XR_EXT_hp_mixed_reality_controller
[OXRTK] 2023-12-27 21:22:39 -0800: Requesting extra extension: XR_EXT_eye_gaze_interaction
[OXRTK] 2023-12-27 21:22:39 -0800: Requesting extra extension: XR_EXT_hand_tracking
[OXRTK] 2023-12-27 21:22:39 -0800: Requesting extra extension: XR_KHR_visibility_mask
[OXRTK] 2023-12-27 21:22:39 -0800: Requesting extra extension: XR_KHR_win32_convert_performance_counter_time
[OXRTK] 2023-12-27 21:22:39 -0800: Application name: 'DCS World', Engine name: ''
[OXRTK] 2023-12-27 21:22:39 -0800: Using OpenXR runtime Windows Mixed Reality Runtime 113.2309.7002
[OXRTK] 2023-12-27 21:22:39 -0800: Using OpenXR system Windows Mixed Reality
[OXRTK] 2023-12-27 21:22:39 -0800: Ignoring XR_MSFT_hand_interaction for Windows Mixed Reality Runtime 113.2309.7002
[OXRTK] 2023-12-27 21:22:39 -0800: Upscaling from 2218x2168 to 3168x3096 (142%)
[OXRTK] 2023-12-27 21:22:39 -0800: Upscaling from 2218x2168 to 3168x3096 (142%)
[OXRTK] 2023-12-27 21:22:46 -0800: Using Direct3D 11 on adapter: NVIDIA GeForce RTX 2080 Ti
[OXRTK] 2023-12-27 21:22:46 -0800: Early initializeInterceptor() call
[OXRTK] 2023-12-27 21:22:47 -0800: MipMap biasing for upscaling is: -1.028
[OXRTK] 2023-12-27 21:22:47 -0800: Open menu with CTRL+F2
[OXRTK] 2023-12-27 21:22:47 -0800: Creating swapchain with dimensions=2220x2168, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21
[OXRTK] 2023-12-27 21:22:47 -0800: Creating swapchain with dimensions=2220x2168, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21
[OXRTK] 2023-12-27 21:23:37 -0800: Projection calibration: 0.05110, 0.00054 | -0.04649, -0.00278
[OXRTK] 2023-12-27 21:28:53 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-27 21:59:24 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-27 22:06:35 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-27 22:06:36 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-27 22:07:44 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-27 22:34:46 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-27 22:35:57 -0800: D3D11Device destroyed
[OXRTK] 2023-12-27 22:35:57 -0800: Session destroyed

Most current DxDiag file

DxDiag.txt

[The_Nephilim]

try turning off the classic apps second to last pic there..

[Ryu8200]

@BIGNEWY I've found this issue to only happen when using the Multithread version.

I just played on the same server (TTI Syria) with the same bird (AV-8B) on Singlethread for two hours without any issues. While I tired my best to trigger the black screen issue by changing views multiple times and switching to other players and the to the F10 map I couldn't replicate the bug with Singlethread.

DCS and the HP Reverb G2 ran flawlessly tonight while using Singlethread.

Attached to this message is the DCS log from tonight and maybe you and the team can use that to compare to the log I posted on 12/28/23 (which the black screen did occur) in this thread to hopefully resolve this bug when using Multithread and the HP Reverb G2.

This is the only game I play that has this issue when using the HP Reverb G2 so I'm guessing it's not hardware related but again a bug with Multithread.

Cheers and Happy New Year

dcs.log

Here's the log from the OpenXR toolkit tonight if that is useful:

[OXRTK] 2023-12-29 20:26:35 -0800: OpenXR Toolkit - GA-3 (v1.3.2)
[OXRTK] 2023-12-29 20:26:35 -0800: dllHome is "C:\Program Files\OpenXR-Toolkit"
[OXRTK] 2023-12-29 20:26:35 -0800: OpenXR-Toolkit layer is active
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_KHR_win32_convert_performance_counter_time
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_KHR_D3D11_enable
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_KHR_D3D12_enable
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_KHR_composition_layer_depth
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_KHR_composition_layer_color_scale_bias
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_unbounded_reference_space
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_spatial_anchor
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_perception_anchor_interop
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_win32_appcontainer_compatible
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_conformance_automation
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_composition_layer_reprojection
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_spatial_graph_bridge
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_spatial_anchor_persistence
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_palm_pose
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_active_action_set_priority
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_scene_understanding
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_scene_understanding_serialization
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_scene_marker
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_FB_display_refresh_rate
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_eye_gaze_interaction
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_hand_interaction
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_hand_interaction
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_hand_tracking
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_hand_joints_motion_range
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_hand_tracking_mesh
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_MSFT_controller_model
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_KHR_visibility_mask
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_samsung_odyssey_controller
[OXRTK] 2023-12-29 20:26:36 -0800: Runtime supports extension: XR_EXT_hp_mixed_reality_controller
[OXRTK] 2023-12-29 20:26:36 -0800: Requesting extra extension: XR_EXT_eye_gaze_interaction
[OXRTK] 2023-12-29 20:26:36 -0800: Requesting extra extension: XR_EXT_hand_tracking
[OXRTK] 2023-12-29 20:26:36 -0800: Requesting extra extension: XR_KHR_visibility_mask
[OXRTK] 2023-12-29 20:26:36 -0800: Requesting extra extension: XR_KHR_win32_convert_performance_counter_time
[OXRTK] 2023-12-29 20:26:36 -0800: Application name: 'DCS World', Engine name: ''
[OXRTK] 2023-12-29 20:26:36 -0800: Using OpenXR runtime Windows Mixed Reality Runtime 113.2309.7002
[OXRTK] 2023-12-29 20:26:36 -0800: Using OpenXR system Windows Mixed Reality
[OXRTK] 2023-12-29 20:26:36 -0800: Ignoring XR_MSFT_hand_interaction for Windows Mixed Reality Runtime 113.2309.7002
[OXRTK] 2023-12-29 20:26:36 -0800: Upscaling from 2218x2168 to 3168x3096 (142%)
[OXRTK] 2023-12-29 20:26:36 -0800: Upscaling from 2218x2168 to 3168x3096 (142%)
[OXRTK] 2023-12-29 20:26:43 -0800: Using Direct3D 11 on adapter: NVIDIA GeForce RTX 2080 Ti
[OXRTK] 2023-12-29 20:26:43 -0800: Early initializeInterceptor() call
[OXRTK] 2023-12-29 20:26:44 -0800: MipMap biasing for upscaling is: -1.028
[OXRTK] 2023-12-29 20:26:44 -0800: Open menu with CTRL+F2
[OXRTK] 2023-12-29 20:26:44 -0800: Creating swapchain with dimensions=2220x2168, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21
[OXRTK] 2023-12-29 20:26:44 -0800: Creating swapchain with dimensions=2220x2168, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21
[OXRTK] 2023-12-29 20:26:56 -0800: Projection calibration: 0.05105, 0.00054 | -0.04644, -0.00278
[OXRTK] 2023-12-29 20:32:09 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-29 20:32:10 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-29 21:18:29 -0800: xrEndFrame: XrResult failure [XR_ERROR_CALL_ORDER_INVALID]
    Origin: OpenXrApi::xrBeginFrame(m_vrSession, nullptr)
    Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\layer.cpp:3251
[OXRTK] 2023-12-29 21:19:24 -0800: D3D11Device destroyed
[OXRTK] 2023-12-29 21:19:24 -0800: Session destroyed

[Ryu8200]

Not sure if this is helpful at all but here are also the two Tacviews from the two flights with the DCS.log

 

Tacview-20240101-213338-DCS-Through_The_Inferno_SYRIA_v4.0.2.zip.acmi Tacview-20231227-213913-DCS-Through_The_Inferno_SYRIA_v4.0.2.zip.acmi

[BIGNEWY]

@Ryu8200 Please disable hotplug in your dcs controls and see if it helps

also I would recommend you use multithreading DCS version.  

 

On 8/3/2023 at 1:29 AM, The_Nephilim said:

If you want I can test the f14 in Sinai or syria and see if I have it happen? if you guys want me to check but I don't have the F15E.

 

 

EDIT: Well I just was flying the F14 in the Sinai and Syria switching from F10 and F2 and such. I did not have the G2 turn off at anytime.. here is my log incase it might help..

dcs.log 280.3 kB · 6 downloads

 

Change your pagefile to at least 32768 MB (initial size) it may help

[Ryu8200]

On 1/2/2024 at 1:19 AM, BIGNEWY said:

@Ryu8200 Please disable hotplug in your dcs controls and see if it helps

also I would recommend you use multithreading DCS version.  

 

Change your pagefile to at least 32768 MB (initial size) it may help

@BIGNEWY thanks for the input. I did disable the hotplug a few weeks ago based on other forum threads I had read trying to cure my issue. But the page file size increase to 32768 did the trick. I just finished an almost three hour flight with the same server (TTI Syria) and the same bird (AV-8B) with the increase in pagefile size. While at some points the hiccups from changing view did cause a noticeable lag spike and the fore mentions blue screen in the HP Reverb this time it would recovery and not black out the displays.

Since I have 64gb of ram do you think I should up the page size to match or keep at the 32768mb?

Either way I truly appreciate your input and want to say thank you again for finding a fix for my issue.

Cheers

Edited January 5, 2024 by Ryu8200