Haha, a couple of obvious reasons spring to mind: #1 I don't release on anything like a schedule, with seriously erratic release timing. #2 I don't use ~2-4 second transitions/popups/sounds to keep your lizard brain activated, or plaster my Mr Beast face all over my thumbnails. #3 I don't really 'SEO optimise' my content with clickbait titles or try to release what people necessarily want to see. For example if I really wanted subs, I'd do a 40 part tutorial series. #4 I'm not actively chasing collabs and cross traffic with other channels. In short, my own conscious disregard of the current KZbin meta lol

Glad it helped!

I don't really dabble with 2D, but does the Line2D node not cover most of it? Otherwise you'd probably want to spring your own mesh by iterating each point pair and calculating the perpendicular vector to determine width and assigning UVs accordingly.

I didn't realise Triplanar mapping wasn't used in 'real games'.

Just iterate the defined path and raycast down for each position to find ground position, store these as a new path and replace the old one with it when finished

You would need to build the GUI interface for the user to interact with, which then interfaces with the Path3D node under the hood. This is by definition unique to your implementation, but any GUI tutorials will help get you started.

@@BeauSeymour thank you now i know where to start

Thanks 😊

Thanks! I really should redo this in Godot 4 hey!

Where it says 'top orthogonal' in the top left of the window is a button with several drop down options for different views. Alternatively clicking the 'Y' of the gizmo in the top right does the same.

@@BeauSeymour thanks for replyin! appreciate dat

The video is the inspiration 😅

If you pause at 2:58 you will see in the top right that the four points on screen that represent the road shape are 2D coordinates. (0.0,0.0) -> (0.0,0.1) -> (0.1,0.1) -> (0.1,0.0). This is a closed loop, so the last link to (0.0,0.0) is implied. The Y component defines the height of the road mesh, the X component the width of the road. I just copy this csgmesh that represents the road and tweak at 3:02 to make the 'curb' segments for the left-hand side. All I am doing is making the points start at (0.0,0.0) but then move left of it (negative on the X axis) and slightly higher than the road on the Y axis. The right-hand side is the same again, but I am moving the points further right of 0.1 on the X axis, and the same amount higher on the Y axis as before. Hopefully that helps but let me know how you go!

@@BeauSeymour Excellent, thank you very much!

I'm not sure I ran into any issues, but I think I used to Jolt Physics addon at the time. Give it a try and let us know how you go?

I'm not sure what the 'correct' method is, but suspect the only reasonable way to handle intersections is to precreate them as models, then snap the road curve to them at defined entry/exit points. Anything else I can think up just breaks the moment you try to automate texturing it :S Maybe some I'll have to investigate in a later video but caught up with another project ATM ^^

Glad you liked it ^^. It certainly was my default for a while but for reasons unknown I don't use it anymore (but should!)

Cool! Yeah I suspected the people reviewing the scans would be able to see it in 3D :D

@@BeauSeymour if you get the right tech they'll take you into the office and show you the 3d (but maybe that's just an america moment)

3 times over, but tbf It'd been a year since my last one. Also I may be predisposed to blood clots apparantly :S (getting tested for it atm)

@@BeauSeymour prob the vaxx itself tbh

The place I went to send them to you through an app, so didn't have to ask!

Nah I bashed this out in ~2 hours so I didn't really deviate at all from what's shown which is just an absurd point mesh approach.

Oh man revisiting this would be the horrors, this was Godot 3 so I'd need to port it up and remind myself of all the ways it sucked. One day I should, but I'll make a video about it if I do!

Thanks ^^