You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other features are functioning correctly, including code formatting, syntax highlighting, and context-aware features such as recognizing when #include'd files are used or not.
Lastly, these shaders are being written in ShaderLab files with a .shader extension and are within HLSLPROGRAM and ENDHLSL.
Other Notes
Tested on 2 different PCs running Windows 11 and on several different Unity projects.
Thanks. After investigation, these are intrinsics that are automatically defined, rather than defined in files that are added to the context via #include. As such, the system doesn't know about them unless we also add them to the parse context.
What I'm seeing
Common semantics are missing from autocomplete in Rider. A list of missing semantics are:
TEXCOORD0
(more generally,TEXCOORD{n}
)SV_POSITION
POSITION
INTERNALTESSPOS
SV_TESSFACTOR
SV_INSIDETESSFACTOR
though there may be others. The following screenshot shows the autocomplete suggestions when beginning to type
SV_POSITION
.If it would be helpful I can provide more screenshots of what appears when I start typing those other semantics.
Expected behavior
These common semantics would be included as autocomplete suggestions.
Environmental Setup
2022.3.1
2021.3.16f1
(LTS)3.0.18
The shaders are included in the
.csproj
file in the following way:Other features are functioning correctly, including code formatting, syntax highlighting, and context-aware features such as recognizing when
#include
'd files are used or not.Lastly, these shaders are being written in ShaderLab files with a
.shader
extension and are withinHLSLPROGRAM
andENDHLSL
.Other Notes
Tested on 2 different PCs running Windows 11 and on several different Unity projects.
Originally asked here: #216 (comment)
The text was updated successfully, but these errors were encountered: