Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1268327
Regression
No
Normal Map is malformed when loading GameObject and Material from separate AssetBundles
How to reproduce:
1. Download the attached "1268327.zip" project from the Google Drive link
2. Open the project
3. From the "Scenes" folder open the "Scene1" Scene
4. Enter the Play mode
5. Exit the Play mode and open the "Scene2" Scene
6. Enter the Play mode
Expected result: The Normal Map is applied correctly to the Cube
Actual result: The Normal Map is malformed on the one or more sides of the Cube
Reproduces on: 2018.4.26f1, 2019.4.8f1, 2020.1.3f1, 2020.2.0a21
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
- Crash on GfxDeviceD3D12::AllocBottomLevelAccelerationStructure when using Raytracing
- The search icon in the "Searches" sections is blurry and inconsistent
- "RenderingCommandBuffer" error is thrown when switching to the tvOS platform
- Left side cog menu button is obstructed by the maximum Y value of the graph when editing a curve in the Particle System Curves
- "Property exceeds previous array size (64 vs 32)." warnings are thrown when switching from tvOS platform to a Standalone platform after restarting the Editor
Resolution Note:
Mesh optimization works by reading usage data from materials & shaders, so if those two pieces of data are in different bundles, it won't work.
There are some options to fix this issue:
-Not put the material in a bundle leave it as none. When building the bundle, it will put the material in the correct bundle.
-Disable mesh optimization.
-Switch to Scriptable Build Pipeline, it handles dependency better than the current build system.