Search Issue Tracker
Fixed
Fixed in 6.0.5
Votes
0
Found in [Package]
6.0.5
Issue ID
PBLD-103
Regression
Yes
Can't delete Polyshape when it's in control point placement state
Reproduction steps:
1. Open the attached “BugRepro” project
2. Create a new Polyshape GameObject (Tools > ProBuilder > Editors > New PolyShape)
3. In the Hierarchy window, select and delete the PolyShape GameObject created in the previous step
Expected result: The PolyShape GameObject is deleted
Actual result: The PolyShape GameObject disappears, but instantly reappears
Reproducible with: 6.0.1-pre.1 (2023.3.0b4)
Not reproducible with: 5.2.2 (2021.3.34f1, 2022.3.18f1, 2023.2.7f1, 2023.3.0a19)
Reproducible on: Windows 11, macOS 14.2 (Intel) (by user)
Not reproducible on: No other environment tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 6.0.5):
Fixed a bug where creating a PolyShape, then immediately deleting it would create a new GameObject.