Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
4.0.0
5.0.1
Issue ID
WBTRB-82
Regression
Yes
Terrain Tools shortcuts are conflicting by default
How to reproduce:
1. Create a new project
2. Install the Terrain Tools package
3. Click Edit → Shortcuts → Category → Terrain
4. Observe the shortcuts
Expected result: The shortcuts are not conflicting
Actual result: The shortcuts are conflicting
Reproducible with: 4.0.0-pre.2, 4.0.0 (2021.2.19f1, 2022.1.0a1), 5.0.0-pre.2, 5.0.0-pre.3, 5.0.0-pre.4, 5.0.1 (2022.2.0a15, 2023.1.0a11)
Not reproducible with: 1.1.2-preview, 3.0.2-preview.3 (2020.3.41f1, 2021.2.0a1)
Reproducible on: Windows 11 Pro
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
User impact for this issue is too minor, the team will be focusing on more critical issues and will be unable to address this anytime soon.
As a work around if you encounter this a pop up will appear where you can change the keybinds to your liking.