Search Issue Tracker
Fixed
Fixed in 2022.3.60f1, 6000.0.43f1, 6000.1.0b10, 6000.2.0a7
Votes
0
Found in
2022.3.57f1
6000.0.36f1
6000.1.0b5
Issue ID
UUM-96214
Regression
No
Broken build (due to Shader Errors) is reported as Successful with Build and Run
Reproduction steps:
1. Open the attached “BuiltInRP6.zip” project
2. Make sure “Compute Fluids” Scene is in the Scene List (File > Build Profiles)
3. Build and Run the project
4. Observe the Console
Expected result: The Player build fails each time
Actual result:
On the first run an expected error is logged “Shader warning in 'Shader Graphs/ParticleShader': pow(f, e) will not work for negative f, use abs(f)“ warning and “Error building Player: 5 errors” logs are visible and the Player does not build
But building the project the second time, makes the Player build successfully, with no errors
Reproducible with: 2022.3.57f1, 6000.0.36f1, 6000.1.0b5, 6000.1.0a2
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Only reproduces with Build And Run
-"Build and Run" specifies "BuildOptions.StrictMode" which means any logged error will fail the build. Doing a regular player build in the UI does not specify this flag.
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note (fix version 6000.2.0a7):
Fix error handling when using the "Build and Run" option so that shader syntax errors, and other logged errors, are consistently treated as build failures. The bug involved cases where the content of a failed build was being reused, instead of the content being rebuilt, on the next build attempt. Note: The repro involves "Build and Run" because that uses the "strict" build mode option.
Resolution Note (fix version 6000.1.0b10):
Fix error handling when using the "Build and Run" option so that shader syntax errors, and other logged errors, are consistently treated as build failures. The bug involved cases where the content of a failed build was being reused, instead of the content being rebuilt, on the next build attempt. Note: The repro involves "Build and Run" because that uses the "strict" build mode option.
Resolution Note (fix version 6000.0.43f1):
Fix error handling when using the "Build and Run" option so that shader syntax errors, and other logged errors, are consistently treated as build failures. The bug involved cases where the content of a failed build was being reused, instead of the content being rebuilt, on the next build attempt. Note: The repro involves "Build and Run" because that uses the "strict" build mode option.
Resolution Note (fix version 2022.3.60f1):
Fix error handling when using the "Build and Run" option so that shader syntax errors, and other logged errors, are consistently treated as build failures. The bug involved cases where the content of a failed build was being reused, instead of the content being rebuilt, on the next build attempt. Note: The repro involves "Build and Run" because that uses the "strict" build mode option.