Copy/Paste Bug

Bug Reports Studio Bugs
#1

This has been around for a few updates.

When you copy/paste a model, the model will paste over the original part.
It used to be, it would paste over the selected part.

I think this is a bug because tons of functionality is just gone. Why would they remove the original copy/paste when it did the exact same thing, but more?

Thanks.

#2

Not sure what you mean. Elaborate?

#3

If I select a part and paste it, the pasted part is pasted ontop of the original part.

It used to be, that the part would paste on top of whatever part your selection was. This made it really nice to copy and paste especially in large maps.

Used to be:
Copy Part A
Pasted on selected part (game.Selection:Get()[1])

Now:
Copy Part A
Pastes over Part A regardless of selection

So it just feels like lots of functionality was removed for no reason. You could do the exact same thing with the original copy/paste just by selecting the original part and pasting (cause when you press CTRL-C, the original part is already selected).

Does that make sense? If not I can try to elaborate further.

#4

I get an issue in Studio where after a while of it being open I can’t copy and paste at all.

#5

Yeah that’s been around a long time.

#6

Okay, I see what you’re saying now.

If you want a similar behavior now for placing a bunch of copies of some object around a space, you could use Ctrl + D (duplicate).

But, it does seem like worse behavior, yes.

#7

[quote] Okay, I see what you’re saying now.

If you want a similar behavior now for placing a bunch of copies of some object around a space, you could use Ctrl + D (duplicate).

But, it does seem like worse behavior, yes. [/quote]

I have no idea what duplicate is o.O

I’ll check that out.

Also are you saying that copy and paste can be brought back to the way it was? I mean it seems like a 10 second fix.

#8

I just now had my clipboard fail in studio, can’t copy anymore. Though I’ve had studio open for 13 hours. I know this was once a more common problem, but I’m pretty sure it was fixed. If this happens again it might be worth reporting in a separate thread.

#9

“I know this was once a more common problem, but I’m pretty sure it was fixed. If this happens again it might be worth reporting in a separate thread.”

The most obvious cases have been fixed. But, it definitely still happens occasionally.