Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b16
Issue ID
792256
Regression
Yes
[Shuriken] Error messages inIndex, inValue, sort[0] floatValue with particles having custom shaders
Steps to reproduce:
1. Download and import attached project. (ParticleEffectsPreview.zip)
2. Open scene: 02_effects_preview
3. Press play
4. Inspect the console.
Error message appears:
inIndex == 0 || (inValue >= 0.0f) == (sort[0].floatValue >= 0.0f)
Regression from: 5.3.4p2
Comments (3)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Martin_H
Aug 08, 2016 22:45
I still get the same error message in 5.4.0f3
Might be connected to using particle system collisions, when I disable those the error seems to go away.
Al3_x
Jul 06, 2016 13:51
I have this issue too, but I'm using 5.2.2f1 Personal.
lastcode
May 28, 2016 07:24
Found in
5.4.0b18