Datasmith Feature Requests

[kenpimentel]

@cwm83

Testing 4.20 with Rhino, and definitely enjoying the improvements! The reimport process has been noticeably improved, but still a few requests:
Edit: After testing with Blocks some more, the recent changes have unfortunately made them nearly worthless, at least for my workflow. The pivot point of the imported block actor is at zero, forcing the elements within the block to have non-zero relative transforms, which is pretty much the opposite of how blocks are meant to behave in my mind. The added actor within the hierarchy breaks the layer=actor pattern that helps navigate through the scene, so they hurt not just block workflow, but also breaks layer-based workflows. And most importantly, the usefulness of a block is that if I change one, that change is seen in all of them. When they came in a single static mesh, I could at least easily replace that one mesh with my own custom mesh. Now I have to write a custom editor script that searches by name, digs down the hierarchy to the components to get the appropriate world pivot, spawns my custom actor at that spot, and deletes the imported actors. I think importing them as blueprints by default would come closest to mimicking how they work in Rhino. If anyone finds them more useful this way, I’d enjoy hearing about it. Maybe I am thinking about them all wrong!

Can you log this as a bug?
Report Unreal Studio bugs here: https://unrealstudiohelp.epicgames.com/s/article/How-do-I-report-a-bug