Search Issue Tracker
Fixed
Fixed in 6.0.5
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
- Cancelling a Package installation leads to invisible compilation errors preventing the user to enter Play Mode when the “Cancel” button is clicked, and does not actually cancel the package install as it appears in the Project after the Editor is restarted
- NullReferenceException occurs when searching presets in “Select Preset” window after selecting a GLTF Importer preset
- Dynamic TMP_Font asset shows up as modified in source control when TextMeshPro text using it is changed
- “Output value ‘outMotionVec’ is not complete” warning logged after creating Canvas Shader Graph Asset
- SVG Image Component loses Source SVG Image field references when upgrading to a different Vector Graphics package version
Resolution Note (fix version 6.0.5):
Removed ProBuilder shortcut conflicting with new default shortcuts in the Editor.