- Home /
Trail renderer lag issue
I have an object containing only a trail renderer parented to a rigidbody object at the bottom of a double pendulum. I would like the trail renderer to trace out the path of the pendulum, but the renderer seems to lag behind the pendulum body and after more than a few seconds has fallen so far behind the movement of the pendulum that the "tracing" effect is all but destroyed. Any ideas about what is going on? It seems strange that the (relatively) slow speed of the pendulum would be "too fast" for the trail renderer considering that the docs mention its use in bullet trails and the like. Is this a bug? Or a known issue? Or am I just missing something? I have the renderer time set to 100, and all four colors to full opacity white. Using the default particle image and shader. Widths are both 0.25. Any help would be appreciated.
Answer by jjmontes · Apr 28, 2014 at 01:39 PM
Trail Renderer has a "min distance" variable which defines the minimum distance the trail has to move before a new point is created in the trail path.
Try reducing that value to something suitable. Ie if your pendulum arc is 1 unit, use 0.05 (0.05 = 1 unit / 20 points in the trail).