I just found one, service SE 28166 from Stuttgart to Bietigheim-Bissingen, and tested it. It consists of a Wittenberger cab, 4 Dostos and a 111. And I can confirm that neither the OHLE voltage meter nor the Oberstrom meter nor the traction indicator seem to work in the Wittenberger cab, when coupled with Dostos. I ran back to the loco to check if it was set to ZWS (it was), and there the OHLE voltage meter showed the correct value. Very peculiar...
In the announcement for the Stuttgart-Heilbronn update (2nd april) they called: "Removed platform numbers from Tief platforms 101/102 (not used IRL)." Perhaps I understand something not correct, but this will mean there should be nor more signs with number 101/102 at the platforms? Because I arrived today with a 423 service at Stuttgart Tief, and there was the 101/102 platform numbers. And the update seems downloaded. At the end, for me personally this doesnt matter. But I am wondering
Thanks! Yeah it was exactly like this. So it might actually be the mixed consists with wiko and Dostos.
Since the last update I get this error on every TimeTable-Service with and without active mods: LoginId:b44862714ec58decf3db7c9688d8ffcc EpicAccountId: LowLevelFatalError [File:Unknown] [Line: 3194] Could not find SuperStruct OnDoorStateChanged (PassengerDoor_FL) to create OnDoorStateChanged (PassengerDoor_FL) TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld TrainSimWorld kernel32 ntdll
After the update A run from Heilbronn to Stuttgart in the br 111 I had no blurry textures on playstation 5. The fix for blurry textures has worked and a full s bahn timetable working. Fps does drop at Stuttgart but it's the only area that does.
I didn't have the silver luck, but I did it about five times, and even though I didn't have all the layers active, the texture blurring still shows up on PS5 Pro, texture optimization alone for Wiko will definitely not be enough, I think that mainly BR101 + IC wagon and Dostos will need optimization........ By the way, since TSW6 there is a problem with the interior lighting and sometimes even with the tauillights for IC wagon to BR101
Hmm since the new update I have returned to the route and have some observations: - BR 423 - The door for first class is not interactable, and the player character can go through the glass. - BR 423 - Only noticed because of doing back to back services. The audio announcement played for a depot move from the storage track to Bietigheim station. Then on the S5 service the audio for next upcoming station played as soon as the service started, not when departing. - BR 423 - Continuing after playing an S4 service from Suttgart to Ludwigsburg, when taking over the incoming S4 train it already had Sifa and PZB on. It must have recycled a train I had played before in the same session. - Wittenberger Cab - As mentioned above the traction/brake indication is not working when the formation is 111-Dosto-Wittenberger. Only found one service Bietigheim -> Frankfurt (RB 19874) - 101 service had me spawn at a random platform and had to teleport and take the train over in game. (IC-619) - When doing the autozug runs and spawining in for AE-1350-Part 2 in Kornwestheim, the shunting service for the car carriers is stuck with the loco off path over a switch. Manually playing the shunting service it is fine. This feels like an issue how the position is calculated on spawn versus the objective position. - Substitution - so far have not seen a grey N-wagen, so the chance is really low its more of a special thing than a regular occurence. 628 services are Mint one way, Red the other way, a mix would have been nice, or just allowing to sub if possible. The n-wagen cabcar I have never seen being subbed in with the Karlsruher Kopf, neither Red or Mint.
In my opinion the DBBR 110 should also take some services, since they were far more present in year 2000 Stuttgart, than just doing the car services. That would be the cherry to the cake. Kind regards.
Where exactly does this happen? And which services are you running? I wanted to do some stuff on the route anyways this evening, might as well check it out
Hi mate its on both timetables mainly the 2018 one tho. Any passenger job or depot move. And it pzb stops me anywhere along the platform a few times. Let me how you get on. Thanks
mmm ok I can't be of much help then. I don't have the BR 147 and the 2018 timetable, and after looking at that one's feedback forum, I don't intend to get it anytime soon... sorry!
Funny you're saying that, I'm just doing my first night service on the Stuttgart 423 The Stuttgart 423 has lightbulbs instead of the LED lights the other 423 have, so naturally it's a bit dimmer. But I agree, it feels a little bit too dim especially on full beam setting. Edit: I retract that, full beam (Fernlicht) looks fine, but the normal setting is rather dim.
Because Stuttgart is the "oldest" route using the 423, being set in 2000. Back then, the 423 simply had lightbulb lights They were changed to LED lights gradually during overhauls and refurbishments, about 10-15 years later. Honestly, I'm glad and a bit surprised to see this little detail being taken into account, when making the Stuttgart version.
Hello! Sadly, since buying the 147 loading into this routes timetable only leads to a CTD. The new timetable worked fine before buying the 147. I always get this error now: LowLevelFatalError [File:Unknown] [Line: 3194] Could not find SuperStruct BndEvt__RailVehiclePhysicsComponent_K2Node_ComponentBoundEvent_29_PresetConfigurationInitializationSignature__DelegateSignature to create BndEvt__RailVehiclePhysicsComponent_K2Node_ComponentBoundEvent_29_PresetConfigurationInitializationSignature__DelegateSignature
There are quite a few 500 Hz magnets along the platforms and in the yard when you approach a platform. This is a real-life security measure because Stuttgart only has bay platforms, and it prevents you coming into the bays "too hot". The 500 Hz magnets enforce a strict 24 km/h speed limit (the HUD shows 30, but PZB enforces 24 km/h shortly after passing a 500 Hz magnet). If you exceed that 24 km/h, the train will be halted. In real life, the speed limit is 20 km/h after the 500 Hz lights up on the dash, the extra 4 km/h is leeway.
But the 24 km/h would only apply if you are in restrictive mode, right? When entering a platform, you (probably) wouldn't be restricted and would be limited to 45 km/h (in mode O for passenger services). Just curious how this is set up in real life -- I don't see a case like this listed on the wikipedia articles for PZB or GPA - the GPA article mentioned the 40/45 km/h case. Of course, if you already violated the first 500hz's 65 -> 45 km/h breaking curve, and were emergency braked, then you'd be in restrictive, so the _next_ 500hz would be active from 25 km/h - maybe that's what happened.
Yea I'd like to second this question. Last night I was running the 147 into Stuttgart - went past a signal at Halt Erwarten so 1000Hz, saw the 30km/h limit on the HUD (but no signage, typical DTG), so was doing 30km/h. Hit the 500Hz magnet and seemed to get an immediate emergency brake. It didn't make sense because I wasn't in restrictive mode, so should be allowed anywhere up to 45km/h.
Yea I'm aware of that rule too. I got another emergency brake into Stuttgart again yesterday. I'll try again today and see if I can work out exactly what's going wrong.
Stuttgart is really putting my RTX 4060 through its paces; I’m getting 17 FPS at best, but sometimes it drops to 10 FPS. It’s simply unplayable. I don’t think it has anything to do with the new BR147 I’ve been playing, because throughout the whole thing my FPS was locked at 30, which I’ve adjusted to 60 using LS with JetWash’s .INI . I’m playing in slow motion at the station – it’s a nightmare. Why is the station so laggy?
I don't think your graphics card is to blame, at least not completely. It's more of a route issue. I've got a RTX 5080, which is more powerful than your 4060, no doubt. I don't use JetWash's .ini since I cobbled some settings together on my own, not as impressive but still rather nice to look at Regardless, I still get a lot of stuttering and frequent drops to around 5 fps on this route here. Meanwhile, Nvidias resource monitor tells me that GPU usage constantly stays at around 30-40% and CPU usage even below that. So my system isn't stressed out by the route at all, but it's hitching and stuttering nonetheless. Other contemporary routes seem to make more efficient use of the hardware. S-Bahn Frankfurt, which has bad performance for many people, works better than Stuttgart-Heilbronn for me (not perfect, but better). Liberec-Stará Paka gives my system more of a workout (higher GPU and CPU usage, higher temperature) but does not stutter at all. It has to be something related to this route in particular, but don't ask me what it could be. And it's not the 147, since I don't own it and had the stuttering long before the 147 even came out. I use HD graphics, not 4k (resolution 2560x1440, the best my poor old screen can do). The stuttering is most intense in the Stuttgart area, but never completely goes away when travelling to Heilbronn (or back, it's just as intense in both directions).
I tried to make three journeys to Stuttgart today, and on all three occasions TSW 6 froze. I had to close TSW 6 via the Task Manager. And it didn’t matter which locomotive I used – twice the 185, once the 145 – after about five minutes, TSW 6 suddenly froze. I then tried the same thing again on a different route, and lo and behold, everything went smoothly there. Something is seriously wrong with the Stuttgart route here, and I’ve only had this problem since the latest update. Before that, I could drive normally on the Stuttgart route.
Most likely, the problem is with the 8GB VRAM. I performed one service involving shunting operations near the Stuttgart station - the video memory consumption was about 11GB.At the station, I think things are even more complicated in terms of memory use.
