If I copy an Atmosphere or Sky object and try to paste it into something (Ctrl+Shift+V), it will place it directly underneath Lighting instead.
Workaround is to manually drag the instance from Lighting into the target location.
5 Likes
That’s a feature. They did that on purpose so you don’t accidently put an atmosphere in workspace or something and then wonder why it doesn’t work.
I can understand that for normal insertion or pasting, but “paste into” means the developer intends to paste into the selected object, not anywhere else. The fact that this behavior does not exist for any other class member (for example, you can paste sounds into anywhere even though they only work in some areas) leads me to believe this is a bug and not intended behavior.
3 Likes
They were just assuming there’s no need for you to put an atmosphere anywhere else. That’s all I was saying. Not that it’s good or anything.
-- Would like that to be changed because it is incredibly annoying to work with (I store Skys in folders for maps when prototyping them) but yeah, not a bug. Should make this a feature request.
If you made a feature request to make this consistent with other paste-into actions, please link it here so we can share our use cases on the feature request. I certainly have a use case that’s likely similar to Candyfloss’. 
Yeah, disabling the magic parenting in the case of Paste Into is definitely better. Should have a fix for this out in a couple weeks.
4 Likes
This should be resolved now, magic parenting still exists but won’t apply in the case of paste into.
3 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.