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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment