Search Issue Tracker
Active
Under Consideration for 6000.3.X, 6000.4.X
Votes
0
Found in
6000.3.0b3
6000.4.0a1
Issue ID
UUM-119648
Regression
No
Shader warnings thrown when applying changes in Shader Build Settings > Keyword Declaration Overrides
Steps to reproduce:
1. Create new Unity project using empty Universal 3D Template
2. Open Project Settings window
3. Select Graphics tab
4. Press “+” button to add a new keyword in Keyword Declaration Overrides
5. Type a keyword name (Testing would do)
6. Change “Type override” to “shader_feature”
7. Press “Apply” button
8. Observe the Console window
Actual results: Shader warnings are thrown in the Console when applying Keyword changes in Keyword Declaration Overrides
Expected results: No Shader warnings are thrown when applying
Reproducible with versions: 6000.3.0b3, 6000.4.0a1
Can’t test with versions: 6000.2.6f1 and lower (No Shader Built Settings available)
Tested on (OS): Windows 11, macOS Silicon, Sequoia 15.6 (M1)
Warnings:
- Shader warning in 'PatchAllocation': array reference cannot be used as an l-value; not natively addressable, forcing loop to unroll at kernel Allocate at (269)/Library/PackageCache/com.unity.render-pipelines.universal@f90c9a894466/Runtime/RendererFeatures/SurfaceCacheGlobalIlluminationRendererFeature/SurfaceCacheCore/IrradianceCompression.hlsl(30) (on metal)
- Shader warning in 'ScreenResolveUpsampling': array reference cannot be used as an l-value; not natively addressable, forcing loop to unroll at kernel Upsample at (269)/Library/PackageCache/com.unity.render-pipelines.universal@f90c9a894466/Runtime/RendererFeatures/SurfaceCacheGlobalIlluminationRendererFeature/SurfaceCacheCore/IrradianceCompression.hlsl(30) (on metal)
- Shader warning in 'ProbeIntegrationOcclusion': use of potentially uninitialized variable (SampleRectangularLight) at kernel MainRayGenShader at (269)/Library/PackageCache/com.unity.render-pipelines.core@942a815dc3c0/Runtime/PathTracing/Shaders/LightSampling.hlsl(255) (on metal)
- Shader warning in 'ScreenResolveLookup': array reference cannot be used as an l-value; not natively addressable, forcing loop to unroll at kernel Lookup at (269)/Library/PackageCache/com.unity.render-pipelines.universal@f90c9a894466/Runtime/RendererFeatures/SurfaceCacheGlobalIlluminationRendererFeature/SurfaceCacheCore/IrradianceCompression.hlsl(21) (on metal)
- Shader warning in 'ProbeIntegrationDirect': use of potentially uninitialized variable (SampleFalloff) at kernel MainRayGenShader at (269)/Library/PackageCache/com.unity.render-pipelines.core@942a815dc3c0/Runtime/PathTracing/Shaders/LightSampling.hlsl(586) (on metal)
- Shader warning in 'LiveGI': use of potentially uninitialized variable (GetHeatmapColor) at kernel MainRayGenShader at LiveGI.urtshader(150) (on metal)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- StackOverflowException occurs and tests fail to load when the Test Runner window is opened while System.Windows.Forms.dll and System.Deployment.dll are present in the project
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment