Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
5.0.1f1
Issue ID
691773
Regression
No
Not informative compute shader error reporting
On purpose there is some kind of error in a compute shader. In the editor the error message is a bit "laconic". It should be more explicit and more helpful.
Error message:
Shader error in 'ErrorReportingFail.compute': Compute shader compilation had a problem, your compute shader was not compiled correctly.
Reproduced on 5.0 versions. On 5.1 such error doesn't appear.
Repso steps:
1. open attached project "ShaderErrorReporting.zip";
2. right click on "ErrorReportingFail" shader in project view and reimport it.
3. not informative message appears in the console.
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 PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
Add comment