Search Issue Tracker
Won't Fix
Under Consideration for 6000.0.X
Won't Fix in 6000.0.X
Votes
0
Found in
6000.0.62f1
Issue ID
UUM-129393
Regression
No
IPreprocessShaders not invoked if Mult-Process AssetBundle Building is enabled
Reproduction steps:
1. Open the attached project "ReproProj"
2. In menu bar, click Tools > Build Asset Bundles
3. Observe the Console
4. Note that the size of the bundle is printed to the Console (approximately 6025)
5. Open “/Assets/Editor/ShaderPreprocessor.cs”
6. Comment out lines 20 and 21
7. Repeat steps 2 and 3
Expected result: Printed bundle size changes to approximately 22635
Actual result: Same bundle size is printed in the Console
Reproducible with: 6000.0.64f1 6000.3.1f1, 6000.4.0a1 (b27b8eafe426)
Not reproducible with: 6000.5.0a3
Fixed in 6000.4.0a2 (417aa67423b3)
Testing environment: macOS Sequoia 15.4.1 (M1)
Not reproducible on: Windows 10 Enterprise 21H2
Note:
- With Windows only reproducible on 6000.0.62f1, but fixed in the latest versions
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The multi-process asset build pipeline was deprecated whilst we work on using the tech in a more effective way. The existing implementation won't be seeing any more development, but promise we're working on it!
Resolution Note (6000.0.X):
The multi-process asset build pipeline was deprecated whilst we work on using the tech in a more effective way. The existing implementation won't be seeing any more development, but promise we're working on it!