Search Issue Tracker
Fixed in 5.0.1
Votes
1
Found in
5.0.0f4
Issue ID
679085
Regression
Yes
Asset bundles not working after 5.0f2
To reproduce:
1. Open attached project (WebGL assetbundles.zip)
2. Build and run WebGL
3. Press 'load asset'
4. Notice that asset loads but the Shader is broken
Comments (3)
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
dm_bond
May 09, 2015 03:22
persist in 5.1.0b6
fullike
Mar 28, 2015 15:32
And, if the shader has a built-in fallback, for example: diffuse, that fallback will be used. It does't output any error when build the asset bundle.
fullike
Mar 28, 2015 14:53
I've met the same problem.
Custom shaders in AssetBundle are broken if BuildTarget is WebGL. After the bundle has loaded, the shader can be assigned, but it's pink. All material property has lost and output "No property" error. It's urgent for us. Please check it. Thanks