Forum Widgets
Recent Discussions
Large map building&texture help
Hello, I'm new in Horizon Desktop App, started creating few things. I have 2 questions that needs your helps. Is it better to parent+stack everything into a single Asset after I finish building some objects? For performance issues, because my world itemwise only %3 but almost %70 in vertex limits. How can I reduce this vertex usage? I cannot adjust textures. I'm creating one, inserting into my floor, but all the stones on the floor are so big that doesn't look realistic. I want to pattern to repeat itself in a smaller scale. Thank you for your helps
Meta Quest Link's virtual camera causes third-party applications to crash.[windows]
Hello, we've encountered a serious compatibility issue and would appreciate your assistance in resolving it. Problem Description: Meta Quest Link's virtual camera causes third-party applications that use DirectShow to enumerate cameras to crash. Reproduction Steps: 1. Install Meta Quest Link 2. Launch an application that uses DirectShow to enumerate cameras (such as OBS Studio) 3. Delete the camera source in the application 4. The application crashes Affected Scope: 1. Crash Probability: Nearly 100% 2. Affected Applications: All third-party applications that use DirectShow to enumerate cameras 3. A large number of our users use Meta Quest Link and have all experienced this issue. 4. Well-known applications like OBS Studio are also affected. I've seen users report this issue in the OBS repository. 5. This issue severely impacts user experience and product stability. Technical Analysis: The crash occurs when DirectShow enumerates the Meta Quest virtual camera. The IBaseFilter object (the fourth parameter) is obtained through the IMoniker::BindToObject() interface, and the crash occurs when releasing this object. The Meta Quest Link virtual camera may have a flaw in its internal memory management of the IBaseFilter object. We hope the Meta team can fix this issue.
Please have native support for locomotion devices
It would be great to have native support for integrating VR locomotion devices (Freeaim VR Shoes, Kat Walk, Virtuix Omni, Natural Locomotion, etc.) similar to how it works with SteamVR. In SteamVR, we can implement our own driver that will translate movement from the device to joystick commands. SteamVR loads the driver and then forwards the joystick commands. We can also retrieve useful information from the headset via the driver and send it to the device, such as HMD position and orientation. Currently, to support a locomotion device on the Meta Quest, game developers have to integrate support. This isn't scalable and is a lot more work than if the locomotion manufacturer could just implement a driver/plugin/background process that works for all games that have locomotion.
SpaceWarp works in empty project but not main one (Unity 6000.1.6f1, Quest 3)
Hey all, I’m running into something weird with Application SpaceWarp on Quest 3. I set up a clean empty project in Unity 6000.1.6f1 with OpenXR (Meta XR features) and Vulkan only. SpaceWarp works fine there and the performance overlay shows ASW kicking in as expected. But in my main project (same Unity version, same OpenXR/Vulkan settings) , SpaceWarp never activates. Both projects have: Meta XR Space Warp enabled Vulkan as the only graphics API Same Project Settings → OpenXR (Application SpaceWarp checked) Same Player/Quality settings I already checked URP settings, even copied the same and Materials show the XR Motion Vectors Pass still no luck. Any tips for narrowing down what breaks it? Maybe some other package that I have on my main project? Thanks!!!Quest Runtime Optimizer cannot analyze frame capture on Quest Pro v79.1029
I'm getting errors analyzing captures, and after a day spent debugging, it seems to have started with the latest headset update. An untouched project that previously had no problems has the error now after the headset update. There seems to be an error caused by format incompatibility with the trace_processor_shell version (v46.0) and the Core SDK 70+ which causes the python script to crash? (Don't ask me the details, I'm just a tech artist trying to get frames benchmarks here). I'm running the following: Unity 6.1 and 6.2 on Windows 11 Quest Pro (updated to v79.1029 on Aug 25, the date the error started appearing) Here is the error text: MetricAPI: 68AE8CCB.json execode: 0 single positional indexer is out-of-bounds Traceback (most recent call last): File "C:\open\fbsource\arvr\projects\integrations\Unity\RuntimeOptimizer\Editor\PerformanceInsight\MetricAPI.py", line 1118, in main File "pandas\core\indexing.py", line 1191, in __getitem__ File "pandas\core\indexing.py", line 1752, in _getitem_axis File "pandas\core\indexing.py", line 1685, in _validate_integer IndexError: single positional indexer is out-of-bounds UnityEngine.Debug:LogError (object) Meta.XR.RuntimeOptimizer.Core.Util:DebugLogError (object) (at ./Library/PackageCache/com.meta.xr.runtimeoptimizer@e44a64bf5ef6/Core/LogUtils.cs:19) Meta.XR.RuntimeOptimizer.Editor.PerformanceInsight.MetricAPI:GetCaptureMetric (string,string) (at ./Library/PackageCache/com.meta.xr.runtimeoptimizer@e44a64bf5ef6/Editor/PerformanceInsight/MetricAPI.cs:68) Meta.XR.RuntimeOptimizer.Editor.PerformanceInsight.CaptureTool:ProcessCaptureToJsonObjFunc (object) (at ./Library/PackageCache/com.meta.xr.runtimeoptimizer@e44a64bf5ef6/Editor/PerformanceInsight/CaptureTool.cs:787) System.Threading._ThreadPoolWaitCallback:PerformWaitCallback ()
New Loading/Splash Screen
Hello, the system splash screen behavior was recently updated. In the past the image supplied by the App would be shown centered on black with the three loading dots below and the size of the logo was pixel perfect so changing the resolution would change the display size. As described here: https://developers.meta.com/ Now after the recent update, the system shows this new fancy animated light rays thing and the image is scaled to fill the entire screen width, i think.. It's very large now and as a result it's very blurry. I was wondering if there is any updated documentation with newer recommendations on what resolution to use now or how the behaviour has changed. I want to avoid submission problems by just guessing, thanks everyoneFIX YOUR LINK SOFTWARE
PCVR with Link is the absolute worst software I have ever used almost daily I will be in iRacing and the Link glitches out, the entire community knows it's trash and always suggest using Virtual Desktop. I Have recently purchased a Bigscreen Beyond 2 headset and will never use Quest again constant software updates and glitches. learn how to code software that doesn't suck.FIX THE ISSUE THAT RESULTS IN CONTROLLERS FAILING ON REGULAR BASIS
Why is meta unable to address the serious problem with controllers failing or bricking, or purple lights of death? Replaced mine 3x in month and keep getting refurbished junk. what is meta doing about this? It's costing me time, money, and a ton of frustration with terrible support & constant down time. I paid $500 for this thing but have maybe 3 full months of play time over 10 months. How is this OK?
