Search Issue Tracker
In Progress
Votes
0
Found in [Package]
6.0.5
Issue ID
PBLD-238
Regression
Yes
All previous changes between "Grow Selection" operations are reverted when using "Grow Selection" for the second time in ProBuilder
Reproduction steps:
1. Open the attached “IN-103648.zip” project
2. Open the “SampleScene”
3. Select the “Cube” GameObject from the Hierarchy
4. In the Scene view toolbar, switch the Active Context to Probuilder (top icon on the left)
5. In the toolbar, switch to Face Selection tool
6. Click on any Face
7. Right-click > ProBuilder Select > Grow Selection (or Alt+G)
8. Then Right-click > Delete Faces (or Backspace)
9. Select any Face again
10. Repeat 7th step
11. Observe the “Cube” GameObject
Expected result: Additional Faces are selected
Actual result: All of the changes made in between “Grow Selection” operations are reverted back
Reproducible with: 6.0.1-pre.1, 6.0.5 (6000.0.50f1, 6000.1.6f1, 6000.2.0b4)
Not reproducible with: 5.2.4 (2022.3.63f1)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- If the “Undo History” Window is open while reproducing the issue, it will be visible how all of the changes are deleted momentarily once “Grow Selection” is used for the second time
- If any other changes are made in between 8-9th steps, like modifying any other GameObject in the Scene or the “Cube” GO itself, all of those changes are also reverted, which can cause loss of a lot of work
- Does not matter what kind of operation is performed on the 8th step, as long as it has some kind of modification
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
This is fixed now, and should go out in the next release.