Severe spline mesh bug (Demo project included)

Simple to reproduce, just add a couple of spline meshes along spline - they’ll behave like that:
134732-
However, when using a mesh that is a cylinder without any loop cuts, it works properly:
134733-
Also, changing the mesh count to lower value (but too low to be smooth looking) causes the bug to disappear. I’ve included all of this in the simple demo repro project:

[DEMO REPRO PROJECT][3]

I’d be great if we could even use some workaround for this bug for now… But can’t find any.
Thank you!

Hi Slavq,

I don’t believe what you are seeing is a bug. For every mesh you add for ‘resolution’ you would need to interpolate another spline point inbetween the other points.

I’m going to move this over to the blueprint section for now and one of the other techs has setup something similar to this in the past. He is going to take a look as soon as he has time.

Also, in your demo project; both the ‘with’ and ‘without cuts’ meshes had the segmenting error for me. Did you just swap the mesh or did you also change a value somewhere?

Thank you.
Yes, just swapping the mesh, that’s why I thought that it’s a bug. Here is a gif that demonstrates this:

Hey Slavq,

I took a look at your project and after investigating I don’t think you are doing anything wrong. The math is correct and the workflow seems correct. What is happening is the vertices between the start and end point of the mesh aren’t scaling in a way that is proportionate to the end points. That creates bad overlap and a stair step effect.

This may be a limitation of the “set start and end” node not allowing it to effect verts properly between the start and end points. The reason your other mesh doesn’t have this issue is because there aren’t any verts that need to be properly interpolated.

I apologize for the confusion and we may need to investigate a little bit further to determine if this is a legitimate bug.

,

Ed

Just updating this has been determined to be a bug. You may track it here: Unreal Engine Issues and Bug Tracker (UE-44425)

If you normalize the tangents, the problem goes away.

Like this:

So I guess it has something to do with the tangents. Anyway, I’d prefer this bug to be fixed, but this helps as a workaround.