Search Issue Tracker
By Design
Votes
0
Found in
2021.2
Issue ID
1338940
Regression
Yes
OnProcessShader is not called when building Development player build
Steps:
1. Open attached project
2. Make sure Development checkbox is OFF in BuildSettings
3. Make a player build
4. Observe console
-> there are messages saying "OnProcessShader..." (correct)
5. Clear console
6. Make player build again
7. Observe console
-> there are messages saying "OnProcessShader..." (correct)
8. Make sure Development checkbox is ON in BuildSettings
9. Make a player build
10. Observe console
-> there is no message saying "OnProcessShader..." (wrong)
Reproducible:
2021.2.0a18
2021.2.0a14.1979 (462ae11b66db)
2021.2.0a13.1875 (71a161db37e2)
Not reproducible:
2021.2.0a12.1768 (687b3b92c1e8)
2021.2.0a6.1011 (dc497bf8326a)
2021.1.8f1.2508 (4b480e725734)
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
- Changing "PreWarm" parameters on VFX Graph leads to significant performance drops and freeze
- Player display resolution changes to the native resolution of the monitor when Player becomes unresponsive
- [Quest] Game View is no longer rendered in the HMD if it's hidden in the Editor when using Meta Link
- Unity auto-generates code it can't compile when classes are renamed
- Terrain's "Grass Tint" Color picker has Alpha 0 by default
Resolution Note:
This is expected behavior. In the new incremental build pipeline you will only get callbacks when we (re)build assets. Which means that if all assets are up to date you won't get a callback, and assets from a previous build will be used.
This applies mainly to development builds at the moment, for release builds we always rebuild assets.