amazon-web-servicesunity-game-engineamazon-s3addressables

Problem with Addressable 1.8.5 not loading remote scene from AWS S3

STACK:

CONFIGURATION:

I want to load a scene entirely from an AWS S3 bucket. I have followed two tutorials:

I have a simple scene with a couple of buttons to press. In this case, the user presses "Load Remote Scene"

enter image description here

that will call the function to load the addressable (which uses a string to define the address). The function is trying to load the Test_scene_2.unity scene where there is a spinning cube.

enter image description here

A new "remote" profile has been created and set as active. Also, the remote AWS path has been configured:

enter image description here

As you can see I have an Addressable group that contains a reference to the scene:

enter image description here

And both global and group settings have been configured for generating a remote catalog:

enter image description here enter image description here

As a final step, I have built the addressable group generating the .hash, .bin and .bundle files in the AssetData folder

PROBLEM: I know that the next step is to load those files to the S3 buckets, but as reported in the MeowKim tutorial:

"Running at this time would cause errors because Unity tries to get remote groups from the server."

Unfortunately, if I run the game in the editor and push the "Load remote Scene" button the scene gets loaded normally, which shouldn't happen because the S3 bucket is empty. I should get an error, which should disappear as soon as I upload the files. This means that my addressable assets are still pointing to the local files.

The strange thing is that if I build a standalone app the remote loading works, meaning it fails if the S3 bucket is empty but it loads the scene as soon as I load the addressable data.

In Summary:

  1. Play in Editor: scene loads correctly with or without addressable data in the S3 bucket
  2. Build and Run standalone app: everything works well (only if addressable data in S3 bucket).

What am I missing?

Solution

  • I had that problem, I modified the scene's addressable keys to simple names without special characters and in one word, it worked for me I hope this help someone.