Search Issue Tracker
By Design
Votes
0
Found in
6000.1.4f1
6000.2.0b2
Issue ID
UUM-105434
Regression
Yes
Prefabs are placed not in their relative Transform positions when adding them in Prefab Edit Mode
How to reproduce:
1. Create and open a new project
2. Create 2 of any 3D GameObjects and set their positions to (0,0,0)
3. Create Prefabs of the GameObjects
4. Enter the Prefab Edit Mode on the first prefab
5. Add the other Prefab to the Hierarchy 5 times
6. Observe the Scene view
Expected result: All instanced Prefabs are in the same position (0,0,0)
Actual result: All instanced Prefabs are in different positions
Reproducible in: 6000.1.0b3, 6000.1.4f1, 6000.2.0b2
Not reproducible in: 2022.3.62f1, 6000.0.49f1, 6000.1.0b2
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Before the regression, all instanced Prefabs are placed in their Transform positions relative to the parent
- The first prefab is instanced at the position at which the camera is looking
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
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
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.
The implementation is working as designed, but we will log the complaint here as Product Feedback so this can be considered in any future placement work