- Home /
The requested feature is not currently supported.
Visual Studio Community on Mac will not recognize HLSL
I use Visual Community on Mac with Unity, and what to edit HLSL shaders. I find that I get some syntax colour highlighting, if I use ".compute" or ".cginc" (but not ".hlsl") file type suffixes, but no support beyond that. As I'm still learning HLSL syntax, it's easy to make minor mistakes. I suppose I am spoiled by modern syntax highlighting and preemptive error checking. Without it, finding errors in my shader code is laborious.
Is there a way to get better support for detecting errors before building? What do Mac users do to make it easier to write and debug compute shaders?
A second, equally annoying problem is that files with ".compute" and ".hlsl" (inside "Assets/Shaders") do not even show up in the Visual Studio Community project browser. I have to open them from Unity.
yeah, i know. there’s no autocomplete. have you looked for extensions?
Yes. There is nothing that looks applicable in the built-in Extensions browser. And I tried various web searches. Web foo failed. Is there documentation on how to install them? I found a $$anonymous$$S docs page on how to make them, but I'm not up for that. I saw a rumour somewhere that Text$$anonymous$$ate plugins might be compatible, but maybe I was drea$$anonymous$$g. Not sure if that would do anything more than colour highlighting. Even better highlighting would probably help.