Does anyone know how you use the HRR version of the BR 422 instead of the RRO version? Whenever I enter timetable mode it always puts me in the RRO version with the incorrect destinations.
So how does the 422 on HRR have the updated PIS display with all the new destinations? And it doesn't look like a flat texture on any AI trains, it looks more like the one on the 425.
The current destination displays being implemented everywhere are like a Version 3. The 422 has a Version 2 display, with the destinations pre-programmed in but they are also not textures, which is why when the substitution system gets them mixed up you get the wrong destinations. If it was the newer displays, they would not get mixed up as they get the destinations automatically from the route. The first version of displays used actual textures for the destinations, but that’s ancient history now.
I think they are the original RRO and HRR versions, neither of them updated as such. The AI has the correct one and you have the other because of the game’s substitution system mixing them up or some other technical reason. That’s why they look different, it’s just the wrong model of 422 given to you by the game. The design of the destination board is just different on the two models from when they were originally made. I think you are talking of ‘updated’ as meaning the correct HRR version while we’ve been thinking ‘updated’ meaning the new smart system for taking the destinations from the route, which is a new system that came long after both RRO and HRR were made, as they were TSW2020 routes, so we’ve been talking at crossed purposes. In TSW2020 you got the right one for the route, it’s only in TSW2 that the two trains got mixed up. I think they are actually mixed consists, with only the driving cab being incorrect when you drive a train. You might find the rear cab of your train has the correct destinations. It’s an odd bug that has been there since the two routes were brought into TSW2.
This is a longstanding problem: the game mixes up the RRO and HRR 422s. Sometimes even in the same train! (hence double pantographs, or, for me for a while, piebald red-and-green trains). It is akin I suspect to the bug, now fixed, where the game mixed up the ECW and GWE Class 66's.
TrainSim-Adam DTG JD Again I need to mentioned both of you, because you never listen to this Bug. It’s every time on any Timetable schedule with the Wrong Train from the HRR 422.
You can get around this problem by spawning on foot at the relevant time, and picking up the train from there. For whatever reason, AI trains always have the correct destination boards.
Hiya, Its not that we don't listen, the Preservation Crew simply haven't reached those routes yet to start looking. If the issue has been logged in Kayako, it will be on our radar. I've also made a note of this thread.
Why can this not fixed from the Main Team like before? It’s just 1 Bug with the 422 Train on the Rhein Ruhr Osten and Köln-Aachen Timetable.
It's not a big enough issue. You can still operate the train without the correct destinations. The main team will be focusing on new content and possibly critical issues that come up. Eventually this bug will be squashed (I hope).
Everyone has one bug they want fixed. So whose gets fixed first? Each route is getting its turn under the microscope where the Preservation Crew will look into reports and feedback.
Of course it would be really nice if there weren't so many bugs appearing, as there seems to be at present. Then more time could be spent on the modules and testing them.
I prefer long QA and no bugs, fixing bugs takes longer than good Q&A Actually from a programming perspective bugs are sloppy & poor programming or that multiple programmers are doing it "Their Way", then bugs appear when you bolt the thing together. I speak from experience. Don't get me wrong I really do enjoy TSW and enjoy all the new stuff coming along in the pipe line. The guys at the coal face are the guys who get us moaning about the bugs. Management needs to allow appropriate time to do good testing on the multiple platforms. Actually UAT is paramount as programmers and even testers, will do a work around in their head with out knowing it. UAT where someone will do a really unthought of press of buttons is the way to find those pesky bugs. You then hopefully put out a program that gets everyone saying how good it is and not moaning about bugs.