Cannot connect Unreal Insights with App Lab game with Quest 2
I am stuck trying to see Unreal Insights for my app which I am developing through the App Lab. I've tried the following 2 guides, but they are so poorly written, I don't know if I am missing some key steps in between. https://developer.oculus.com/blog/get-started-with-unreal-insights-on-the-oculus-quest/ https://inu-games.com/2020/01/06/unreal-insights-on-oculus-quest/ So Far, I've connected my Quest 2 through USB. And I have a Beta build installed through App Lab in my Quest 2. I can launch and play my app no issues. Unreal 4.27 Then I set up TCP connections, by opening a Command Prompt and doing this "adb reverse tcp:1980 tcp:1980" and I get a return value of 1980. Next I set up the UE4CommandLine.txt which is under This PC\Quest 2\Internal shared storage\UE4Game\MusicalRange\UE4CommandLine.txt which is a path in the Oculus Quest 2. I have tried various variations of these txt files. I know it is updated in the quest, because I can see the file size change which each version. The 3 versions are ID Redaced to random characters ../../../MusicalRange/MusicalRange.uproject -Messaging -SessionId=ABABABA565656 -SessionOwner="Eugenio" -SessionName="Quest_2 (CDCDCD898989)" -cpuprofilertrace -statnamedevents -tracehost=127.0.0.1 ../../../MusicalRange/MusicalRange.uproject -Messaging -SessionId=ABABABA565656-SessionOwner="Eugenio" -SessionName="Quest_2 (CDCDCD898989)" -cpuprofilertrace -trace=log,counters,cpu,frame,bookmark,file,loadtime,gpu,rhicommands,rendercommands,object -statnamedevents -tracehost=127.0.0.1 -tracefile=-tracefile=/sdcard/UE4Game/MostRecentTraceCapture.utrace ../../../MusicalRange/MusicalRange.uproject /Game/MusicalRangeReloaded/Maps/Map_MRR_ShootingRange -trace=log,counters,cpu,frame,bookmark,file,loadtime,gpu,rhicommands,rendercommands,object -statnamedevents -tracehost=127.0.0.1 -tracefile=-tracefile=/sdcard/UE4Game/MostRecentTraceCapture.utrace Next, I open up Unreal Insights, enable Auto Start Analysis, but no session ever shows up when I run app on my Quest 2. All guides seem to indicate that it's done. It should be working. What am I missing?Oculus always says the Android SDK version is wrong during validation
When uploading my app to Oculus, I receive this message: ERROR: Android Target SDK version is 29, but should be 32 or greater (targetSdkVersion in AndroidManifest.xml). But I am on SDK 32, in fact its the only SDK I have installed. my gradle.properties: my AndroidManifest.xml: In Unreal, I am targetting SDK 32, and during the build process, it specifically states I am using SDK 32: Is this a bug on the Oculus side? Side loading the app works fine. but can't upload
Textures Unexpectedly Downsized on Quest 2
Background: I have a material that uses an 8K x 4K texture like a cubemap using the LongLatToUV node in UE5.1. There is a user-controlled surveillance camera in a static environment, and rather than render a virtual camera into a render target to display on the surveillance monitor, I'm using this 8K environment map generated from the position of the camera mesh and then doing look-ups into it based upon the world orientation of the camera mesh. The user needs to be able to zoom in fairly far and retain clarity, hence the large texture size. This works very well in PCVR mode, but when packaging for the Quest 2, the texture gets downsized to 2K x 2K and is obviously quite blurry when zoomed in, especially horizontally. I created a new material that uses two 2K x 2K textures (the same 8K x 4K, downsized to 4K x 2K and then split in half) to effectively create a 4K x 2K texture on the headset (see image below). The worked perfectly. I was then confident I could use the same tiled cubemap technique to effectively create an 8K x 4K texture on the headset. The end result looked exactly the same in PCVR as the original 8K texture. On the headset, however, it looked exactly like the previous attempt, 4K x 2K tiled, making me think my eight 2K tiles got downsized to eight 1K tiles maybe. Does anyone know why this might be happening? I'm assuming there is some kind of per-material limitation that I am running up against. And thank you for taking the time to read all this! (Note: the material has an additional texture look-up to create a HUD effect, so Option 1 has 2 look-ups, Option 2 has 3 look-ups, and Option 3 has 9 total look-ups.)
