Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2022.1.0a7
Issue ID
1365040
Regression
No
[DXC/DX12] No way to enable SM 6.6 features results in compiler error when e.g. using 64-bit atomics in a shader
How to reproduce:
1. Open the attached project ("Repro 2")
2. Select the "SM_6_6_repro" shader and in its Inspector click "Compile and show code"
3. Observe the errors in the Console (Reimport the shader if errors were cleared)
Expected result: SM_6_6 64-bit atomics are supported without issues
Actual result: "Shader error in 'Unlit/SM_6_6_repro': opcode '64-bit atomic operations' should only be used in 'Shader Model 6.6+'" when compiling for the D3D API
Reproducible in: 2022.1.0a10 (931a09a17a43), 2022.1.0a7 (d67c444e4fb7)
Note: SM 6.6 feature support added in 2022.1.0a7 DXC update and thus is not a regression
-
BoltScripts
Apr 01, 2023 01:05
Says this is fixed but it's still happening for me on 2022.2.8f1
Am I missing something or what.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a16