Search Issue Tracker
Fixed
Fixed in 6000.2.9f1, 6000.3.0b7, 6000.4.0a2
Votes
4
Found in
6000.1.2f1
6000.2.0a10
6000.3.0a1
6000.4.0a1
Issue ID
UUM-104560
Regression
Yes
Prefabs are instantiated in the wrong position when dragging and dropping from Project window to Hierarchy
How to reproduce:
1. Create and open a new project
2. In the Hierarchy, right-click and select “3D GameObject → Cube”
3. Drag and drop the cube from the Hierarchy into the Project window to create a Prefab
4. In the Inspector, take note of the Prefab’s position
5. Move or rotate the Scene view camera slightly
6. Drag and drop the Prefab from the Project window to the Hierarchy window
7. In the Inspector and Scene view, observe the instantiated Prefab’s position
Expected result: The position of the instantiated Prefab is equal to the position shown in the Project window
Actual result: The position of the instantiated Prefab differs from the position shown in the Project window
Reproducible with: 6000.1.0b3, 6000.1.2f1, 6000.2.0a10
Not reproducible with: 2021.3.51f1, 2022.3.61f1 (e6a1f07378cd), 6000.0.48f1, 6000.1.0b2
Reproducible on: Windows 10 (by user), Windows 11
Not reproducible on: No other environments tested
Note: The Prefab is instantiated relative to the Scene view camera’s position/rotation, hence the need for step 5
Comments (4)
-
IanT
Jan 21, 2026 10:02
It's indeed insanely bad, it seems they just let their brain at home when making these UX decisions! Or is this team so bored that they actively look to prank users?
Anyway, the very least, as the other users mentioned, is to not have set the bug to "fixed" (since it wasn't a bug but a feature – no joke here, unfortunately), and above all to have clearly stated the comprehensive path to switch back to the sensible placement behavior. I had to rely on other users' more detailed comments to find out that my version (6000.2.7) doesn't feature the option.
-
HRDev
Nov 07, 2025 10:12
Unity, please make "Use prefab asset position when dropping on the Hierarchy window" ON by default. This restores the behavior that has always been the standard in Unity, and makes the most sense when dragging in the Hierarchy Window. It also allows us to have both behaviors available based on whether we drop in the Scene view or the Hierarchy window.
-
martin_noble
Oct 28, 2025 09:28
Note for others who might stumble upon this:
In the versions 6000.2.9f1 and 6000.3.0b7, which are claimed "Fixed" at time of this writing, this behaviour still occurs, but It seems there is a setting in the "Preferences -> Scene View" tab, called "Use prefab asset position when dropping on the Hierarchy window". It is turned OFF by default but when being turned on, the behaviour seems to be as it was in previous versions. -
Gillissie
Sep 03, 2025 17:47
I am continually astounded at the bad UX decisions being made by Unity every day. Congratulations, you made Unity worse by design. Again.
If there is a preference setting for this dumb behaviour, please tell us how to find it, rather than just saying "3D Placement Rules preference".
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
Placement of objects in the scene has now been unified under the 3D Placement Rules preference. The expected behaviour described in this ticket was an unexpected side effect of the previous implementation.
To restore previous behaviour, we have added the "Use prefab asset position when dropping on the Hierarchy window" preference to allow prefabs to be placed at the position saved in the assets root transform when they're placed in the scene via the Hierarchy window
Resolution Note (fix version 6000.4.0a2):
Placement of objects in the scene has now been unified under the 3D Placement Rules preference. The expected behaviour described in this ticket was an unexpected side effect of the previous implementation.
To restore previous behaviour, we have added the "Use prefab asset position when dropping on the Hierarchy window" preference to allow prefabs to be placed at the position saved in the assets root transform when they're placed in the scene via the Hierarchy window