Search Issue Tracker
Feature Request
Feature Request in 6.0.X
Votes
0
Found in [Package]
6.0.1-pre.1
Issue ID
PBLD-232
Regression
No
ProBuilder Tool item appears twice in the overlay when editing in Vertex/Edge/Face context
Steps to reproduce:
- Open a project and install ProBuilder
- Create any kind of primitive and select it
- In the Scene overlay, change the tool context to either vertex, edge or face
- Observe the overlay
Actual results: the Tool icon appears once
Expected results: the Tool icon appears twice
Reproducible with versions: 2023.3.0b1, 6000.0.40f1, 6000.1.0b10, 6000.2.0b2 (6.0.1-pre.1, 6.0.5)
Not reproducible with versions: 2023.3.0a18 (5.2.4)
Tested on (OS): Mac OS
Notes: The ProBuilder overhaul moved its tools from the dedicated window into the overlays and this issue is reproducible everywhere where that change is present so this is not marked as a regression.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for taking the time to report this bug and sharing your observations with us. After reviewing the details of the report, we’ve determined that this issue is not a software defect but rather an opportunity to enhance the clarity and usability of the UI.
As such, we’ve transitioned this report into a feature request to explore UI improvements that address the concerns raised. Our team will assess this feature request as part of our ongoing roadmap planning and prioritize it alongside other initiatives based on its impact and feasibility.
We greatly value your feedback as it helps us refine and improve our product.
Resolution Note (6.0.X):
Thank you for taking the time to report this bug and sharing your observations with us. After reviewing the details of the report, we’ve determined that this issue is not a software defect but rather an opportunity to enhance the clarity and usability of the UI.
As such, we’ve transitioned this report into a feature request to explore UI improvements that address the concerns raised. Our team will assess this feature request as part of our ongoing roadmap planning and prioritize it alongside other initiatives based on its impact and feasibility.
We greatly value your feedback as it helps us refine and improve our product.