That baseUrl is used correctly to load all the assets in the scene, but it fails to load the custom emote via triggerSceneEmote, so probably the issue is related to that particular function.
SDK:
[ ] SDK6
[x] SDK7
Steps to reproduce:
Deploy a world that makes use or triggerSceneEmote and test it in runtime.
Expected behaviour:
It should load the custom emote from the baseUrl provided in the scene urn.
Current behaviour:
It tries to load the custom emote from the content url defined in the about, instead of the baseUrl defined in the scene urn.
Issue Description:
The
triggerSceneEmote
function does not work when using a custom baseUrl in the entity's urn.Here's an example scene: link
In that scene there's a button that when click it triggers a
triggerSceneEmote
action. You will notice that a request is made when tat happens to:And it should be done to:
The hash is correct, but the baseUrl is wrong. The base URL is configured in the
/about
endpoint of the Builder's custom realm: linkAs you can see there, the baseUrl is configured in the
scenesUrn
array with the following value:That baseUrl is used correctly to load all the assets in the scene, but it fails to load the custom emote via
triggerSceneEmote
, so probably the issue is related to that particular function.SDK:
Steps to reproduce:
triggerSceneEmote
and test it in runtime.Expected behaviour:
It should load the custom emote from the baseUrl provided in the scene urn.
Current behaviour:
It tries to load the custom emote from the
content
url defined in the about, instead of the baseUrl defined in the scene urn.