Skip to content

Conversation

@ErrantOverflow
Copy link

When you create the newObject, it copies the local position, rotation and scale of the original object, which is all fine, however, if the object itself is inside a transform with a position, rotation or scale that isn't the default one, it can cause some problems. It cam be fixed by simply assigning the same parent to the newObject.

You could argue that it wouldn't be necessary to do that if instead of using local position and rotation you used the global one, however, the scale is still a problem.

I was stuck trying to figure out why the sliced parts teleported through the map and it turned out to be this. I am sure this is a very hacky way of fixing this, but it worked for me, and hey, if it turns out to be a good solution, then perfect!

Leaving that aside, the slicing scripts work like a charm, thanks a lot for writing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant