ApproachMedium
Youtube dude
Has anyone been able to get TRC triggers/crossings to work in Trainz 2022 (123794) at all?
I've been trying to get them configured on my P&B route but there is utter inconsistency with any of the configurations saving. I can get a few crossings named and configured on the route layer, the triggers will see each other, the gates and stoppers, I'll save and exit and upon returning none of the triggers see anything. Then if I open a base session, I'll find some of the triggers are seeing all the things but others are not. If I leave and return again, a different set that weren't working are suddenly working again and the previous ones that were working suddenly have lost their configuration.
My hunch is that it has something to do with unified Driver/Surveyor and perhaps the game isn't sure where to save the configured info, ie session layer or route layer? It's just wildly inconsistent. As soon as I feel like I have it working and figured out, a different set of crossings breaks.
So I'm just curious if anyone else is having this issue and have you found a fix? Because I'm about to lose my mind here lol.
-Joe
I've been trying to get them configured on my P&B route but there is utter inconsistency with any of the configurations saving. I can get a few crossings named and configured on the route layer, the triggers will see each other, the gates and stoppers, I'll save and exit and upon returning none of the triggers see anything. Then if I open a base session, I'll find some of the triggers are seeing all the things but others are not. If I leave and return again, a different set that weren't working are suddenly working again and the previous ones that were working suddenly have lost their configuration.
My hunch is that it has something to do with unified Driver/Surveyor and perhaps the game isn't sure where to save the configured info, ie session layer or route layer? It's just wildly inconsistent. As soon as I feel like I have it working and figured out, a different set of crossings breaks.
So I'm just curious if anyone else is having this issue and have you found a fix? Because I'm about to lose my mind here lol.
-Joe
Anyway, I went through the process of replacing all the broken ATLS crossings, and had the new crossings all programmed and working properly. Then one day I loaded S20 as usual and in the corner of the screen it started displaying “Script Failure <kuid:xxxxxx,” (I did check if it was vincentrh’s kuid and it was) over and over at random times while I was editing. I got concerned that the crossings broke, but I tested multiple in Driver and they worked perfectly. Every time I load into S20 it gives me the same message, but I am not sure what could exactly be affected. Interestingly, if I edit the route in Surveyor Classic, it never gives me any errors. I need to double-check the kuid in the error message because I don’t know if it is for the crossings or the triggers.