Search Issue Tracker
Not Reproducible
Votes
1
Found in
2018.2.0f2
Issue ID
1080174
Regression
No
Particle System's Renderer complains about Vertex Streams not matching when the Shader doesn't require it
How to reproduce:
1. Open a new Unity project
2. Import user's "Bug_report_Particles.unitypackage"
3. Find "EstelaDesierto_Real_MBT_GPU" prefab in Assets > 05_particulas > Tanques > Estelas > Resources and drag it into the Hierarchy
4. Expand "EstelaDesierto_Real_MBT_GPU" prefab in the Hierarchy and select "Dust02" GameObject
5. In the Inspector open Renderer's tab and Shader's tab
Expected result: the Shader does not require a 'Tangent' stream so the UI shouldn't complain about it.
Actual result: UI complains about 'Tangent' stream even though the Shader does not require it.
Reproducible with - 2018.3.0b1, 2018.2.8f1, 2018.1.9f2, 2017.4.11f1
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
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
radhat2009
May 03, 2020 05:45
I know this is old but someone might come looking.
I got the same error using Unity Example effects, namely BigSplash.
What I found was that Ripple did not have matching arguments in the Custom Vertex Stream section. It was missing UV2 and AnimBlend. All 3 others (BigSplash, SmallDrops, BigDrops) had the exact same arguments. I made them match and viola! Bob's your uncle. I hope this helps someone else out.
wklogoo
Aug 01, 2019 02:01
I faced this problem too.
For my case, it is the EnergyExplosion effect from the Particle Pack, after applying the LWRP:
- The LWRP particle unlit shader wants a TANGENT like information;
- however, the EnergyExplosion.mat does not have such information.
Anyway to solve / work around this.
afshin_a_1
May 23, 2019 16:54
i'm also kinda getting this error with using unity shader "Particles/Standard Unlit" using default particle system without any touch. it's wierd.
it says
vertex streams do not match the shader inputs.
- TEXCOORD streams do not match
Yusufu_Cote
Apr 09, 2019 21:55
Ran into this issue as well.
tatoforever
Mar 25, 2019 19:38
To reproduce the bug, instantiate any Standard/Particle in Play mode with a particle that is in Fade mode with Normal maps enabled.
tatoforever
Mar 25, 2019 19:09
This is 100% reproducible and is a bug
You can easily debug what the particle system is trying to send and what the shader input has.
Particle is trying to send data to TEXCOORD but what the shader has is TEXCOORD0.
AtomicArtist42
Feb 18, 2019 09:50
I have a particle system that uses the standard surface particle shader and custom vertex streams. If no tangent stream is added I get an error in the system, if I add a tangent stream the shader complains that it doesn't need it and removes. Would really like this issue to get addressed asap.