Ty2 radio bug with cabin setting on splitter when changing driving directions

[jeroezie]

With the radio on the Ty2 steam engine their is a bug. If you change driving directions, by selecting a - or + position on the reverser, the radio splitter seems to be thinking that the driver has changed cabins. Thus the radio splitter will only provide power to the A or B cabin respectively, while their is only one, usually A but sometimes it can also B (maybe when starting the journey in reverse).

Workaround for any player encountering this problem: simply flip the cabin switch on the radio splitter, located in the overhead cabinet on the back wall of the steam locomotive.

[Admin BOT]

Thank you for reporting this issue! Internal ticket number: #4195
Dziękujemy za zgłoszenie tego problemu! Wewnętrzny numer zgłoszenia: #4195

[Stele]

Anything extra to trigger it? Reverser changes VehicleControllerBase.Direction in jumps 1/0/-1. Radio splitter checks VehicleControllerBase.cabinDir and it's 1 all the time in my tests.

Only suspicious line that could switch that value is (common for all vehicles) cabinDir = (int)vehicle.trainsetInfo.CabinDir * (int)vehicle.DirectionInTranset; which could mess if it's spawned in reverse in the first place.

That value can be checked in debug panel in outputs table. Output_General.data[(int)GENOUT.actual_cabin] = (int)trainset.CabinDir;

[jeroezie]

The bug is present in my Lazy to Katowicd cargo scenario. I dont know for sure out of my head, but I probaly do spawn ut reversed. I have only a light signal in the vack and I find them easy to referance compared ti findtrack. I could swap it of course for a track referance.

 

If you like to try see the bug in the scenario, you can find it here: https://steamcommunity.com/sharedfiles/filedetails/?id=3628486286&searchtext= or

 

Make sure to pick one of the first Ty2 loco's, the thirt option spawns the other way around (so you drive the cargo train tender first, which is kinda strange).

 

Personally I have the impression (but no facts to prove it at all) that spawning vshicels reversed can mess around with more things. Might you have any ideas/info on that?

 

 

Edited 20 hours ago by jeroezie

[Stele]

It broke shader on wagons when I tried to spawn reversed one to test for whatever (likely unrelated) reason. 😄

Sorry, I don't have setup to test scenarios. Somebody else will have to. Could you check that GENOUT value when bug happens? It's the only place in code that I found that could mess it up.

[jeroezie]

While standing with a single loco in the deport, I was unable to reproduce the bug. But it got interesting as soon as I coupled up the the wagons after shunting: when I got back in the cab after coupling, the radio green light was unlit, before getting out of the cab, it was lit up. Setting the reverser forwards or backwards had no effect on the radio light. Changing the radio signal splitter cabin from A to B got the radio working again.

I am unsure, what data vale, you are referring to. If you need more information from me, please describe it better. I will attach entire Vehicle I/O and log file, as after coupling, where the radio only works with the spiller on B cab.

 If I can help with gathering more info, please let me know, I am happy to help.

vehicle IO after coupling.txt SimRail_log_2026-01-28_18-26-48.txt

[jeroezie]

11 hours ago, Stele said:

It broke shader on wagons when I tried to spawn reversed one to test for whatever (likely unrelated) reason. 😄

Sorry, I don't have setup to test scenarios. Somebody else will have to. Could you check that GENOUT value when bug happens? It's the only place in code that I found that could mess it up.

Last time I attempted to spawn bot driven trains with reversed wagons, it was pretty fun too. Turn out, in bot driven trains, all wagons will go the 'pretend' forwards. But they don't seem to get the massage, they are flipped. So the train will pull itself apart because the wagons will move in opposite directions. But that was a longggggggg time ago.