Cyclic VRC 1 after update to new MacOS and MQDH
I started seeing weird behavior recently with Performance Analyzer in MQDH. So last week everything was ok, but what happened to me: 1. I updated MacOS to Sequoia - I use Macbook M1 2. I updated my Quest 2 to latest version 3. I updated MQDH to 5.0 version (other versions stopped working) I've noticed that no matter what game or app I test, I see the same results in the Performance Analyzer. Below you can see screenshot for "First Steps" application (the one from Meta), You can notice this cyclic VRC1 flag showing in pretty regular intervals. I already did factory reset on Quest headset, used different USB-C cables, but not luck. What is weird, that on the headset itself I don't see any problems (or I'm not able to notice it for some reason), it's only this Performance Analyzer showing flags. Does anyone have similar experience and solution perhaps? I created bug in MQDH, but I don't know where it goes as I cannot find it.
macOS MQDH 4.4.1 ships with x86_64 adb
Title says it all. Current (as of this writing) revision of MQDH for macOS ships with adb built only for x86 when it should probably be a universal build like the rest of the app. Evidence from the CLI: my-fancy-prompt$ pwd /Applications/Meta Quest Developer Hub.app/Contents/Resources/bin my-fancy-prompt$ ls Casting.app/ NOTICE.txt aapt2 InputForwardingService.apk OculusDeveloperHubService adb my-fancy-prompt$ file adb adb: Mach-O 64-bit executable x86_64 This drove me bonkers for a goot bit trying to get my Quest 3 connected to the developer hub. My Ventura-based Mac does not have Rosetta installed on it as it's actually a clean install and I avoid Rosetta unless it's absolutely necessary. When attempting to connect my Q3 to MQDH it went through the whole process and ultimatley did nothing with zero feedback, error or otherwise. There was no indication that adb failed to launch because of the "Bad CPU type" of the binary. I grabbed the platform-tools from android.com and those are indeed a universal build as they should be. I pointed MQDH at that adb and it's good for now. Please consider packaging a universal arch adb with a near-future release of MQDH for macos. Cheers!
Is it possible to build a Quest app with macOS?
With the Vision Pro out I know Meta does need developers and I do see Quest 3 as a better value for money. I am curious to know if it is possible to develop Quest 3 apps on the Mac or is WebXR the only path? Tons of developers that are non-game devs are on Macs so I am curious to know if it is possible or if Meta will issue an update in the future on this!
Oculus VR Plugin Missing in Unreal Editor Project Settings Menu - Intended Quest Development
I am trying to make an app for Oculus Quest using Unreal Engine and the Oculus VR plugin while developing on macOS. I wish to access the settings of the Oculus VR plugin in the Unreal Editor in the "Project Settings" panel in the "Plugins" section, but the OculusVR item does not appear (see first screenshot below) even though the Oculus VR plugin was enabled in the "Edit->Plugins" menu (see second screenshot below). The expected appearance of the OculusVR plugin settings are described in the "Configure the Oculus Plugin for Unreal Engine" guide. I have followed all preliminary steps listed in Oculus' Quick-start guide for Unreal Engine development on Quest. I have experienced this behavior with both the Unreal Engine editor binary download from the Epic Games Launcher, as well as from the editor I built from source using the Oculus-VR Unreal Engine repository. The versions I used are: Epic Games Unreal Editor Binary: 4.25 Oculus Source Code for Unreal Editor: 18.0 based on UE 4.25 I am developing on MacOS Mojave (10.14.6). This same issue has been pointed out in other posts and forums. The solution mentioned in a couple of the posts is to download the Oculus Rift software, but this software only supports PC and not MacOS, so I am unable to use this. Surprisingly, this solution worked for PC users who were not attempting to develop for the Rift, but instead for the Quest. Another partial solution mentioned, which only allows you to modify the FFR setting for the plugin, is explained at the bottom of an Oculus guide on FFR in Unreal Engine. Is there any known full solution to this issue, specifically when developing on MacOS? I assume it would be simple enough to see the plugin settings for a plugin which has been enabled in the Unreal Engine editor. Thank you for any help on this topic. I originally had many helfpful links inserted into this post, but the Oculus forum has prevented me from posting links because I am "too new". This greatly reduces the quality of this post and is very sad. I have created a duplicate post on the Unreal Engine forum, so if you are looking for the links, please visit there!
