Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.2.1f1
Issue ID
733702
Regression
Yes
[VSTU] Openning shader as first file in the project fails to open it in Visual Studio, opens MonoDevelop instead
Steps to reproduce:
1. Create new Unity project
2. Create a new shader file
3. Make sure default text editor is set to Visual Studio
4. Double-click the shader file to open it
5. Notice it starts opening Visual Studio, then throws "DirectoryNotFoundException" and opens MonoDevelop instead
Workaround: Add a C# script file to the project, double-click the shader file, it will open in Visual Studio then.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Add comment