Quest 3 Specific Build for graphical update
We've been having some issues with trying to make a Quest 3 graphical update filed and wondering what the best method of doing this would be. We want to use device profiles to control both the t...
Forum Discussion
Hello, have you found a solution for this problem?
I Found Solution! (ﾉ◕ヮ◕)ﾉ*:･ﾟ✧
To fix the problem, you need to add a MatchProfile in your BaseDeviceProfiles.ini located in (Your Engine Loc)\Engine\Config\.
- Open BaseDeviceProfiles.ini.
- Find the existing MatchProfile for Meta_Quest_3.
- After the existing entry, paste the following:
+MatchProfile=(Profile="Meta_Quest_3",Match=((SourceType=SRC_DeviceMake,CompareType=CMP_Equal,MatchString="Oculus"), (SourceType=SRC_GPUFamily,CompareType=CMP_Equal,MatchString="Adreno (TM) 740")))
The Quest 3 has a different GPUFamily, so we create a rule to match the Quest 3 profile accurately.
Note: Unfortunately, differentiating between Quest 2 and Quest Pro is tricky since they share the same GPU. I tried adding a rule based on RAM, but no luck so far.
I have been unable to get logs off my unreal project on device for a while, perhaps some issues I've been having were that I was having the wrong profile being set on quest 3. I'm going to test this now to see if it helps my distance field issues.
