If the road is 2d, Yes. If it's not, probably not,... maybe with some modifications. In theory, I separated all vectors into X and Y component, and I purposely left out the Z, so maybe it's worth giving it a try. Personaly I don't see that much uses for this 3d Offset, but I may be mistaken. If you manage to work it out, let me know ;)

@@BlenderBash You'll probably have to offset the curve points perpendicular to the z coordinate or the point. That way the up and down movement of the curve should be irrelevant. You also have to sample both the previous and next point and a lot more and without variables or attributes with names it just seems daunting. Maybe I'm too lazy :)

All kinds of circle (bezier or mesh) work just fine. Make sure you're using Blender 3.1.

Hi! Yes, I was aware of this problem, but at the time, I wasn't sure there was a solution to it, and I would just use it on a single curve at a time. However I have actually found the solution in the last couple of days. This new node is much more complicated though. But now It should works flawlessly for multiple curves, or so it would seam at the moment. Unfortunatelly I'm away for work this whole week, and I m not able to test the node thoroughly. Sometimes next week I will probably be able to upload the updated node and everyone who purchased it will be notified.

I don't exactly know what you mean by strange geometry. Nothing should be strange. Every result should be explainable.

@@BlenderBash I am considering that the offset geometry became strange over same amount of offset ... in other words the off set value can be anyone?

I mean off set amount what you call "t" in the video. Also do you think offset rules can be applied both convex and concave geometry ? also when you apply formula c=t/sin(Omega) what happen if Omega = 0? this happens when 3 point are aligned

Contact me on Gumroad, you can send me your file so I can understand better what's the issue exactly

Hello Michele, I found out what was causing this issue and corrected it. I made a post on Gumroad for everyone who purchased the node. You can download the new version there. Bye

You can, but you need to set the Resample Curve value high enough that it looks fine with the longest spline of them all

Would you care to elaborate? Im very interested in what you meant

@@BlenderBash in vector math node have the option normalize wich is the vector divide by the norm of the vector, so we just calculate the normalize of the 2 vectors then do the dot product and last the arcocosine

Is your curve a spline maybe? That would cause these problems you're having. If it is, try increasing the resample curve value. If you want, you can send me the blend file and I would gladly check it out. You can find my e mail in my channel's About section

@@BlenderBash That's so nice of you, but I already fixed it (kind of). And yea, it's a spline (a SVG I've imported) and in my case it helped to decrease the resample curve. Now it works like it should. Thank you a lof for this node setup

If you're trying to do a neon sign or something like that (I literally just bought it for this reason), a good tip is to use a 'Set Spline Cyclic' node after the string to curves node, and have it unchecked. This will remove the weirdness and give a pretty good neon-ish result. Also I found that adding a 'set spline type' node, and using NURBS as the method seems to work best. And use a nice chunky font, anything too fiddly won't work so well. Basically this is a Blender issue where the spline joins back up with itself. I'm pretty sure the normals are flipping at the join points for some reason.

@@btn237 Still more or less the same issues. For example if i use the string 'Hellllo' only some of the l are messed up ... so it is inconsistent.The solution used in the neon tutorials or boxed letters make use of lofting a spline along a spline path. That mostly works, but in sharp corners it results in intersecting meshes.

@@jacowaes you’re right - upon further experimentation I found that even if you’re using a standard curve object, two rectangles (for example) being in close proximity to one another causes issues with offsetting curves using this method. It’s quite a strange issue. I’m wondering if a workaround solution is to increase the spacing on a string, and then move the letters back together somehow later. I’m determined to get to the bottom of it lol I need to write out a lot of different words and shapes in neon style so I need a procedural approach

@@jacowaes okay I think I get what’s happening here - I sat and watched the dude’s explanation of how the offset node works. It takes each vertex - looks at the position of the next vertex (based on index) and uses that to kind of triangulate the direction in which the current vertex should be offset. With a text object (or even multiple curve islands in the same object), when you reach the last vertex of the island, the direction calculation for that vertex will be fucked up because it’s looking toward the next vertex which is part of a separate character - which explains the inconsistency because how weird it gets depends on where the next vertex is on the next letter / island. I’m not exactly sure what to do about it, but at least I think I know what the issue is now!

Hi! Yes, I was aware of this problem, but at the time, I wasn't sure there was a solution to it, and I would just use it on a single curve at a time. However I have actually found the solution in the last couple of days. This new node is much more complicated though. But now It should works flawlessly for multiple curves, or so it would seam at the moment. Unfortunatelly I'm away for work this whole week, and I m not able to test the node thoroughly. Sometimes next week I will probably be able to upload the updated node and everyone who purchased it will be notified.