Search Issue Tracker
Fixed
Fixed in 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a3
Votes
0
Found in
6000.0.57f1
6000.2.3f1
6000.3.0b1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-116514
Regression
No
Broken compute shaders propagate via the cache server
How to reproduce:
1. Open the “Broken Compute shaders.zip“ project
2. Set up and connect to a Cache Server (Accelerator) in Edit > Preferences > Asset Pipeline
3. In the Project tab, in Shaders > CS folder, create a Compute Shader (or it can be created anywhere within the project)
4. Open the Compute Shader file in an IDE and inside the CSMain add ‘#include "foo.hlsl"’, then save the changes
5. Create externally a file named “foo.hlsl”
6. Select the Compute Shader file and observe the Inspector (error is still present)
7. Close the project
8. Delete the Library folder
9. Open the project and select the Compute Shader file
10. Observe the inspector
Expected result: No shader errors are present
Actual result: A shader error is present (“Couldn’t open include file ‘foo.hlsl’“)
Reproducible in: 6000.0.23f1, 6000.0.57f1, 6000.2.3f1, , 6000.3.0b1
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Workaround: Reimport the Compute Shader file
Notes:
- Locally not reproducible without Accelerator
- Reproducing this issue is incredibly inconsistent. Sometimes the issue is not reproducible in certain versions, and other times it is
- Because of these inconsistencies, the project might need to be reextracted to make the bug reproducible in certain versions, or a new project might have to be created
- And because of these inconsistencies, the bug could not be tested for regressions
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment