Search Issue Tracker
In Progress
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
- Internal Package Manager window lines becomes duplicated or splits into two when window is docked
- Particle System curve editor does not remove or delete a curve when clicking the "Remove" button
- Some deprecated packages are seen in "Unity Registry"
- [Material]The emission of the materials used in scenes does not carried over correctly after upgrade project to 6000.0.44f1
- Crash on StackWalker::GetCurrentCallstack when opening a project
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.