| Author |
 Topic  |
|
|
redorav
Starting Member
United Kingdom
1 Posts |
 Posted - Nov 27 2024 : 6:39:49 PM
|
I recently bought VA and I've tried to make it work with my shaders. The whole hlsl file doesn't have any syntax highlighting at all and navigation is very clunky and slow. This is with VS 17.12.0. I don't have HLSL Tools installed.
VA syntax highlighting with shader does work in VS2019 and VS2017, it's just 2022 that it seems to have quite some issues with. Any ideas or suggestions?
Reverting to 17.10 makes it work, it's versions after that are broken. |
Edited by - redorav on Nov 27 2024 7:57:59 PM |
|
|
feline
Whole Tomato Software
United Kingdom
19066 Posts |
Posted - Nov 28 2024 : 06:53:07 AM
|
Apologies for this problem. Someone else reported this a couple of days ago, and I am seeing the same problem here. Visual Studio 2022 version 17.12.0 and above have changed something, which is stopping VA from applying syntax colouring to shader files.
VA colouring still works correctly in earlier versions of Visual Studio 2022, and earlier versions of the IDE. Having the shader tools doesn't make any difference to this problem for me.
Interesting that you are also seeing the performance problem. I haven't confirmed that here yet, but this was also reported, so it is good to get conformation of this side of the problem:
case=165194 |
zen is the art of being at one with the two'ness |
 |
|
|
Woody
Senior Member
Czech Republic
36 Posts |
Posted - Dec 10 2024 : 3:21:23 PM
|
| Syntax highlighting of .shader and .cginc files works fine for me (VS 17.12.3, VA 10.9.2537.0), but editing is a problem. After I press enter, my cursor always jumps to the first column of the next line. No matter the scope. It very annoying. I was blaming HLSL Editor Tool extension, but once I disabled Game Development -> Enable support for shader files, it's fixed |
|
|
|
panmotor
Starting Member
1 Posts |
Posted - Dec 11 2024 : 03:31:10 AM
|
Has Visual Assist released any updates addressing VS 17.12.0 compatibility?
|
https://tunnelrushgame.io |
|
|
|
feline
Whole Tomato Software
United Kingdom
19066 Posts |
Posted - Dec 11 2024 : 12:07:48 PM
|
Woody, so far I cannot reproduce this problem. Do you have the HLSL tools component of VS2022 installed?
Can you please export your VA and IDE settings and send them to me:
VA Options -> Performance -> Export Settings
IDE tools menu -> Import and Export Settings -> Export selected environment settings
I can then import them here and see if I can reproduce the problem.
Please send me the files via email:
[email protected]
including this thread ID or URL in the description, so we can match it up.
panmotor, no updates on this yet, but I am hoping for some soon. |
zen is the art of being at one with the two'ness |
|
|
|
Woody
Senior Member
Czech Republic
36 Posts |
Posted - Dec 12 2024 : 05:37:41 AM
|
| I was unable to uninstall the HLSL Tools in the VS->Manage Extension..., so I had it just disabled, but as you suggested, it was because it's been installed in the VS installer as a component. Removing it helped. But to be honest, I'm not sure I understand how the shader support is supposed to work. If I don't use HLSL Tools and have no special mapping in the VS Options->Text Editor->File Extension, I got no syntax highlighting. I need to map .shader and .cginc to MS Visual C++ first. Is that ok? |
|
|
|
Woody
Senior Member
Czech Republic
36 Posts |
Posted - Dec 12 2024 : 05:50:18 AM
|
hmm, I spoke too soon.
This is what I get now even with the HLSL Tools removed:
https://youtu.be/R_OFPmREPdM
I will see if I can send you the exported settings |
|
|
|
feline
Whole Tomato Software
United Kingdom
19066 Posts |
Posted - Dec 12 2024 : 07:14:48 AM
|
I am not sure what is going on with shader support and syntax highlighting personally.
For me, enabling:
VA Options -> Game Development -> Enable support for CUDA files (requires restart)
gets VA to become active in .shader and .cginc files. The VA navigation bar appears, the Alt-M list works, VA Outline works, and VA syntax highlighting is being applied in these locations. But I am not seeing VA syntax highlighting in the editor window.
Having said that, I don't have the NVidea CUDA development kit installed and working, so I am not sure if my current set of tests are a valid test. So reading that you are having similar problems and are actually working with CUDA files isn't reassuring.
Having said that, I still haven't been able to reproduce the caret jump to the first column, with or without the HLSL tools installed into VS2022. |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
19066 Posts |
Posted - Dec 12 2024 : 1:12:57 PM
|
I have put a note onto my bug report about these files not getting VA syntax highlighting by default, explaining how you have solved this:
case=165240 |
zen is the art of being at one with the two'ness |
|
|
|
feline
Whole Tomato Software
United Kingdom
19066 Posts |
Posted - Dec 17 2024 : 08:48:09 AM
|
After some digging, the trigger for this problem seems to be the combination of mapping the shader file extension to the C++ editor in the IDE options, and enabling VA shader support.� Nothing else seems to matter.
I have put in a bug report for this:
case=165309
since this is something it is good to be aware of.
I believe the root problem is that Microsoft made another change to Visual Studio 2022 in version 17.12.0 and above, which is stopping VA from applying syntax colouring in shader files.� In earlier versions VA syntax colouring worked correctly in shader files, once you turned on shader support.� Once we correctly handle this change in the latest VS2022 you shouldn't have to apply this file extension mapping any more, so the problem won't show up.� The bug report for this colouring problem is:
case=165194
|
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
HLSL Syntax Highlighting Not Working
