When I was recreating the Riverview Bobs the generators??? lack of precision was incredibly vexing. For example, I discovered that two successive curved sections of 90 degrees did not result in the same length and total angle of curvature than a single arc of 180 degrees, and every single one of my single arc curves were off anyway, such as the horseshoe curve following the lift which is exactly 250 degrees on the blueprint but had to be rendered at 254 degrees to get the same result in NL2. There???s a total of 16 curves in the ride and it was maddening having to experiment with every single one to find the right ???fake??? values. Then I had to do the same thing with node spacing on the curves. Then, on the straight sections, I discovered that only the first and last few nodes were spaced at the values I???d set ??? all the rest were off by some fraction of a decimal point, meaning that I had to go and re-space all the nodes by hand. This doesn???t matter so much when you???re building rides from your imagination but it???s absolutely critical to be precise when recreating a ride from blueprints. I could have saved myself several days of time if only the generators did what they were supposed to. Does anyone know which language the generators are written in? I???m really tempted to put it into my long-term plans to create a better track generator which doesn???t have these problems.
Welcome back, not seen you in a while! I'm curious how inherant the problem is with the way NL2 forms the track or if that isn't a factor at all! I've messaged the NL2 team so hopefully someone will drop by with some insight