Br 146.2 Braking Bugs On Ps5 Kinzigtal

I have a tsw2 + journeys and a free TSW5 under Epic Games on PC with no 146.2 because it is built to be ready to test the new Köln timetable and the new GWR before touching my PC Steam or PS5 ( i hope. ) and to be as free of quirks as possible while including as many lok on layers as i can for both ... but without purchase of 182, 187, 155 and 204 ... and definitely no Main Spessart with the 146.2 and no PS5 Deluxe or Standard install. And that TSW5 loads FAST ! I did purchase the old 101 just for testing Köln Aachen.

( loading tsw5 on PS5 gives me time to make a pour-over coffee from scratch with roasted beans ... )

On PS5 i think a scenario tester should have the habit of first reducing speed with e-brake before bringing in train brake and in station on Main-Spessart Bahn with sufficient gradient, to habitually add direct brake as a roll-back safety in order to see the 146.2 brakes misbehave. Some users may never do these 2 things leaving us comparing apples to oranges. And there may be more variables closer to charging and releasing brakes that i leave to DTG.

It may not be enough to trigger the bugs with use of AFB + PZB alone or to have changed ends. I know these bugs as cab 1 but not whether cab 2 is worse.

If only TSG would offer a 146 replacement !

 

Without PZB and running late on MSB by not using AFB, BR 146.2 seems innocent enough if you never apply full train brake let alone Emerg and of course never have emerg brakes applied by train systems.
Maybe 146 was tested gingerly ...
I have the ( bad ? ) habit of cutting throttle and using light braking with e-brake rather than more brutal AFB speed reduction when i don't think i need it and the line speed is not reduced before or after the station stop. So i stop and then climb up to AFB setting.
Others may say you should drive using the AFB for your approach braking ... this is after all my hobby, not my former day job.

 

Starting out in station at MSB Aschaffenenbrg in 146 on a gradient, there are no brakes applied, so out of habit i apply the lok brake as the parking brake is off already. I add AFB and the brakes leap up then down on the gauge. Why ? This train has not yet moved. I have not yet touched the train brakes.
Maybe i should have applied full train brakes, but this 146 does not require that.
A symptom, a bug or both or nothing ?

 

OK, on this PS5, same MSB timetable psgr service, 3 restarts, 3 different brake gauge behaviors upon engaging AFB ... depending on Reverser neutral or forward? Doors opening ?. Once the train was rolling on the gradient ( why only once ? ) so MSB needs a re-work, not just this 146.
I don't think my instinct to engage the direct brake is the problem here ... it might be MY problem, but it is not THIS problem.

 

If you look back quickly, you can see the parking brake come off ... but this is a timetabled service, not a scripted scenario ! I look back to change the setting for my lights. So far i have not set a brake let alone tested a brake, but we are on a gradient ... with no brakes in a station with a message to open the doors.

 

anecdotal: i have run some MSB 146.2 passenger enjoyably now by never turning on PZB but instead concentrating on speed and braking for station stops and a few of the timetable services are actually enjoyable and challenging on the Spessart gradient, especially red signals on steep gradients.
I may reconsider adding MSB to my light-weight Epic Games free TSW5 ... but i hate being unable to use PZB and LZB in 160 kph lok on an HS route ...

 

AFB, on the 146 like all reasonably modern DB locos/MUs, is designed to automatically apply a small amount of brake whenever the train is stopped- this is intended to hold the train where there is a gradient. Applying power of ~40kN causes the system to release them.