Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2018.3.0a1
2018.3.8f1
2019.1.0a1
2019.2.0a1
Issue ID
1140279
Regression
No
Drag-select in Prefab Mode selects GameObjects with Gizmos in any loaded scene
How to reproduce:
1. Open attached project "Case_1140279_repro.zip"
2. Open "SampleScene" scene (in "Scenes" folder)
3. In the Hierarchy, select "Cube(5)"
4. Open Prefab Mode
5. Select 2 rightmost cubes with drag-select
6. In the Hierarchy, drag selected objects to "Cube(6)"
Expected result: No new GameObjects appear
Actual result: GameObjects from the loaded scene appear to be selected as well
Reproducible with - 2018.3.11f1, 2019.1.0b9, 2019.2.0a10
Notes:
1) When exiting Prefab Mode, if "Discard Changes" is clicked, those GameObjects that come from the scene are irreversibly deleted.
2) When an object with a gizmo from the scene is in the drag-selection area, there are no Transforms arrows.
3) It looks like when in Prefab Mode, the prefab is placed in the (0;0;0) position of the loaded scene. This means that if an object with a gizmo is in the (0;0;0) position in the loaded scene, it will be on top of the prefab in the Prefab Mode.
4) Not reproducible with 2017.4 because Prefab Mode was not implemented yet.
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
- GfxDevice::UpdateBufferRanges when running UIBuilder tests
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
Resolution Note (fix version 2019.1):
Fixed in 2019.3.0a1
Fixed in 2019.2.0a15
Fixed in 2019.1.3f1
Fixed in 2018.4.3f1
Resolution Note (fix version 2019.2):
Fixed in 2019.2.0a15