PZB Train Type

[Tomisnic]

Is there a way of changing the train type for the PZB system in locos like the BR 189 and BR 145? The BR 101 selects the correct train type based on what category of freight (55 or 70) or passenger (85) you choose in the scenario editor but for these two locos, that choice seems to have no effect...they default to 85 regardless. So is there another way of making the PZB system work properly or is this yet another bug? Both these locos are cargo locos so having the PZB stuck on 85 kind of ruins them.

[Lt.Smash]

I asked the same question myself a few days ago. It looks like you cannot change the PZB train type. The same for the ME146, BR146.0 and BR146.2. In the BR146.2 you even cannot turn on the SIFA!
The low quality of the newer locos is very disappointing. I hope the new BR185 will do better, but I doubt it.

[Tomisnic]

It seems like Dovetail has made an absolute mess of the German content. Just about everything they release is somehow broken or not quite functioning correctly. Between these two and the 442 Talent which has major issues, I’ve spent $60 on content which I can’t really use. It’s very disappointing and I feel cheated.

[Tomisnic]

Regarding the 146.2, I think you can turn SIFA on but there is no audio warning so if you are looking ahead at signals and miss the SIFA light, you are screwed. On this loco, they even managed to get the sun shades wrong...the one on the driver side is pulled almost all the way down while the one on the other side is much higher up. They got it right on the Metronom (identical loco) but for some reason on the DB version they messed everything up…just pathetic laziness imo.

[Lt.Smash]

Yes. I can not understand how you can miss features that were in the game back then. The BR101 had all you need and it all worked fine. What is the problem to implement these features in the newer locos? Oh right ... less time you spend to develop = more locos you can develop = more money.

[Lt.Smash]

Okay so despite my concerns i bought the BR185.5 and I have to say it is actually pretty good. I haven´t found any major issues and the PZB works better than ever. You can choose the train type within the scenarios and even the emergency brake applies if you are speeding. And finally you can choose yourself which pantograph is up. I hope DTG will keep this quality this time.

But anyway some fixes for the other rolling stock would be nice. As you said the most of them is kind of useless.

[skinnyraf]

Now I hope they would backport the new and nice PZB code to previous locos.

[nolanblew]

I know this is an old topic but...
After hours of trying to figure out how to change the PZB value (one of the DEFAULT SCENARIOS assigned a freight PZB to a passenger train making it near impossible to make the schedule) - I played around with some scripting of the scenario and such and finally came across how to fix it.

Note: This is only for those who know what you're doing. I recommend making a backup of EVERY file you edit first, just to be safe. Also, this assumes you are using Windows and has some Windows-Specific commands. A quick Google search should show you how to do the same on a Mac.


1) Go into the editor mode, and find the scenario you want to edit. Then click "edit" (you can clone it if it makes you feel better).
2) In the editor, click on the TimeTable icon to bring up the popup window (The top-left slideout panel, and the icon is on the bottom left - the one that looks like a pie chart)
3) Click on the blue "Scripts" icon in the window (The second-to-last icon on the top -- it looks like a blue square with a gray rectangle inside it)
4) Click "Open Folder"
5) In your explorer, right click on the file that says "ScenarioScript.lua" (if you don't see the .lua, look for the description that says "LUA FILE" -- NOT LUAC or MD5), click on Open With... (or if that's not available, just click on "open"), and select a file editor. I use Notepad++, but if you don't want to download that you can just use Notepad
6) Search (Ctrl+F) for "PZB". Find a line that looks like this:

function TestConditionPZBSIFA()

7) Below this line, you should see something that looks like:

        if PZBState ~= 2 then
		SysCall ( "PlayerEngine:SetControlValue", "PZB", 0, 2);
		SysCall ( "PlayerEngine:SetControlTargetValue", "PZB", 0, 2);
		--Print("PZB should be changed to 2")
	end

8) Change all the 2's to:
1 -- For type O
2 -- For type M
3 -- For type U
0 -- For Off (no PZB)

9) Save the file. Most likely it will be read-only, so save it on to your desktop. Then take your desktop file and Cut & Paste it to the folder that TS opened for you. It might ask you for admin permissions, so say "yes".

10) Go back to TS, and click "Reload". Then, click on "Compile/Generate MD5"

There you go! You don't even have to save the scenario. It's a bit of work, but it's totally worth it if the PZB is annoying you.

[nolanblew]

Also for those of you who don't want to mess with the code or scripting too much, I wrote a quick program that should fix the problem. Read the README.txt file that it comes with to see the instructions. Basically it just manages all scenarios that have PZB enabled and allows you to edit them (along with sifa). It does so by doing exactly what I described above!

You can download the tool I wrote here:
https://stratsofttech.blob.core.windows.net/public/TS PZB Editor 1.0.1.zip

Also I don't think this follows under the limitations of cracking or hacking, as we are simply modifying a line in a script to fix something that is broken with the game.