Fix VoxelGI saving VoxelGIData as a built-in file, despite being prompted to save it to an external file #78772
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.
This fixes #50029.
It seems like the resource saver will change the VoxelGIData resource path to the external file, save the resource and the revert it to what it was previously (an empty string), essentially creating two resources, one built-in to the scene (which has the actual data) and the external file. I do not know why the resource saver works this way, but the
ScriptCreateDialog
does the same thing:so I copied that.