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
- "FileNotFoundException" thrown when adding "User" Index after deleting "Assets" Index in Search Index Manager window
- Camera Background Solid Color does not Render
- Raytracing renders artefacts and performance drops when switching Volumes at runtime
- Shader variants are compiled when creating a server build
- Crash on WeldVertexArray when opening a specific project
Add comment