Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0b4
Issue ID
1036146
Regression
No
[Renderer] GPU Instancing glitches out mesh particles when a standard particle shader is initially assigned
Repro steps:
1. Open Scene1 from the attached project.
2. Drag the AssignMe material from the project window onto the particle system
3. Observe glitch
Notes:
- not a regression, happens in 2018.1, where the feature was introduced.
RichardK note:
- i think we can fix it by hooking into the SetDirty call on the SetMaterial. either make it virtual and override it, or hook into whatever it causes to be called (was it UpdateRenderer or something?)
- basically we need to reset the vertex streams hash to 0, to forceit to be recalculated, whenever the material changes.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment