Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.4.4f1
Issue ID
1062770
Regression
No
Game Objects from a Scene in an AssetBundle do not work properly if they depend on assets from another AssetBundle
Reproduction steps:
1. Open "ShaderAssetBundleTest.zip" project
2. Open "TestScene" Scene
3. Enter Play mode
4. Look at the two Game Objects (Left - Custom Shader, Right - Standard Shader)
5. Exit Play Mode
6. Open "Loader" Scene
7. Enter Play Mode
8. Look at the two Game Objects
Expected Result: The Left Game Object should look like in the "TestScene" scene
Actual Result: The Left Game Object doesn't look as expected
Fixed with: "Scriptable Build Pipeline" package
Reproduced with: 2018.3.0a9, 2018.2.4f1, 2018.1.9f1, 2017.4.9f1, 2017.3.2f1
Note:
Need to rebuild bundles through versions
"Window" -> "AssetBundle Browser" -> "Build" -> "Build"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment