Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.2f1
Issue ID
934024
Regression
No
Material inherits Rendering mode from other materials in a scene when running a standalone build
Steps to reproduce:
1. Open the attached project(Own Cloud)
2. Open the MainScene scene
3. Build and Run
4. Observe the objects are fading
5. Close the build and go back to Unity
6. Select Assets/ErrorMat.mat and change Rendering mode to Opaque
7. Build and Run
8. Observe the objects do not fade (In Editor works fine)
Actual results: Material inherits Rendering mode from other materials in a scene when running a standalone build
Expected results: Material should not inherit Rendering mode from other materials in a scene when running a standalone build
Note:
In Editor everything works as expected
Reproduced with: 5.5.4p2, 5.6.2p4, 2017.1.0p1, 2017.2.0b4, 2017.3.0a1 (DX11, DX9, OpenGL3)
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 when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
This is a duplicate of issue #822767