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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment