Search Issue Tracker
Fixed
Fixed in 6.0.X
Votes
0
Found in [Package]
6.0.1-pre.1
Issue ID
PBLD-99
Regression
Yes
The ProBuilder and Editor shortcuts are conflicting by default
How to reproduce:
1. Create and open a new project
2. Install the ProBuilder package
3. Press the "P" key on the keyboard
4. Observe the opened "Shortcut conflict" window
Expected results: Nothing happens
Actual results: "Shortcut conflict" error window appears for the “P“ key
Reproducible in: 6.0.1-pre.1 (2023.3.0b4)
Not reproducible in: 5.2.0, 5.2.2 (2021.3.34f1, 2022.3.18f1, 2023.2.7f1)
Reproduced on: Windows 11 Pro
Not reproduced 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
- OnPostprocessAllAssets() is not called for a modified Prefab when another Asset is set Dirty in the same callback
- [Android] UIToolkit ClickEvent is fired when the device is rotated
- Compilation errors occur when "uintBitsToFloat(int)" gets used in OpenGLES
- User Reporting does not send reports when Managed Stripping Level is set to Low or higher
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is thrown when launching a project with a corrupted library
Resolution Note (fix version 6.0.X):
Removed ProBuilder shortcut conflicting with new default shortcuts in the Editor.