Recent content by justinroth

Oh yeah that little overlooked window that should allow us to store positions to use as bookmarks? I've been doing the same.

Geez. It appears I need to go back and read the wiki again.

It looks great! Kinda bummed though as I started using Jr dk grey track years ago, moved on to a great looking pro track (it's Russian so I had to mod the gauge)that matches the Jr dk grey ballast perfectly and more importantly many assets I've made with the ballast texture (abutments, bridges...

I have to add the lack of a good signal scripting system.

I've been using 2.0 for a few days and gotta say in many ways it's amazing and time saving. The scrapbook feature is by far the most powerful aspect. Conversely, laying track is tedious. Not having a spline circle to help with gauge is a big inconvenience. Here's the thing, I've always used...

So I checked it and tried and it's giving me what seems to be a relative height value, which when applied becomes an absolute height value. Otherwise all I get is the ground height. Something just doesn't seem right. Am I supposed to do the math, manually enter the desired height and then apply...

I found the wiki. Ignore this I'm a dingus.

I can't seem to figure out how to grab a spline point height and apply it to other splines? I assume the dropper tool is used to grab the height but most of the time it seems to be grabbing ground height and not spline. Am I missing something or is it a bit more complicated than 1.0?

I use my own signals which at this point either use Grahamsea/Jon Roma script(which sadly doesn't work with EIT's past 2019 sp2) or an updated version of the RRsignal scripts. I never considered that the signals may be a factor, I guess I assumed that as long as the train was on top of multiple...

Just updated to 22 and thought this might have been an error in 2019. I use invisible speed limit objects in conjunction with trackside signs and quite often notice that Trainz will display an update in line speed before the train has passed through an interlocking/switch/ect. Could this be an...

Ok I figured it out. I should've known to check this. I went to each speedtree mesh library which were showing faulty and selected to view errors and warnings. I got some warnings but 0 errors. After doing this for every one they now show up correctly.

They are build 3.9 and 4.1

This route came from 2019 sp2

I don't know but I'm sure it's the start of issues.

I can't seem to find a solution. I updated to 2022+ and I have a good deal of faulty speed trees, mostly from mcguirel. I tried looking for asset versions as I know there aren't any updates. Any ideas?