Search Issue Tracker
Fixed
Fixed in 2021.3.38f1, 2022.3.25f1, 2023.2.18f1, 6000.0.0b15
Votes
0
Found in
2021.3.35f1
2022.3.19f1
2023.2.9f1
2023.3.0b6
6000.0.0b11
Issue ID
UUM-62756
Regression
No
#pragma directives in .hlsl files are not being ignored when #include is used
How to reproduce:
1. Open the attached “PragmaBug.zip“ project
2. Open the “Assets/Scenes/ExampleScene.unity“ Scene
3. Observe the Game view
Expected result: The “RedColorSphere“ GameObject is red
Actual result: The “RedColorSphere“ GameObject is blue
Reproducible with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Reproducible on: macOS 14.2.1 Sonoma (Intel)
Not reproducible on: No other environment tested
Notes:
- Also reproducible in Player
- Warnings that indicate that the Pragmas will be ignored are shown in the Inspector when the “Assets/Shaders/CustomShader.shader“ shader is selected
- The documentation ([https://docs.unity3d.com/2022.3/Documentation/Manual/SL-PragmaDirectives.html|https://docs.unity3d.com/2022.3/Documentation/Manual/SL-PragmaDirectives.html|smart-link] ) is very explicit that Unity-specific #pragma directives in .hlsl files will be ignored unless the #include_with_pragmas directive is used
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shadows are not cast when the Light's CullingMask and the GameObject's Layer do not match
- Graphics.DrawMeshInstanced does not work when 2D Renderer and 2D Shaders are used
- SpeedTree does not move when using WindZone
- "Undeclared identifier 'LinearToSRGB'" error is thrown when creating a color variable with HDR color mode and assigning a Custom Render Texture target in Shader Graph
- Input System package is missing when creating a new HDRP project
Add comment