Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.0a23
2023.2.0a1
Issue ID
UUM-2439
Regression
No
[Bug] [Materials] Reset functionality doesn't work on "Emission" and "Motion Vector For Vertex Animation" in Material
Reset functionality doesn't work on "Emission" and "Motion Vector For Vertex Animation" in Material
Steps to Reproduce:
1. Open a new Project with HDRP Template
2. Window > Package Manager > ShaderGraph > Install
3. Create Assets > right-click > Shader > PBR Graph
4. Create Assets > right-click > Material
5. Assets > New Materia > Inspector > Shader > ShaderGraph > New ShaderGraph
6. Check option Emission = True
7. Check option Motion Vector For Vertex Animation = True
8. Cogwheel > Reset
Alternate reproduction steps:
1. Create/open a new Project using 3d template and Built in renderer.
2. Create a new default material using standard shader
3. toggle emission on
4. cogwheel/three dots > reset (results and "reproducible on" is the same for both reproduction paths)
Expected Result:
Emission and Motion Vector For Vertex Animation options set to the default value
Actual Result:
Emission and Motion Vector For Vertex Animation options does not set to the default value
Reproducible on: 2020.1.0a14, 2019.3.0b12, 2019.3.0b4, 2019.2.12f1, 2019.1.12f1
Reproducible with package Version: 7.1.5, 7.1.1, 6.9.2. 5.7.2
Environment: Windows 10 and Mac 10.14
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Hi, we are able to reproduce the error here but this issue currently don't have enough priority for us to look at. Workaround exist and it is not a blocker. We are agree that it is not good for workflow. If this issue is important for you please reopen the issue and we can raise the priority, but for now we will close it.