Search Issue Tracker
Fixed
Fixed in 6000.0.X, 6000.0.23f1
Votes
5
Found in
6000.0.16f1
Issue ID
UUM-78665
Regression
Yes
Shader errors in DXC when building an empty URP project for Windows platform on a MacOS machine
Reproduction steps:
1. Create a new URP project for Windows platform on a MacOS machine
2. Build the project for Windows platform
Expected result: The project is built without errors
Actual result: “Shader error in 'StpSetup': DXC: can only use DXC to target D3D from the Windows Editor. “ errors in the console
Reproducible with: 2023.3.0a18, 6000.0.16f1
Not reproducible with: 2021.3.43f1, 2022.3.41f1
Couldn’t test with: 2023.3.0a17 (BuildFailedException)
Reproducible on: macOS 14.6.1 (M1 Max)
Not reproducible on: No other environment tested
Note: No repro with built-in pipeline
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
thylaxene
Sep 26, 2024 02:41
Saw these errors first time with 6000.0.20f1 macOS 14.6.1 on M1:
"Shader error in 'StpSetup': DXC: can only use DXC to target D3D from the Windows Editor. If DXC use is not intended, make sure no built shaders have DXC enabled explicitly via '#pragma use_dxc d3d11', '#pragma use_dxc' or implicitly via '#pragma require' with feature arguments that are only available through DXC. at kernel StpSetup"