Route Pfälzische Ludwigsbahn - Feedback Thread

I've explained this "neutral section" back in March: https://forums.dovetailgames.com/threads/pf%C3%A4lzische-ludwigsbahn-feedback-thread.88852/page-8#post-979564

 

Aaand of course I thought this service was cool to see, I spawn there at 7:50 and it's made of 101+DB IC wagons, and never moves, locking all other trains on nearby tracks too. Cool, DTG, another bug! Can't have one cool thing...

 

I just tried it on both timetables, it works if you spawn in at 7:45 on my end (PC/Steam).
Probably 7:50 is too tight for the dispatcher to calculate a valid path in time.

 

Thanks, great info. I do guess then this is the base issue that causes random gridlocks while playing timetabled services, what if I spawn in a service at 7:50 in Kaiserslautern bound for that platform....

 

The main traffic light's HUD is green,
but the traffic light itself has scattered red spots.

 

At this point I've lost all hope for the Feedback Forum, but anyway...

Ludwigshafen Mitte does have a closed canopy above the tracks, so it can't rain inside. And it doesnt. That's good.
What's not good is that if I'm inside a train in that station, I still can hear the rain sound on the train's roof.

Also, if I try to switch the PIS on the 425 to a different destination, upon pressing Enter some random location seems to be set instead of the one I wanted. And if it's a multi-part train, the rear part will always be set to "Nicht einsteigen" even if I'm setting the destination using the "ZUG VERB" (Zugverband) button.

 

Hello
I would be very happy if the flying objects at the level crossing signals between Hochspeyer and Frankenstein could be fixed.

 

Why do all the 425 destination boards say nicht einsteigen. Even my train says it i cant change i go into the lcd screen press the buttons but nothing happens. DTG Harry is this bug that you are aware off. Thanks.

 

It's a core bug introduced with the January update, the Dev's are aware of it. Countless threads already exist for it. Supposed to be fixed soon they say.

 

Thanks didn't realise it was already mentioned not played this route for a few months.

 

@dal#7945

This is not only the case on this route, but on all routes.
You can read about it here.

https://forums.dovetailgames.com/threads/pis-displays-not-working.96910/

 

