Studio World Effects: [XR] Scale can only be run before calling XR8.run()

I just cloned “World Effects” into studio but just initializing it on a mobile device results in an error:
[XR] Scale can only be run before calling XR8.run()

Permissions on the phone are set correctly (I’ve been running anther project and it’s android so no need to re-enable permissions) but while the camera icon appears on the top right of the OS for a moment, no camera appears and no world tracking occurs.

Considering this is all template code, this should just work out of the box… right?

Hiya Matthew,

I’ve had issues with this when I first tried out Niantic Studio ( I was hoping to use it as part of a game jam )

Just keep trying it - and if you come back in a few hours after a break, try it again - I couldn’t see a pattern to it not working.

I just updated a physics test I made earlier to use XR, so you have another link to test ( if one goes down, see if the other is down also - might help identify the issue )

image

Hope that helps a bit!
Mal

Indeed… checking back today, I do see the “The current configuration is still in development” and can confirm that the camera is still not available. It’s a bit disappointing considering they are having contests for using the new studio but the functionality is not built yet.

8th wall works great if you can fork out the cost for the original non-studio but this just shows the platform’s move to studio only for R&D users is a massive step backwards.

@Matthew_Potter @Mal_Duffin

:wave: Thank you both for this feedback and apologies you are experiencing issues with the AR Camera in Studio. We did release an update at the end of last week and this could be the cause of the downtime seen regarding the AR Camera. We will be working to improve XR capabilities and performance as a key team focus in the near term. Our team is working to apply fixes to the bugs noted below – thank you for bringing this to our attention.

@Matthew_Potter

For the Android Camera feed issue, our Studio team is here to support. In order to best troubleshoot the issue, we have a couple questions and want to confirm your set up.

  • What Android device type and version are you using?
  • To verify if permissions issues on Android could be a cause here, what happens if you select Launch on your device from the project page directly: https://www.8thwall.com/8thwall/world-effects - are you still seeing that the camera feed is not coming through?
  • Note: The [XR] Scale can only be run before calling XR8.run() error should not be causing the camera feed not to run. We have identified this issue as a bug and are currently working on a separate fix for this.

For the UI error: “The current configuration is still in development” we’ve identified this as an editor bug, and the project’s default Camera Configuration is correct/functional. This is separate from the Android camera feed issue. We are applying a fix to this UI issue this week.

We really appreciate the valuable feedback - it greatly helps us improve the user experience for Studio.

1 Like

I saw the same issue a few weeks ago - hopefully it gets resolved soon!

With the XR option on mobile, the 3D experience seems to start and then the camera feed comes through later - it might be good to have an option to not show any of the 3D content before the camera feed is live.

Sorry for the delay. We just wrapped the other project and launched so that was taking priority.
I’m using a Pixel 8.
I just replicated a new version of the “World Effects” project and launched it without modifying anything. It had the same issue initially but then after about 16 seconds, the page refreshed on the device and the camera feed came on and the project functioned as expected. Replacing the model with a different GLB works too.

Another Matthews feedback

I’m having the same issue. Initially with the new Absolute Scale template, but also seem to be having an issue with older AR Studio projects (Cactus tap to place). Just get a black screen

Running on a Samsung S21
I get the same issue when running it through staging or the test QR code redirect.

Hi, I think I’ve replicated the issue on our test device (Samsung S24). Is this what you’ve been seeing?

I was able to get to this screen by disabling Camera in Chrome’s settings. If you enable the Camera settings in Chrome it should work.

Hi there,

So yes, that is the general screen I get, however, my camera permissions are on. This makes sense because effects using the Cloud Editor work fine

I get these errors no matter what I remove from the scene

With was with using the Absolute Scale Studio template

Hi @Matthew_van_Niekerk, can you please confirm the browser you’re using? Has the webpage ever requested camera permissions, or has it always gone directly to the black screen? Are you able to share screenshots of the camera permission configuration from the browser settings and the system settings?

I will mention that Android remembers camera permissions granted to websites in your browser, meaning if you allow a site to use your camera once, it will generally be able to access it on future visits unless you manually change the permission settings for that site within your browser settings. So if at some point camera permissions were denied, you will see the black background instead of receiving the request for camera permissions and/or see the camera feed rendered.

Apologies for the extremely late reply on this. I completely missed this reply

On Android I am using Chrome and have accepted the camera and mic permissions. I don’t recall it requiring permissions when I was testing the experience since I test many 8th wall projects on the device and don’t always get the permissions request.


(sorry, not sure if this is the screenshot you were looking for)

I am still able to launch other 8th Wall projects on the device. For example, the Launch QR code provided for the " Studio: Door Portal" scans and runs fine on the device. However, as soon as I clone the project, without any changes, it get the same issue/error.
The camera feed is all black, but the door is static but still opens and reveals the interior

I have also just tested this again on my iPad, with the same results