Rather strange problem, I can't drive the BR612, because by activating the PZB most of the controls stop working, even the light in the cab! I tried re-downloading the dlc but it didn't work. What the hell could it be? Thanks in advance.
Did you follow all the start up instructions first? I have been caught out in the past with RSSLO trains.
The Pegnitztalbahn BR 612 is a complete new build by DTG und not the RSSLO one. Never had the problem with lights not working after switching PZB on. So I can´t say anything about that.
Is there a battery isolation function on this BR 612? I don't know because I don't own the DLC but it seems like maybe there's a keybind issue that the PZB and the battery isolation are mapped to the same key, just something else to eliminate if not.
I can rule out a problem with the download. I tried installing the dlc on a second clean install of TSC core and this time everything works perfectly. It is clear that in the daily use installation of TSC, full of contents, some conflict is evidently created with I don't know what. For the record I also have a backup of my entire installation but at the previous version of the game (73.3B) and the problem occurs here too. I could do a check of the game files, but it's something I hate doing because it resets certain changes I made to the contents (the AP skies, certain sounds, etc...). However, I don't think it's a problem of this type, it's more likely to be some conflict with some installed content. But what can undermine the execution of the scripts of a rolling stock? I do not know where to begin.
Is it worth a clean reinstall of the unit? Just deleting it via Steam DLC list doesn't fully delete the file. Go into the Railworks Assets folder and delete it from there too. I had a weird problem with Class 319s crashing my sim a while back and after much trial and error realised that even as AI it would cause a CTD, only a clean re-installation of all Class 319 DLC and the routes that came with it sorted my issue out.
Yes but to check for conflicts you should untick from the main install, Go to the folder delete any remaining files and then reinstall. Just to make sure nothing is overriding the .ap file
Sounds like a script problem. Have you used logmate before? If not, try to use this in the startup settings: Code: -LogMate -SetLogFilters="All" -lua-debug-messages and check the log for errors, or post it here. Try to run it in a scenario with no other trains.
Fact: The 612 works out of the box. The route is self-contained so nothing can interfere except repaints installed to DTG\Pegnitztalbahn\ or additional files in DTG\PegnitztalbahnSignals\ Make sure that first folder only contains PegnitztalbahnAssets.ap. Don't listen to anyone telling you to unpack .ap files - you'll become a regular advice seeker else. Make sure "Dynamic Lights" are ticked in the Game Graphics settings.
Thanks for reminding me, must tweak the overbright headlights (Camera position already improved, also cleaned the dirty windows) Lights fixed. Lensflares removed and intensity lowered. We're not using high beams in Germany as we'd blind everyone around us. This is not the US desert atomicdanny Pegnitztalbahn is a great route, and it's a pretty solid DLC. Vegetation assets don't need any AP enhancement (no more "balloon" trees). Just looks good and is a smooth experience. It's obvious it was done by very experienced route builders. Credit where credit is due
All conditions are met but the BR612 still does not work. I also tried it on the test track, it behaves exactly the same way: by activating the pzb, all the other commands stop working. Yesterday I also checked the integrity of the game files, but it didn't solve the problem. On a minimal installation of TSC, everything works perfectly. It's going to drive you crazy.
Be more specific - do the stock scenarios work, is it only on TestTrak (or Academy, not sure what you meant)? Is other stock involved on the scenarios you are playing?
BR612 doesn't work in stock scenarios and on the old Test Track from the Railworks era, where there is not AI traffic.
You must tell us what exactly you were playing when this log was generated, there is lots of references to RSC, VirtualRailroads and AP_Waggonz, doesn't look like a stock scenario - and if so, it (or the route) has been modified (by adding dependencies/preloads to RouteProperties.xml) For moving on, let's concentrate on a given scenario. Play the first 612 Career scenario "[01] RE30..." and post the log.
I guarantee you that the log was recorded playing the first scenario, the one you mention. Everything is in stock condition, no modifications except for the AP skies, which however DO NOT AFFECT the functioning of the rolling stock. The BR612 does not work regardless of the presence or absence of AP skies.
This is the log generated by the minimal TSC installation where the BR612 works perfectly. https://www.dropbox.com/scl/fi/50l7...R612.log?rlkey=5wkb3oklfsr4sz0bb1f4f15fh&dl=0
The following errors will for sure cause trouble. 165 = Unable to execute non-function: OnControlValueChange 165 = Unable to execute non-function: Initialise But I'm not sure what train is causing this. It is best to try BR612 alone with no other trains, like 749006 mentioned, in a Quick Drive.
All we know is that there's something different between the clean installation and your main installation. What that is, only you can tell... It should not open the RSC\BR189 or AP_Waggonz Class90 or vR stuff which your first log shows. Have you made edits to the route? Have you activated providers in World- instead of Scenario editor? In a freeroam, placing multiple different vR locos can lead to scripts stopping working for example.
Very trivially, but isn't all that material you say present in the log due to a previous session? I'm asking because I'm not familiar with the tool that generates logs, maybe I used it incorrectly. I reiterate that this is a stock scenario on a stock route, without added rolling stock, as DTG mother created. The only exception is the AP skies, but those are irrelevant. And, no, I haven't full control of what's in my full installation. There are 170GB of material accumulated over years and years, at a certain point you lose control a bit.
Well, after quite a few experiments, I finally isolated the problem: if I remove the BR442 (Talent 2) from the \Assets\DTG\ folder, the issue is solved. The problem is that I don't want to throw the BR442 in the bin!
I wonder if there is something in the engine.bin (might be something else .bin) that references the BR442 because DTG did a lazy copy and paste with the simulation files?
They couldn't have done this. The BR442 is a DLC, so its presence in the game is anything but obvious.
Open TgPcDx in RSBinTool, export DDS, lower Alpha opacity with your preferred image processor, reimport, save.
I don't know what the hell is behind it, but in my case it is precisely the "BR442Pack01" folder that inhibits the functioning of the 612. And you can't even say that it's a problem resulting from my overweight, DLC-filled installation. Even in my minimalist installation, where I only installed the "Pegnitztalbahn", I just need to copy the Talent 2 folder to make the Pzb of the DB612 unusable.
Use the wiper Would need to check how AP does this first. If it's a single texture, making it fully transparent would be the easiest thing. Or disable the "bug" code in the c37-wipers.lua script, it's not compiled fortunately. I really like that feature. Edit: look for flies.TgPcDx in \CommonResources\CabViews\...\Textures and make it transparent
