Fix: SOG proper removing of texture assets from asset cache #8012
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When a SOG asset is destroyed, GSplatSogsData.destroy() calls .destroy() directly on the texture resources. This fails to remove the parent Asset from the AssetRegistry cache.
Fixes #
Modify GSplatSogsData.destroy() to call asset.unload() on the texture Asset objects instead of destroying the resources directly.