Jump to content

recent meta link software update (NON PTC) and DCS is constantly crashing when startup


Recommended Posts

Posted (edited)

meta automatically updated meta link software to version

i am not subscribed to Public Test Channel

Meta Quest Link App Version 68.0.0.433.361 (68.0.0.433.361)

disabling OpenXR toolkit does not help, also uninstalled openXR toolkit and rebooted PC, and still not success.

I can not start up DCS in VR (desktop mode works ok)

DCS is kaput for me with meta quest link

dcs.log

Edited by hannibal

find me on steam! username: Hannibal_A101A

http://steamcommunity.com/profiles/76561197969447179

Posted

If you are using OpenXR Toolkit, Quad View Foveated Rendering, HTCC, or any third-party OpenXR layer tool, disable them. They're not compatible with Meta Link v68 anymore due to Meta's changes. If you want to keep using those tools, switch to the Virtual Desktop app, which uses its own VDxR link instead of Meta Link.

  • Thanks 1
Posted (edited)
On 7/30/2024 at 9:55 AM, slughead said:

 HTCC, or any third-party OpenXR layer tool, disable them. They're not compatible with Meta Link v68 anymore due to Meta's changes

Only API layers that depend on querying what extensions are available are broken. HTCC specifically has a workaround in the latest version and works fine.

Some are broken, some are not. If things are broken, turn them all off, then *try turning them all on one at a time* - they're not all vulnerable to the bug, some are.

Edited by actually_fred

My projects:

OpenKneeboard - VR and non-VR kneeboard with optional support for drawing tablets; get help
HTCC - Quest hand tracking for DCS; get help

If you need help with these projects, please use their 'get help' links above; I'm not able to track support requests on these forums.

 

Posted
3 minutes ago, actually_fred said:

Only API layers that depend on querying what extensions are available are broken. HTCC specifically has a workaround in the latest version and works fine.

Some are broken, some are not. If things are broken, turn them all off, then *try turning them all on one at a time* - they're not all vulnerable to the bug, some are.

 

Yeah I was generalising somewhat. 👍

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...