If disabling IoStore, when we create a patch package and an asset is deleted comparing to the base package, it will be marked with bIsDeleteRecord in the patch pak.
[Image Removed]
Buf if enabling IoStore, it seems not to mark an asset which has been deleted when creating a patch package. So how does the engine know the asset has been deleted and not try to load it.
Hi,
Currently we don’t support marking assets as deleted in the I/O store container files. You need to patch any assets referencing deleted assets.
Currently I don’t think there’s a good way to prohibit loading a deleted assets without creating a new release.
Without marking, how to avoid loading a package which has been deleted in the patch, when we try to load it manually by using functions such as RequestAsyncLoad.