Replies: 1 comment
-
By the way a rename for EditorScenePostImportPlugin may be desirable. EditorSceneAdvancedImportPlugin perhaps? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I believe it may be useful to change the signatures of EditorScenePostImportPlugin's
_pre_process()
and_post_process()
to match that of EditorScenePostImport's_post_import()
. That way EditorScenePostImportPlugin may too radically transform the imported scene and EditorScenePostImport may be removed.I'm making a 3D game with modular and customizable characters and the way I mostly use EditorSceneImport currently is to look for a particular node, for example a Skeleton or an AnimationPlayer, and make it the root and only node of the imported scene. I would like to use EditorSceneImportPlugin to replace my workflow of setting an EditorScenePostImport script for every asset I import.
Using an alternative custom importer for assets that already have one is very cumbersome with the forced editor restart required and is redundant as well.
Beta Was this translation helpful? Give feedback.
All reactions