never noticed either, I usually apply like 10 or so kN when starting and as it starts to move, I got into like 50% or so and then more
This may be connected to the AFB brake interlock; with it engaged you need X newtons of force (~ 40% power) for the brakes to disengage. Functioning properly, you get no tractive force until the throttle is above the threshhold. It could be that with this loco it improperly keeps trying to apply some power, then when the brakes resist it it shuts down again, back and forth.
AFB loco brake only needs 10kN tractive force to disengage. The OP is referring to the traction motors switching from 4 motors to 3/2 for efficiency, but it's switching back and forth every couple of seconds. This wasn't present in the original Railpool Vectron release, and has creeped in following the release of the DB and Flixtrain variants.
FLX1819 can't be started as it immediately fails the scenario for "signal passed at danger" on the BR101 Expert timetable, but is fine on the original.
Then it can't be anything to do with the traction motors switching. The Railpool Vectron and Flixtrain Vectron are identical in the Simugraph blueprint except for the Flixtrain Vectron having suspension enabled. Interestingly the DB Vectron is slightly different in Simugraph since I wasn't able to carry over all the changes I made to the Railpool Vectron Simugraph before I deep copied it for the Flixtrain. "All" doesn't mean a lot, it's just a fix to the traction motor eco switch off so that it doesn't initiate if you are using dynamic braking, and a fix to the ep brake transducer logic. This sounds more to me like suspension is wreaking havoc on the wheel slip protection, which was the issue that caused me to disable in on the BR 101 Expert until a core fix is implemented by DTG, and nothing to do with the traction motor eco mode function.
Scenario "Hanau Heart Rate Raiser": As usual with scenarios involving cab changes and coupling moves, there isn't enough God damn time allowed to do it. You can't keep to the schedule even using teleportation and keyboard shortcuts--- and since you're doing everything in a tearing rush, the odds are you will never notice that Cab 2 is inexplicably set to PZB Mode M (on an all-passenger line!)- which means that you will run yourself into a ZB as soon as you pass 120 km/h. Easiest solution: since this is an emergency rerouting scenario anyway, just remove the timings like on a freight route.
