Unreal - Use Take Recorder with Live Link for Hand Tracking as Motion Capture?
Hi everyone, I'm trying to record an animation in Unreal using the Hand Tracking of the Quest 3 and 2 as a motion capture and once recorded I need to export the animation for future use. When I record with the Take Recorder, the only things that move are the rotation and location of the Motion Controller Components. I searched for a Live Link connection but found only the tracking for body and face with Quest 2. Is there a function for recording the Skeletal Mesh movements of the hand with the Take Recorder? (I found this Post similar to my question but didn't know how to record the bone transforms.) Is there a Live Link connection for the Hand Tracking? I'm using the Meta XR plug-in and already set it for Hand Tracking only.Simultaneous hands and controllers doesn't work anymore
Hi, around march/april 2024 we were able to implement the support of both Hands & Controllers simultaneously, using the Meta OpenXR API. Our app is written in C++ and runs in PCVR (Quest Meta Link PC). We are using a Meta Quest Pro headset (3, actually, one for us, two for the client). Back then Meta VR software was either v62 or v63. I recorded this video as a proof that it did work : https://www.youtube.com/watch?v=NHGjfHEtBgs The use case is that we need the user to manipulate a real luggage and see it in the VR. It worked indeed for a couple of months, at our client's facility, with more than half a hundred different users. Our code relies on xrResumeSimultaneousHandsAndControllersTrackingMETA / SXRE_META_DetachedControllers / ... based on the OpenXR API provided by Meta (I can profide more code if needed). Our problem : The project is now reactivated and I updated both the PC and the headset to v69. And it turns out, the simultaneous support of both hands and controllers doesn't work anymore. My questions : - has anything changed recently in the way we should except this to work ? - is there a way to test this feature, outside our of own application, to make sure the headset behaves as expected ? I've seen quite a lot of similar posts either on this very forum or on Reddit, and the lack of information makes me rather concerned. Is there any plan at Meta to allow such use cases where a real life object can be tracked in realtime ? Or is it something you simply don't care about (the compositing provided a standalone tracker, so I would expect Meta to at least consider the question) ? Please be honest if this feature was disabled and there is no immediate plan to reinstate it, so we can move on to another solution (possibly another headset vendor).
I use Autodesk's VRED, but there is an error in Hand Tracking through OpenXR.
I'm using Autodesk's VRED program. The VRED program wants to use Hand Tracking via OpenXR (OpenXR is leveraged because the VRED program does not directly support Quest products) If you try to activate the VR environment through OpenXR using Quest2 and Quest Pro equipment, an error occurs and the program shuts down. Conditions are normally using a cable that supports USB 3.0 or later, enabling developer mode in the Oculus smartphone app, and enabling OpenXR Runtime in the Oculus PC program. VRED is currently using the most recent version of Professional 2024 (16.0.11988). I had the same issue when using the 2023 (April) version. The Oculus PC app version is also using the latest version, 54.0.110.284. Switching Display Mode to OpenXR HMD with Quest Link turned on on on the Quest device in the View option of VRED often results in an error and the VRED program is forced to shut down (sometimes when multiple attempts are made) As for the error report, Date/Time: 2023-06-29 06:50:09 +09:00 Application: VREDPro.exe Error: Access violation - code c0000005 (first/second chance not available) Crashed Module Name: XR_EXT_hand_tracking.dll Exception Address: 0x00007ff859bb6b5f Exception Code: c0000005 Exception Flags: 0 Exception Parameters: 0, 3b4c0000003c You can check these error details. If you check the Callstack Text file, OS-Version: 6.2.9200 () 0x100-0x1 00007FF859BB6B5F (XR_EXT_hand_tracking): (filename not available): OVRInterfaceShutdown 00007FF84C349873 (vrDisplayHandler): (filename not available): vrOpenXRHandTracker::locateHandJoints 00007FF84C3490C5 (vrDisplayHandler): (filename not available): vrOpenXRHandTracker::update 00007FF84C3324D0 (vrDisplayHandler): (filename not available): vrOpenXRHandler::update 00007FF841C16048 (vrKernel): (filename not available): vrOSGWidget::processVREvents 00007FF841935223 (vrKernel): (filename not available): vrController::timerLoop 00007FF85FD9321B (Qt6Core): (filename not available): QObject::qt_static_metacall 00007FF85FD95364 (Qt6Core): (filename not available): QMetaObject::activate 00007FF85FDAAB0C (Qt6Core): (filename not available): QTimer::timerEvent 00007FF85FD9B8E7 (Qt6Core): (filename not available): QObject::event 00007FF85CF7134E (Qt6Widgets): (filename not available): QApplicationPrivate::notify_helper 00007FF85CF7031B (Qt6Widgets): (filename not available): QApplication::notify 00007FF7F44EB582 (VREDPro): (filename not available): vrApplication::notify 00007FF85FD59805 (Qt6Core): (filename not available): QCoreApplication::notifyInternal2 00007FF85FEAB278 (Qt6Core): (filename not available): QEventDispatcherWin32::event 00007FF85CF7134E (Qt6Widgets): (filename not available): QApplicationPrivate::notify_helper 00007FF85CF7031B (Qt6Widgets): (filename not available): QApplication::notify 00007FF7F44EB582 (VREDPro): (filename not available): vrApplication::notify 00007FF85FD59805 (Qt6Core): (filename not available): QCoreApplication::notifyInternal2 00007FF85FD5BB4D (Qt6Core): (filename not available): QCoreApplicationPrivate::sendPostedEvents 00007FF85C81DC9F (Qt6Gui): (filename not available): QWindowsGuiEventDispatcher::sendPostedEvents 00007FF85FEAB622 (Qt6Core): (filename not available): QEventDispatcherWin32::processEvents 00007FF85C81DC79 (Qt6Gui): (filename not available): QWindowsGuiEventDispatcher::processEvents 00007FF85FD5E34F (Qt6Core): (filename not available): QEventLoop::exec 00007FF85FD578AC (Qt6Core): (filename not available): QCoreApplication::exec 00007FF84193A9F7 (vrKernel): (filename not available): vrController::loop 00007FF7F44E040E (VREDPro): (filename not available): safeRun 00007FF7F44DF7B1 (VREDPro): (filename not available): vrCrashHandler::run 00007FF7F44CCC0A (VREDPro): (filename not available): vrMain::run 00007FF7F44C176B (VREDPro): (filename not available): vrmain 00007FF7F44C11D4 (VREDPro): (filename not available): wWinMain 00007FF7F44F639A (VREDPro): (filename not available): __scrt_common_main_seh 00007FF87F797614 (KERNEL32): (filename not available): BaseThreadInitThunk 00007FF87FA426F1 (ntdll): (filename not available): RtlUserThreadStart You can check this out. VRED's OpenVR HMD mode operates normally, but VRED's OpenVR HMD mode operates over Steam VR, so Hand Tracking is not enabled. Alternatively, enabling OpenXR Runtime on SteamVR and operating OpenXR HMD mode will still function normally, but Hand Tracking will not work here either. An error occurs only when utilizing Oulus's OpenXR Runtime. I'm guessing there's a problem when I try to use Hand Tracking. This is because even if you utilize Oulus' OpenXR Runtime, there is no error when you turn off Hand Tracking in VRED's settings and run OpenXR. Does anyone know a solution?
