Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

My scene wont load in Chrome or Edge on desktop.

  • 2 replies
  • 1 has this problem
  • 117 views
  • Last reply by OhMyGorm

more options

Hi there

So my problem is that I have made a scene in spoke (it's a bit large and has a lot of models in it), that wont load in Chrome or Edge on desktop, but works in Firefox on desktop and chrome on android.

When I say it wont load, means that it keeps spinning and never finishes, while it has no problem loading and entering rooms on Firefox or mobile browsers.

I am able to start a room with a different scene, and change to other scenes on Chrome and Edge, but when I switch to my own scene the background stays black, while on Firefox it successfully changes the scene.

I am also able to load other scenes I have created, so it is just my one scene that doesn't work.

I hope someone here has a tip to what might cause this. So I can prevent this issue from future scenes :)

Chosen solution

Hi there

Sorry I don't feel comfortable sharing the space. But since the last time I posted I have checked the console on Edge when trying to load the scene, and it resulted in the following error:

"Uncaught (in promise) RangeError: Maximum call stack size exceeded" as a reference to "three-pathfinding.module.js:1"

I've been told that it is a bug which is being fixed soon.

Thanks for the reply though!

Read this answer in context 👍 0

All Replies (2)

more options

Hi

Are you abel to share a link to the space you have made so that we can have a look and try to find a solution for you?

more options

Chosen Solution

Hi there

Sorry I don't feel comfortable sharing the space. But since the last time I posted I have checked the console on Edge when trying to load the scene, and it resulted in the following error:

"Uncaught (in promise) RangeError: Maximum call stack size exceeded" as a reference to "three-pathfinding.module.js:1"

I've been told that it is a bug which is being fixed soon.

Thanks for the reply though!