It's very unforgiving (we joked that it should have a black colour for difficulty rather than red). My advice would be to keep as close (or even below) 1 km/h as you can achieve when getting within 10 meters of the stop point. While technically you shouldn't use direct brake to hold speed with coaches coupled, this one probably one of the exceptions since the train is broken down on quite an unfortunate stop with a 1% gradient Use full electric brake and as soon as you hear "Stop" (or perhaps even right after the "1 meter" call) go immediately into emergency brake. EDIT: Probably the least frowned upon method, if electric brake is not enough to hold speed, is to drive without direct brake applied but full electric brake applied until you are within one coach (or less) and then apply train brake to stop the train, then release the train brake but apply direct brake. This would minimize the time the direct brake is applied and lower the risk of brakes overheating. Did you remove the reverser before moving it into "0"? This was a bug before which I submitted a fix to (so it shouldn't be possible) but since we've already had an issue with patches not getting out to all the platforms (i.e. the Interference crash on Xbox) I'm slightly worried.
Yeah, I pressed E and nothing happened on almost every single menu possible. It's likely something broke somewhere along the way, I don't know how, but I'll give the scenario another go from the start and hope that fixes it.
Not played any freight yet but as it been sorted now because if I remember rightly. In the original timetable some of the freight journeys really struggled to in wet weather.
This is caused by (in my best estimation) a core bug with the periodic/cycling behaviour of these switches. In certain situations the value skips and becomes 10 instead of rotating back to 0 (or 9). I have fixed it locally by scrapping the core logic and scripting it myself but as a workaround what you can do is to go "the other way" if you encounter this bug. For example, suppose you use the decrease button and 11 goes to 20 (or 21 goes to 30), to get it back to the correct value you can click increase a couple of times. Or vice versa (if increase is bugged use decrease to go back).
this was a question I guess mainly for cwf.green, kinda got lost among other comments, so I was wondering about this O ... I know a consist of 101 + 7 coaches isnt a super long train, but in my previous runs on other routes where the consist was fully expert, if I got Sifa Zwangsbremsung, only like 1-2 times had I been able to recover the train and still be in motion... most cases resulted in screeching halt in this present case, I kinda lost focus, but still pressed Q quite fast afterwards (was going around 160 kph) and after I pressed Q I was still moving at like 80 kph (the brakes releasing quite fast)... so I wanted to know
You thought with this gamepack they would have moved the stop markers away from the red lights. But no still on top of them almost.
try setting it to 29, then back to 20, I reported the bug, too.....seems TSG and DTG rather push out buggy packs than run proper beta testing.
Scenario Interference: Too bad the information transmitted on the radio is not in French (I have it in English)
I also drive a PS5 Pro, so I tried your method with saving, while driving the ICE3m I was driving in the opposite direction, the blurring appeared when leaving Fulda at the freight station, I saved, left and reloaded the saved game. The only thing that surprised me was that I had to turn LZB off and on again to make it work and show correctly
What service was this? I definitely changed the stop marker for all the IC/101 services and also the freight (moved back things to leave about a loco length from the signal). I think I also changed most of the stop markers on the Flixtrain and ICE services. For example KWG doesn't have correct automatic marker positions for trains based on length so I edited this manually based on the 260/360 markers at Fulda & Kassel. I even changed a lot of the AI RE/RB markers based on videos and pictures (which was quite excruciating since I had to place a train in the editor, check the position, then go back and move it iteratively until it had the correct position ). As I stated above, I was only able to reproduce this issue after we had reached "dev complete" which usually means that only crash/serious game breaking issues can be submitted. Since I now have a fix finished I will talk with DTG about whether it is possible to include it in a hotfix, but I make no promises since that is not up to me. We were fortunate to have several fantastic volunteers to record voice lines with in English and German (which was possible because they are fluent in both languages), not so in French or other languages unfortunately. Personally I would prefer having German voice lines with English subtitles, but with the way the game works this would require making duplicate scenarios (one with English VO and one with German VO) which wasn't feasible during development. Unfortunately this is a mostly global issue in TSW where some of the trains eat up a lot of memory and cause blurry textures. The only solution from our side would be to disable layers based on what console is used which obviously isn't ideal either. Disabling substitution seems like it has an impact of lessening/preventing blurry textures, perhaps you could try that? That's the less aggressive way since you still see the AI trains, just with the default locomotive. If that doesn't work, the ICE-T is probably the more demanding train that you could disable as a layer (or if you want to drive ICE-T maybe try disabling the 101 layers and/or the Flixtrain). Hopefully there are more core performance optimizations in the future that can resolve these issues.
Thank you for the answer. It is interesting that the textures are blurry for me only after Fulda station on the line where there are not so many trains. On the contrary, in Würzburg hbf where there are many trains, the textures are fine. I will continue to test disabling layers, maybe it would be good to indicate its memory requirements for each layer.
It was a freight run i cant remember witch service but stop marker was like 5 yards from a red signal.
I am on PS5 Pro. As someone mentioned here recently, saving and reloading the game at a given moment can help, but unfortunately this will "turn off" or change some of the train settings, especially the safety systems or perhaps even the power supply of the set. But in the current situation with TSW5, this was already likely to cause problems with textures...... When I didn't have Dresden-Riesa, Bremen-Oldenburg, Ludwigsbahn, Niedertahlbahn and Maintalbahn installed, even with substitution turned on, I had no problems, or rather I didn't encounter any blurring. Currently, it's always a big alchemy. But doing it for consoles without AI traffic, similar to the Frankfurt S-Bahn, just leads to the fact that people don't buy it at all, that's not the right way.
The worst are the customers who invested the most money in this game. The more DLC, the greater the probability of a texture error. I did not expect that this package would have texture problems and bought it immediately after release. I was surprised that the texture error also appeared when playing the scenario. There, the AI operation is fixed. I made two attempts and the texture error appeared in the same place. That would mean that the texture error would have to appear in this scenario during testing.
I agree with your feelings, my feelings are the same, I have practically all the German DLCs, except for the S-Bahn Frankfurt and Rapid Transit. In general, the English DLCs work better, I have practically no problems with WCMLS or WCMLSoS ...... I mentioned some time ago that I suspect the German Dostos and there will probably be more vehicles that clog up the memory in some way. And the Expert version is probably a big load too. It's a shame that the package didn't include a non-expert timetable, with the original BR101 ...... I'm personally not an "expert" player It's a shame that there isn't a button that would "empty the memory", probably similar to what Save and reload a saved game does ... as long as it doesn't destroy the settings and etc.
Unless you played an IC service from the original 2022 timetable by mistake I can guarantee that the train was all Expert vehicles There are a few reasons for why you lose such a big chunk of speed if you fail a Sifa check: The IC coaches have really strong brakes, both in terms of air brakes and the Mg brakes, however the biggest reason is due to the brake pipe accelerators. These engage when the brake pipe pressure drops rapidly and open up valves to exhaust the brake pipe at each coach (rather than just at the locomotive). These won't close immediately when the brake pipe starts charging from the locomotive. On release the delay of these valves to close was uniform and based on a prototypical average, but with the recent physics update I made them vary randomly between normal minimums and maximums. You may simply have gotten a train of less "laggy" valves, but losing 80 km/h is still quite significant so that seems sort of "average" to me It also depends on what speed the intervention occurred at, since even though disc brakes have relatively flat friction curves they still do "bite" more at low speed (nothing like tread brakes though for sure).
Gotta say cwf.green the more I read of your explanations, the more I get to appreciate the Expert DLCs. I started using the Expert 101 and IC cab just recently, and the level of detail continues to amaze me. Big kudos for all this work I can remember all the comments when the Expert 101 was originally released, about "it's just a new cab and a refurbished loco" or "it's way too pricey" or "we already have a 101, we don't need another"... Must have been hard reading all this, knowing how much work has gone into it.
I use the new TSC-X controller with the fantastic interface by Cobra and it works really well with the 101 expert. I don’t have a rail driver any longer so can’t help, but as I said, it works great with the joystick
In the layer overview, I was interested in one called, I think, Surprised layer. Does anyone have any idea what's hidden under that?
PS5 Pro Similar to the Ludwigsbahn map, installing the Dresden - Riesa map will deactivate some trains, in this case the AI Desiro trains in Fulda will no longer be displayed. It is possible that this also affects the AI628/642 combo in Kassel, I haven't investigated that yet, but it might also be.....
I gambled that there existed a non-insignificant segment of the player base that share my interests (study level simulation). I think so far the gamble turned out to be successful, I guess we'll see in the future if it "holds up" If I answer this question it might spoil some things for the future. Let's just say this currently AI-only layer might become playable EDIT: Before this gets taken out of context etc: the layer is not currently playable and any decisions on buying this gameplay should assume that it will remain unplayable. This sounds really strange to me (and worrying), I will investigate.
Well, looking at this forum and how people are longing for more Expert content, I'd call it successful. And it will continue to pay off, I'm sure
Xbox Series X Game is unplayable since installing this DLC, I tried playing the 40 minute scenario twice and it crashed upon taking control of the 101 both times. Have since been restarting the game and restarted the console, has crashed during loading screen before the main menu 3 times now. It’s been an hour. EDIT: Finally got game started again and game crashed again when taking control during the interference scenario.
I assure you, I played the new timetable, to try it out ... I know why you lose speed when you get Sifa zw.... I have discussed this at length with you, raph and a couple others shortly after release, so I already know that getting Sifa zw. aint no joke the thing I was wondering wasnt that I was going to lose speed - I already know that in most cases, getting Sifa zw. almost always means you either lose ton of speed or even get to stop... on the contrary - I was surprised that after getting it and even taking like a second to press Q, I didnt get to a screeching halt - brakes released fairly quickly and I lost "only" half the speed (from like almost 160 kph to like 80, which I still call a success lol) thats why I was asking - I wasnt expecting the brakes to release so quickly and even continue moving on... thats why I was wondering if the coaches are also expert simulated so if I understand your reply - I just got extremely lucky that the brakes released so quickly?
Thank you for your response, so we'll leave the surprise layer alone. I've further investigated the traffic. In Kassel, AI BR628 appears on RE2, RB4 and I think I've seen it on RB39. But AI BR642 also appeared occasionally on RB4, maybe on other lines in Kassel. Now, similarly to Fulda, AI BR642 is not in Kassel either, but since it's somehow substituted by AI BR628, it's probably not so noticeable in terms of traffic. (I didn't have all the add layers installed at the beginning, I just installed Dresden Riesa later, when I was testing at what load the textures start to blur, so that's why I didn't notice it right away)
PS5 Pro - then one more side note. The emergency method with saving and reloading does not work with the scenario. At least not for me. When I reloaded the Keep running scenario during the game to eliminate the blurring of textures, it was no longer possible to control the train at all. The reverse lever disappeared and it was not possible to move the power lever at all. In the timetable, the LZB setting is deactivated after reloading, and I had to turn the train lighting back on, but otherwise the game continued to run and was playable...... but it probably won't work in the scenario.
PS5 Pro Scenar Rescue Even though I finally passed the brake tests successfully despite manually setting the train data, everything went fine, then finally, when I was supposed to leave for Kirchheim, the brakes went crazy and I can't release the train brakes...... I don't know if I did something wrong.
Hey folks, we released a hotfix that should have fixed the crashing issue during the Interfere scenario. Please let me know if these crashes are still happening post-update.
What does "brakes went crazy" mean? There's not enough information in your description to identify the issue. If you can describe it in more detail and ideally show a screenshot of the brake gauges that would be helpful. I would also highly recommend looking through the BR 101 Expert manual since it explains a lot of the more complex systems in a way that could help you troubleshoot issues.
First of all, it is necessary to mention that I am riding in non expert mode ..... but so far I have managed to complete all the previous scenarios and even a few rides within the timetable. When I put the brake release, or brake in the running position, the pressure does not go to 0 and I cannot move off ....... EDIT: I try it again and see ... EDIT 2: So on the third try I managed to finish it... ))
I'm rewatching the stream and I saw that lot of the shunting movements are done "against color" rather than proper Sh 1. I know that altering the map is not the focus here, but given it's just three (major) stations, can that be revisited? It definitely takes a lot away from the expert experience you are aiming for when such basic thing is wrong. I believe it was Lukas who said that for Kittenwaldbahn purposes, a new subsystem was developed for signals so that they can properly distinguish between train and shunting movements.
On the engineering scenario, I ended up getting a 1000Hz light flashing and the brake pipe dropped to zero. There were no alarms or anything in the scenario to suggest it was part of it. It happened about 5-10km after changing to the left track. I was unable to recover from this, despite trying everything I could think of, even isolating PZB/LZB. Not sure if it was an issue I caused as I accidentally started the run in PZB mode as I put the reverser to neutral. Also, the PZB tran data wasn't entered when I entered the cab, I had to press send. I would also like to see the GSMR dialogue in spoken German with English subtitles, although, I read your post earlier on that it's not the easiest thing to do. Does changing the language settings in game give both German speech and subtitles?
Yeah when you choose English in game you get English voice overs in game so better you choose English
Just noticed that in the journey mode there are jobs IC 2278. One in chaper 1 amd one in chapter 2. Only difference one the the rain the other in dry conditions. Both in the cab car. Is that correct .
I really don't get this. There were a few instances where the speed reached 201 due to the train not slowing down sufficiently when transitioning from an incline to a decline. However, for the other times, while on LZB and moving at the maximum permitted speed, there is no reason this should've happened...
We discussed this earlier (I can't remember where, perhaps someone can help ). Essentially the game uses the same parameter to check if you are overspeeding and to display the current speed on the classic (Shift + 5) HUD. Since the speedometer will spike if your wheels are slipping (and droop if they are sliding) the game thinks you are overspeeding. My recommendation would be to keep an eye on the speedometer and tractive effort gauge and decrease power if you are slipping excessively. The locomotives wheel slip protection is not perfect (in the simulation or reality) so leaving the throttle at max is not recommended if the track conditions are poor. Lastly, both on the real BR 101 and in the simulation, AFB will deviate from the target speed by up to 2 km/h temporarily when transitioning from a steep increasing gradient to a steep decreasing gradient, as on Kassel-Würzburg. That's realistic. Usually in game the deviation is not large enough to make you lose many points, but if your goal is to never overspeed then my recommendation would either be to brake manually or set the target speed 5 km/h below the line speed.
