There might be a problem of trail renderer (or some new features I didn’t know?) in unity 5.3.1.
I add 3 sprite with box collider2D, rigid2D and trail renderer to all of it and watch their falling in a completely new project.
Once they fall at the same time, all trail has been draw correctly. However, once I let them drop one by one. I found no matter how many object I have in the scenes only 1 object would draw the trail. And more weird is that, if I let the other objects drop with that object, they’ll all draw the trail perfectly.
I’m pretty sure it didn’t happen before, cause my 5.2 built projects works well on trail renderer and I never change setting on trail renderer.
Is there any new feature for trail renderer, is this for saving resources? I don’t know, but how to solve it?
That’s with 5.3.1p2. Have you tried the patch releases?
To test it try changing the trail time and increasing the min vertex distance. You could be hitting some maximum trail vertex limit or bug.
You could also setup a cube dropper stress test that generates falling cubes on demand and recycles them to the top of the screen when they go off the bottom.
Note that I think Trail Renders were moved onto the GPU, so if you can try a WebGL build or the same scene on a different device/gpu.
And raise a bug with Unity if the patch releases does not resolve the problem.
I tried building the project, and it doesn’t work. Not even work after I build with the “web player”. It never happened before. My version is 5.3.1f1
You see, all the trail renderer works if the first cube drop and draw the trail renderer. But they can’t work separately.
what a strange problem.
Thanks, I know it could work when objects with trail renderer moving all together. But I just can’t let them work right when a single one moved and other stops, as I show in my videos
