EditorExportPlugin docs: Workaround for customized texture behavior
#94092
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
AThousandShips
changed the title
EditorExportPlugin docs: Workaround for #94045 (CompressedTexture2D behavior)EditorExportPlugin docs: Workaround for CompressedTexture2D behavior
allenwp
force-pushed
the
editor-export-plugin-docs-94045
branch
from
ea67f93 to
d741b2e
Compare
KoBeWi
reviewed
Aug 8, 2024
…behaviour of customizing texture resources. The list of types that should not be both customized and skipped was created through trial-and-error with the following import types: - AnimationLibrary - BitMap - Translation - CompressedCubemap - CompressedCubemapArray - FontFile - FontFile - FontFile - RDShaderFile - Image - AudioStreamMP3 - AudioStreamWAV - ArrayMesh - PackedScene - CompressedTexture2D - CompressedTexture2DArray - CompressedTexture3D - AtlasTexture - AudioStreamOggVorbis The reason `skip()` should not be called is because the original resource will now point to the `.ctex` (or equivalent) file of the resource that replaced it. In this scenario, the `.ctex` file that was initially referenced by the original resource will no longer be included in the project. Co-authored-by: Tomek <kobewi4e@gmail.com>
allenwp
force-pushed
the
editor-export-plugin-docs-94045
branch
from
e1dd85e to
c6e994b
Compare
|
I've pushed an update to this PR that includes more types that should not be both customized and skipped. It is now ready for review and merging. |
allenwp
changed the title
EditorExportPlugin docs: Workaround for CompressedTexture2D behaviorEditorExportPlugin docs: Workaround for customized texture behavior
KoBeWi
approved these changes
Oct 31, 2024
|
Thanks! |
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.
EditorExportPlugin docs: Workaround for #94045. Describes behaviour of customizing texture resources.
The list of types that should not be both customized and skipped was created through trial-and-error with the following import types:
The reason
skip()should not be called is because the original resource will now point to the.ctex(or equivalent) file of the resource that replaced it. In this scenario, the.ctexfile that was initially referenced by the original resource will no longer be included in the project.From a usability perspective, there should be no difference between the way that different resources are handled, so I believe this is not a complete solution to the original issue. That said, my hope is that this documentation addition will at least bring
EditorExportPluginto a more usable state.