Improved Asserts when Deleting and Regenerating Assets #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Unreal Importer 1.3.0 Release (Fixed)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In version
1.3.0we fix a number of issues relating to source control plugins, especially the case where the plugin accidentally marks all the generated assets fordeletewhen they should be marked asedit.Just in case these somehow reoccur despite the fix, I've added additional asserts which ensure that the old generated database is actually deleted before creating the new one and gently fail the import. Previously, this issue would crash the Unreal editor if any of your Articy objects changed templates between imports.