Search Issue Tracker
Duplicate
Votes
0
Found in
5.0.0f4
Issue ID
682850
Regression
Yes
[Material] Emissive and Transparent properties are not properly copied to new material
Steps to reproduce:
1. Open attached project's scene "Default"
2. Enter play mode.
3. Observe not correctly copied materials:
Two cubes in a front should look the same, two cubes and the back should change colors randomly. Right cubes have copied materials from left cubes.
4. In "Color Change Dest" and "Transparent Dest" inspector expand material component. One at the back ("Color Change Dest") starts working, at the front "Transparent Dest" gets correcrt color, but transparency is still not displayed correctly.
5. Exit play mode.
6. Select "Color Change Dest" and "Transparent Dest" and in the script "Copy Material" check "Copy Shader Keyword".
7. Enter play mode.
8. Cubes look like after step 4. (Transparency is still not displayed correctly)
-
eheimburg
May 24, 2015 03:26
This bug makes it impossible to actually use Unity 5 "standard" shaders with dynamically configured content. It's a huge deal that breaks large-scale workflows, and it should be a hell of a lot higher priority.
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
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- OnPointerExit and OnPointerEnter is mistakenly called when an overlapping child Image is destroyed
- Dynamic text is rendered in the background when it is inside the <font> tag
This is a duplicate of issue #677642