Search Issue Tracker
Won't Fix
Votes
2
Found in
5.3.5p8
Issue ID
814820
Regression
No
Material.SetPass sometimes doesn't cache results on DX9
Steps to reproduce:
1) Download attached project 'Preloading.zip' and open in Unity.
Note: Make sure that Graphics API is set to Direct3D9.
2) Open scene 'Main'.
3) Open the Profiler and view the CPU section.
4) Press Play.
5) In Game tab, click on "Step 1 - Material.SetPass (Preload)" button.
Notice in the Proflier that shows huge spike in Material.SetPassUncached (this is expected).
6) Now click on Click "Step 2 - Instantiate".
Notice in the Proflier that shows huge spike in Material.SetPassUncached (this is NOT expected).
Note: It doesn't happens every time after those steps, If you wasn't able to reproduce it from the first time, try again.
I was able to reproduce with OpenGLCore once.
Wasn't able to reproduce with DX11
Reproduced with: 5.3.5p8, 5.3.6f1, 5.4.0f1.
Not reproduced with: 5.5.0a3
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2017.1.0f3):
We do not support DX9 now.