I made a feature request for a toggle which a staff member replied to 
3 Likes
Roblox really needs to do a better job of considering how changes like this will disrupt people’s workflows before pushing them live, especially when there’s no option to disable it. This is a great addition for copying things between files, but is seriously disruptive to many builders’ workflows. Almost every builder I know has collisions disabled, as you often need to be able to place parts inside of each other. It would be very inconvenient having to repeatedly toggle the collisions setting on/off.
Since the goal for this is to allow copy/pasting assets between different files, maybe a better solution would be:
- If copying something from a different file, or from a non-Workspace service, it will be pasted into its original location
- If copying and pasting something within the same Workspace, use the old behavior, which would be more expected within this context
13 Likes
Please tell me how this is supposed to help us, please consult with developers before you make such a change. You guys never ask the community how they feel about changes to Studio, you guys just make the changes and a lot of your updates piss us off…
2 Likes
It’s genuinely amazing how people will complain about a good update and be perfectly content with an update that causes detrimental change to the platform.
1 Like
I can’t do “paste into objects” which copies & pastes it automatically a million times(to the amount of selected objects) with the duplicate feature. And I can’t duplicate an item between windows. Which are 99% of my use cases here.
2 Likes
As an environment artist, I use “duplicate” and “paste-into” a lot, but never use straight “paste” as I have complicated folder structure and never want an item to be in the root of the workspace. So for me to find this update useful it would also need to apply to “Paste-into”, in which case it would be VERY useful.
So another vote for applying this to shift-ctrl-v.
3 Likes
This could be useful to new developers, however to people like me who have been using this tool to move parts across a map it isn’t all that helpful.
I also think duplicate already does this but slightly easier. Hopefully we can get some option to make it go where you want it to.
3 Likes
I don’t usually dislike any Roblox Studio updates, but this one I really do dislike. I do believe it is an improvement for some cases, for example it would be a great Improvement for newer developers, but for older developers this really isn’t the best improvement. This is basically Ctrl - D with extra steps.
4 Likes
Please revert this, this is so annoying to have to relearn the way I build.
5 Likes
so now we have 2 buttons that do the same thing, kind of pointless : /
3 Likes
I was about to get on studio to Work on a Big Change for my Map and What Im Hearing is not Acceptable for me
3 Likes
Hello, this ruined my workflow as I use Copy-Paste to have parts get set on top of other parts.
1 Like
We are thinking about that let me see about this I know that is a problem we are thinking is vehicle car jailbreak
2 Likes
Workflow updates can be incredibly disruptive for a lot of people. I regularly use duplicate when I need more of an object and would exclusively use copy & paste to move objects to a new location by selecting a different part and then pasting it to that location.
The aspect of being able to paste to a selected object’s location is overall beneficial and isn’t something that should have been lost with collision checks toggled off.
The following should be the preferred functionality of the update.
-
When pasting something from your clipboard without having an object or part selected should use the object’s original location.
-
When pasting something from your clipboard while an object or part is selected, it should use the selected object’s location.
A workaround for being able to do the above would be to toggle collision checks, but then you still run into the issue of that chair you want to paste into a house is now on the roof instead of on the floor of the room you have selected.
Something else that could be a feature is a “Paste-to-Location” function, which would paste an object to a select item’s location. (Ctrl+Alt+V as the proposed shortcut)
2 Likes
now, this is a great idea. I want to be able to paste origin but I also wanna paste regularly.
2 Likes
This is a complete and total misunderstanding of the feedback. Paste is fine. Paste should respect the collision setting. Duplicate is what people are complaining about. Duplicate should never use collisions. If you add a context menu item for this it will be a complete waste because it’s already easier to just paste it into Lighting and drag it into Workspace. Make it easier. Keep the paste behavior. Fix duplicate.
5 Likes
it’s a major headache of finding the Model tab in Studio and clicking the Collisions checkbox only to need to click it again a few moments later.
You can make this far less cumbersome by assigning a hotkey to it in File > Advanced > Customize Shortcuts > Collision Check. I’ve assigned it to Shift + B, for example’s sake.
We have rolled back the change and put things as they were. And soon we will be adding a new and separate command to “Paste at Original Location” to the right-click context menu.
This isn’t entirely satisfactory, either. I have never found the “stacking” behavior of pasting (or duplicating) useful. If I want to drag a piece out after duplicating it, I can hit Ctrl + 2 and use the move gizmo to move it from its origin (I almost never use freehand dragging unless I’m aligning a part to a surface).
I was really looking forward to this change, as stacking is unwanted behavior for me. The new solution of requiring a right click context menu is an extra step that is still inconvenient.
I like the idea of “Paste into” behavior being at origin, as others have suggested.
I also think everyone could be satisfied if the behavior were made to be a toggle rather than a discrete action in the context menu.
… On that note, “Collisions” already was a toggle for it that was intuitive, and especially with assigning it a hotkey, it seems to me the change was just fine as it was.
2 Likes
Thank you for reverting this change. It was really affecting my workflow and (clearly) many others as well.
2 Likes
The new behavior is absolutely what I want when pasting between two copies of Studio, like to bring a structure from an older, saved copy of my place into the current place. Many developers know there is a workaround where you can paste-into somewhere like ServerStorage, then drag the copy into the Workspace, but this is not intuitive, it’s an implementation-defined behavior developers discover and then make use of.
It feels to me like some of the proponents for the old paste behavior might be better served by Studio having a proper “place a copy here” tool, like many games have for placing furniture and things when decorating your home/plot. Various model stamping plugins have existed over the years to compensate, but I feel like this should be a built-in, first-class tool.
The existing behavior of Paste has always been a bit strange; if the 3D viewport has focus, it tries to paste the object where the camera is looking. But you can move the camera and unless you left-click again in world, your item will be pasted where the camera used to be looking before you moved it. This is just weird IMHO. A right-click menu “paste here” that does a raycast from the cursor location into the world would make more sense to me (along with right-click “move selected item here”).
1 Like
For those following this thread/feature:
We have just added 2 new commands to the right-mouse context menu:
“Paste At Original Location” and “Paste Into At Original Location”
They do not have default hotkeys, but you can add them using File->advanced->customizeShortcuts.
And all the paste variations have the same behavior, whether collisions are enabled in the ribbon or not.
These allow you to have the behavior we tried to give you before, without altering any of your existing workflows.
There will be a separate announcement shortly but you can use these as of now.
6 Likes