Jump to content

Ryu8200

Members
  • Posts

    41
  • Joined

  • Last visited

Posts posted by Ryu8200

  1. 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

  2. @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

  3. Headset Display 1.jpg

    Headset Display 2.jpg

    Startup and desktop.jpg

    Audio and Speech.jpg

    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

  4. 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?

  5. Hello can we please add the adjustable trim tab setting for the FW-190s like we current have in the special options for the BF-109?

    Thank you and Happy Holidays

  6. 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.

  7. 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

    Desktop Screenshot 2023.07.11 - 20.12.34.58.png

    Desktop Screenshot 2023.07.11 - 20.12.44.25.png

    dcs.log DxDiag.txt

  8. I’m guilty of using auto start when I fly. But with the A10C and A10C II I’ve noticed that when I’m playing on the TTI servers I don’t get all the steer points (mainly the bases) until my first landing. Then it downloads all the steer points. Is there something I can do besides having to RTB to get all my steer points?

     

    Thanks in advance.

  9. The last few days I keep having issues with failed integrity checks. After deleting the fxo, metashader2 and mission editor files I can log in. But once in the server I get “timed out” and a new list of random files that “Failed Integrity”.

     

    The files that fail are never the same and I have an unmodded Steam DCS running the newest Open Beta.

     

    So how am I failing the integrity checks if DCS is unmodded and why are the files that “failed” completely random.

     

    I did a clean install to see if that would help but after that I still had the same issues.

     

    Please help

  10. The last few days I keep having issues with failed integrity checks. After deleting the fxo, metashader2 and mission editor files I can log in. But once in the server I get “timed out” and a new list of random files that “Failed Integrity”. The files are never the same and again I’ve never modded my DCS.

     

    So how am I failing the integrity checks and why are the files that “failed” completely random.

     

    Again I just did a clean install and after that I still had a random file not pass

     

    Please help

  11. Ryu8200, Same thing here. I used to get ping times in the 70ms range to the server I usually play on. After the latest update, 2.5.5.41371 in the 500ms range. Nothing has changed on my Internet end. A direct ICMP ping to my usual server, ~70ms. In-game multiplayer 3x to 5x higher. Has to be the update in some way...

     

    Thanks Bell,

     

    The 107th boys helped me with work around. If I connect by IP I can get in and my ping in the game is 20-30ms but the server list still shows as 350-400ms.

     

    Like you said must of been the update.

     

    Thanks again :thumbup:

  12. Tonight I'm currently unable to log into my normal servers I play on (Example: TTI SoCal) because my ping is showing 350-400+ in the server list. Normally I have a ping of 30-50ms with this server and was play just last night.

     

    Of course at first I thought it was my end so here's what I've tired so far:

     

    1: Speed tests on Google and Ookla: All reporting 10ms or less

    2: Verify game integrity in Steam = Passed 100%

    3: Delete FXO and Metashader2 and Mission Editor files "Saved Games" folder.

    4: Reset Router/Modem

    5: Refreshed server list multiple times

     

    Still unable to resolve so I tested other games and my ping is just fine.

     

    Any ideas how to fix this?

  13. Not sure where to post this but it happened while in the Viper.

     

    So I had just taken off on the Through the inferno “SoCal” server and went to the F10 map to look and where I was heading. While in the map my callsign changed from Ryu8200 to “New callsign” and I couldn’t F1 back into my Vioer or find myself on the map anymore.

     

    So I exited the server and went to the TacView and sure enough my name changes from my gamer ID of Ryu8200 to “New callsign” and without be controlling the plane it does a 180* turn by itself and then just seems to be on a constant bearing after that till I exit the sever.

     

    Any idea what just took place? Never had this happen to be before.

     

    After checking the TacView I verified my file for DCS and it came back 100% ok.

  14. Thank you for all your hard work. Too many complaints and not enough praise. Remember everyone if it was easy to build this level of simulator there’d be multiple on the market.

     

    Cheers :thumbup:

×
×
  • Create New...