Remote Addressable Content Updates Not Working

Unity Engine
,
1

I’m having the problem described here. Remote asset deliver works on device (Quest 2) but updating catalog leads to assets not being found. I’m on 2021.3.8 LTS. Using very basic/default loading logic based on documentation. Some screen grabs:

8711580--1177209--upload_2023-1-6_17-50-29.png
8711580--1177209--upload_2023-1-6_17-50-29.png928×735 61 KB

8711580--1177218--upload_2023-1-6_17-51-8.png
8711580--1177218--upload_2023-1-6_17-51-8.png928×783 57.1 KB

8711580--1177203--upload_2023-1-6_17-45-35.png
8711580--1177203--upload_2023-1-6_17-45-35.png922×845 64 KB

8711580--1177209--upload_2023-1-6_17-50-29.png
8711580--1177209--upload_2023-1-6_17-50-29.png928×735 61 KB

2

Trying to figure out where I’m going wrong, so if anyone can answer these questions, that would be very helpful:

  • Can I create new asset groups after creating the initial full build of the app or am I required to work within the existing groups?
  • Can I create completely new assets and add them to asset groups after the initial full build or am I limited to update existing assets?

Any help is greatly appreciated!

3

Hi there @ronjart , the answer to both of your questions is yes - going through the steps of the content update workflow will allow you to make both new groups and add brand new assets to your project. As long as you follow the steps in the docs and deploy your new asset bundles along with the new catalog + new catalog hash to your CDN, it should work.

That said, its important to note that if any code changes are made between your two builds a completely new build will be required, as the content update workflow is not able to pass along code changes due to it only updating the catalog and asset bundles. If new assets are not being detected, its possible that the catalog is not being properly updated or that the bundles are not being uploaded to the CDN correctly. Additionally, make sure that before/after updating content you unload all of the assets that may have been updated to get new versions of any assets to show in your project. While all future loads following a content update will use the new versions of assets, any existing old versions will remain loaded until unloaded - they will not be automatically overwritten.

I hope this helps!

4

Thank you for the reply and the valuable information.

To clarify, even if I create a new scene with code that is completely separate from the original build (like a self contained experience) I won’t be able to push that update (ie. I need to make a new build)?