So I've come to notice that at the Ludwigsbahn Route the museum at the station Neustadt Hbf is nowhere to be seen. I remember it being there at least before this DLC released. Has anybody got the same problem? I've tried reinstalling both this pack and Ludwigsbahn itself, no change. Too bad as this is one of the key features of Neustadt Hbf (and wasn't the E94 supposed to sit in the hall as well?). Anybody else?

 

The museum is unlocked via the mastery, you may need to re-enable the mastery tile if you've already unlocked it. I think it's just a static thing to look at, though. There's a screenshot in this review.

 

The museum itself should always be visible. The mastery only opens its doors and lets the players inside and take a gander through the empty museum.

 

Thats extremely weird. For me the whole museum is missing. Like there is no building at all there. Just invisible walls.

 

I just checked, and for me, the museum building is there:


A mod related problem perhaps?

 

Since I've got more mods than DLC I'll check it later once I'm home. If I ain't got that issue (haven't driven the route in quite some time), it's likely not mod-related and needs a ticket for DTG to investigate.

colinL what platform are you on anyway?

 

Sorry, TSW6 and Steam PC. I remember it being there when I purchased the Route in TSW5, but I only really switched to 6 a few weeks ago and didnt look at the route. I'll disable all my mods and check again (even though they got nothing to do with the route)

 

Just tested it with every german mod under the sun and many many more:


It's definitely there and open for business. So no mods in their current state can be interfering here.
On the other hand, if you should have an outdated mod, I can't rule out that for causing the issue.

 

Hmm. Perhaps verifying your game files in Steam might help? Right click on TSW6, go to properties and then Installed files. Might take a while though, and if something's really missing, it will re-download it

 

I‘ve tested it without mods as well, still not there lol. I‘ll verify the game files. Although I did go ahead and reinstall the route DLC and then the E94 Railtour pack via Steam. But maybe verifying will do the trick.

 

So verifying doesn't work either. What can I do?

 

I just noticed that both of the crossing monitoring signals between Frankenstein and Hochspeyer have an orange blob hanging over the tracks next to the respective signal. I haven't used the route in about a month or so but I'm pretty sure I haven't seen this ever before, must be new.
The blob is only visible when facing the front of the signal.




Just a couple of days ago I did a service along Niddertalbahn and didn't see it occur there.
Edit: Just double checked, it does not appear on other routes using this signal, like Niddertalbahn or Mittenwaldbahn.

 

Yes, it is new. The last updates fixed these signals (they weren't working and their PZB magnets copied function from next signal), but this appeared.

 

It's been fixed ages ago and the fix submitted for testing, according to Dion the route builder.

As usual, the solution lies somewhere in QA-limbo at DTG.

 

I just had to start service ICE 9555 Paris - Frankfurt (15:35 from K'lautern towards Mannheim) three times. The first two times triggered an instant SPAD.
Strange. I've had something similar on Stuttgart-Heilbronn recently - an instant SPAD the first time, then it worked.

Also, the supposedly fixed tunnel near Frankenstein is not fixed. There still is a bright segment in it.

 

As anyone done job S2 (38244) so right at the end you have to couple to another train but all is bounce off it i have tried everything without any luck. Any help would be good. Thanks

 

dal#7945 I just tried that service out of curiosity, same result. The two 425 just won't couple. Not sure what we are missing...

 

Appreciate you giving it ago i reckon there might be a bug.

 

Which is a shame, since it's a rather nice service overall... perfect on a clear or slightly cloudy summer evening, and it's one of the few which travel via Schifferstadt... I might give it another go this evening, and tinker with the 425 until I find a solution

 

Yes I done in the summer months its very relaxing drive if you do manage to complete it please do let us know.

 

GAG 49255 (two services) has some issues:

• The description of part 1 instructs you to drive to Mannheim Hbf, while it terminates at Hochspeyer (minor issue).
• Part 2 has several issues:
  • It starts with a wait instruction (which is reasonable), followed by another wait instruction that is in fact a hidden "go to" instruction to Neustadt an der Weinstraße. It clears as you approach Neustadt. A player that follows the "wait" instruction will however never clear this instruction, thus being unable to finish the service.
  • A little further, at the branch off towards Schifferstadt, you encounter a Ks 2 signal, which should be a Ks 1, as the next Hs is more than 3 km's away and has its own vorSignal about 1 km in front of it.
  • When arriving at Mannheim, the station is fully locked up with one train stopped off path and several other trains in a lock up because of that. I had to remove 3 trains to get the traffic running again. Luckily the path towards the player destination is clear of traffic.
  • After arriving at Mannheim, I had to wait 13 minutes for the service to finish, as there was a STC attached to the stop instruction.

Edit: this was all on the Expert timetable.

 

dal#7945 I just did the S2 (38244) service again, to check out the coupling issues.
Before starting, i did some coupling tests with the Rhein-Neckar 425 at Mannheim yard, which worked fine and without any issue.
Did the service then, but once again, no luck. The two 425 just won't couple. I was under the impression that the other 425 might not be set up properly, so I went over there and basically reset everything, but still no luck. Seems to be a broken service after all

Oh, for the troubleshooters: I did the service on the Expert 101 timetable

 

Had a service on the normal timetable with the 628, after the last update. RB-38925 seems to be the service number based on the DTL Logbook. Faced a few intresting operations to say the least.

When entering Neustadt A.d.W I was facing a single Red aspect, yet the route monitor shows green. The distant was correctly displaying yellow for the red aspect. This should have probably been a shunting permitted at least, since the actual red on the track monitor was at the end of the platform. Had to pass it with Befehl 40, which wouldnt be a problem had the dispatcher told me so and not that "Proceed as signals indicate" when the visual of the signal is "Stop" for all movements.

No other events until arriving in Schifferstadt. There was no indication of Red when entering the platform yet I was hit with an emergency brake for 500Hz. Then on the platform there seem to be quite a few magnets, and each of them triggered further 500Hz stops, even though the exist was a permitting aspect.

I can probably conclude that since its a layered on service, not core rolling stock, and a pretty long and slow one it might not have been tested end to end as part of QA if tested at all.

I had the same happen to me in Stuttgart as well in the past, but that was a shunting movement to the depot where it might be running against shuting only with active magnets.

 

I believe this has to do with the Zd signal (Zugdeckungssignal) on Platform 4 (which is towards the end of the platform but not at the end). IRL the entry signal would indicate an entry with a reduced speed (like 20Kph, but I dint know the real numbers), which the signal in game can not display. Also, if I remember correctly, DTG has actually programmed a shunting asect for this situation, which is 1) incorrect anyway (you would not enter a station on a shunting aspect) and 2) can not be siplayed by the signal in game either, hence it simply stays red.

 

xbox x (br145expert)...

 

Yeah so the workaround for something that was not supported by their system is still a setup that is not supported, and borderline against the rules in real life. I much rather would have them deviate from the IRL signalling setup but portray only situations which are safe on a real railway, which passing a red or giving shunting movement authority of an active passenger service both are not. And then you wonder why the legal buffs at SBB or MTA had issues with how DTG does their due dilligence, and either revoked the license or forced them to not portray things that would put real life railways in bigger danger from inconsiderate humans.

Overall I dont really have hopes for it getting changed then

 

Yeah... sadly this route is somewhat known for its sketchy signalling. Numerous issues have been posted here already, but haven't been blessed with a fix so far. The areas of Kaiserslautern and Neustadt are particular hotspots

There's another similar issue with the service S2 (38244) which I tried the last two days. You have to couple with another 425 at Kaiserslautern, so the entrance signal is red on approach at first. When calling the dispatcher, they tell you to proceed at reduced speed. But the entrance signal is unable to display any shunting aspect, so you have to pass it while red using Befehl 40.
IIRC this has already been reported too... months ago.

 

Thing is that the infrastructure they have in game would be perfectly set up for this situation, as a Zs3 is actually installed. Only thing would have been to programme this accordingly and make it display a "2" if the route ends in front of the Zd. I am assuming that this routing was simply not envisioned at the time the route was build and as the signaller always falls back to shunting aspects if it doesnt know what to do this is the logical consequence.

But I agree, will probably not be fixed...

 

Someone from DTG needs to take a shovel and dig out this buried signal.

 

These buildings in the depot are too big. On the other hand, the depot next door is too small.