I don’t like the engine sound, especially above 49 km/h it sounds like it was artificially generated, and it’s terrible in my opinion. At startup, the engine sound is completely fine and nice, but above 49 km/h, when it shifts, it’s really awful in my opinion.
Anyone else think that this 2018 timetable the blurriness is much worse then the 2000 timetable. And overall performance feels a lot worse as well.
Not impressed with all these comments. Won’t be buying this one. Looks like a very problematic release.
Also, good morning folks. We're going through all your feedback on this today. I can only apologise that console users aren't having a great experience. Keep feedback coming, and if anyone has accompanying videos/pictures of their feedback (like not enjoying audio, or experiencing crashing around Stuttgart) then please fire them over and we'll get these added to their appropriate places.
Worth noting (in my experience) I only get blurry textures when heading away from Stuttgart, all the services I've done so far the other way have been fine. The only other problem is poor performance approaching Stuttgard (which was present in the 2000s timetable too)
Folks getting blurred textures; are you able to let me know if it's all services or particular services (if you have the service number or details that helps), if you're on 4K or HD and if what layers you have installed? And your platform! Thank you.
It might be all services but try 08:07AM S4- Stuttgart - Ludwigsburg with the Br 423. All layers PS5 4k mode
Hi again Harry, So, I've replayed the same three services with identical parameters from yesterday (see below for reference) with the only difference of switching from 4K to HD display mode: - RE (19501) - Mannheim Hbf to Stuttgart Hbf - 0717 - DB BR 147 - Light Clouds - RE (19509) - Heidelberg Hbf to Stuttgart Hbf - 1319hrs - DB BR 147 - Light Clouds - RE (19515) - Heidelberg Hbf to Stuttgart Hbf - 1919hrs - DB 147 - Light Clouds The results are as follows: - All three services I managed to complete. However, just as you arrive into Stuttgart Hbf, blurry textures become a major issue every time. It's also worth noting that after completing one of the services, when I went into photo mode at Stuttgart Hbf to provide evidence of blurry textures, I received an 'out of video memory error'. - From my play through of the route so far, I've concluded that perhaps Stuttgart Depot might be the biggest resource hog of the route. After you pass Stuttgart Nordbahnhof station going towards Stuttgart Hbf, performance becomes really poor with lots of hitching in the final few kilometers. Coincidentally, but not surprising, it's also around here, roughly 2km from Stuttgart Hbf and near the depot - where all the 'out of video memory errors' occur. So, the devs really need to focus optimisation around here and the main station to increase performance and hopefully also get rid of the blurry textures. Some other general feedback from the loco, route and timetable: - At night, many, if not all, the dosto coaches with the 147 are in darkness with no passenger lights switched on. - The cars are still old fashioned; for a 2018 timetable, the road cars need to have more modern designs to increase immersion. - The 147 display screens I can't seem to have in dark mode for night time, instead they seem to only remain more of a brighter blue colour. Any more question Harry, then please let me know. I really like the route, but it's let down by the poor performance and blurry textures on console. So, hopefully this provides some good info to help the devs better optimise this route!
Hi there, Really sorry you're experiencing so many performance issues, cloudyskies21 - but all this info is MASSIVELY helpful for me to chase with dev. I'm hoping they'll be able to update me on a potential fix, but a workaround that has been suggested (although still not ideal, could work) is to save before reaching Stuttgart's 'crash zone' and restart. I'm not sure whether this just fixes the service to make it completable, or whether it helps with memory saving, but it's all the info I have for now until we get a fix in.
So doing the journey mode and across this job. Thought a nice summer then I i saw the snow level. Really does it snow in Germany in July.
Platform: Xbox Series X Service: DGS 95008 Karlsruhe Rheinbrücke Raffinierie nach München-Milbertshafen Train: DB BR 140 Instant Failure because of Red Signal. After First attempt I restarted the Service and again instant Red Signal
Thank you for reporting this, I just tested this on Steam and can confirm it's an issue there as well. Will put in a ticket now.
Sorry, has this actually been tested by anyone?! What I'm seeing passing by here is bizarre..... if you paid for this, ask for a refund, I'd say. Selling something of such quality is just insane. So many bizarre errors, even after the release has been postponed. Just absurd. You should be ashamed!!
Completely understand your frustration, but myself and Jan have been trying to help with logging these issues. Being disappointed and angry is reasonable, but please don't tell Jan he should be ashamed when he's trying to assist another player.
Okay you're right! Let me be clearer… That ‘you’ was meant as the company, not any specific person. Jan can’t do anything about it, of course. So let me make that clear now!
Hello DTG, DTG really ought to be ashamed of selling a DLC in this state. When it was announced that BR 147 was coming out, you could already see from the DTG ambassadors’ live streams and videos that there were quite a few issues with the locomotive. DTG then wrote that the BR 147 would be released later because of these very issues. And now DTG has released the BR 147, but why weren’t the issues fixed in the meantime? It’s one thing to say the BR 147 is being delayed due to problems, only to then find that these problems haven’t been fixed. In my view, that’s tantamount to deceiving the buyers. And as we know from DTG DLCs, there might be one patch that fixes a few things, and after that, we’ll hear nothing more from DTG.
I bought this DLC not so much for the new locomotive, but for the new timetable. I'm thinking to myself that maybe the new timetable will include new routes: to deliver/pick up cars to the power plant, to deliver metal to the metallurgical plant, and some other routes to enterprises. What do I see? Nothing. Timetable for BR294/363 Almost completely copied from the 2000 timetable. Nothing new. DTG, are you serious? Why do enthusiasts find services that were already available and that could be added to the timetable to make better use of the route? There are not that many of them, literally about 10, probably. There are tracks there, you can go there on foot - why don't trains go there? After all, add a locomotive to more than one route. There's neither one nor the other. What should I pay for? I applied for a refund.
That 'zwangsbremsung' message came on out of nothing while i was on an external cam. No brakes are applied, i'm in the LZB zone on leipzig-dresden. Also when entering LZB my train braked without notice, might be something i did wrong though. Also the blinking 'open door' light is gone
hi DTG Harry , My CTD was only on my first run on the stuttgart route. I haven't had problems after that. This CTD might be more for the stuttgart feedback thread. A bit similar with dal#7945
Platform: PC, Steam (No mods) Route: Frankenbahn: Stuttgart - Heilbronn (2018 timetable) Service: RE (19055) Würzburg Hbf to Stuttgart Hbf (08:09) Train: BR 147 Issue: Player spawns on foot away from the train, every time
So far it kinda works on my end. The model looks great, the sounds are good and it handles quite well. Only tested it on two services on Stuggi and in Free Roam though and at least on those it behaved. Then again since that route isn't equipped with LZB I didn't run in on half the bugs I've read so far. Oh boy. Apart from everything Trainsa covered in his ambassador preview including false button logic for the cab activation and every error linked to that (there may be more, hang on) and the various typos, the loco itself runs OK without LZB. I've been thinking on the issue of the trains without lighting. The trainline is just a click-button here. If I remember correctly my train spawned on the last service on the timetable from Bietigheim-Bissingen to Stuttgart with lights on. As kinda muscle memory from most other trains we've got I pressed the trainline button with the intention of activating it. Looked outside a few minutes later and found my train to be dark. My mistake, so far. Reactivated the trainline and the lights came on again. Funnily enough the actual train lighting controls inside the right MFD's menu should do that. They're listed there, but they're not interactive or working. Since the cab activation button logic is switched, the cab stays inactive according to the diagnostic screen on the right MFD when I in fact activated it. Now what if that logic error continues inside the MFD menu logic? Also have no idea why the equaliser (Angleicher) button is inoperable here. The shunting controls at the windows are interactive, but I've not been able to actually use them so far. Not sure what's going on with those, but while on the topic of the shunting controls: Why is it that they've been recreated as usual, for a time period where they're not really used IRL anyway, while it was stated for the WiKo that they weren't recreated for that reason when that can car and route are originally set to an era where they were used? So far it's the only piece of German rolling stock where we can't play with them and it makes no sense to me when the literal next German DTG DLC does have them kinda operable again on a loco that was built 20 years after the WiKo... It's got more typos than just the infamous Baden-Württemburg, close to the amount on the 294, which raises my suspicion that AI is being used for texture creation but unsupervised and its results are being taken for granted without checking when we all know by now that AI doesn't know what it's doing and shouldn't be (blindly) trusted with it's results. The timetable seems to be sub-par from what I've read so far, which raises the question of the pricing. If the timetable is a mess, the route crashes for many people and has a poor performance even on good PCs (look at the immense stuttering and freezing on Jan's preview stream, that's an issue with the route though mostly), the loco (basically decent if not for everything wrong with it) doesn't come with any new cars (would've been a great selling point to add a high rise entry Dosto after a decade of TSW with it), how is it worth 17,99€? We got the BR Class 90 without an engine room or new cars but with its own timetable a few weeks ago for less money and it's riddled with less CTD errors at least. Yes, that's a 3P product, but from the cost-benefit experience it's better than the 147 and it's still rather messy itself. One last kinda positive thing: I've tested compatibility in Free Roam and made a tandem service of the 147 as a pilot and a 187 as second engine. They work well together. They sound awful together and you start to question your own sanity if you stay too long in the outside camera. But they work together.
I've noticed the train seems buggier on Dresden-Leipzig vs Stuttgart, with the blinking door light and other things seeming far better behaved on the "native" Stuttgart route. Why is TSW set up in such a way that simply being on a different route causes differences like this? Why aren't the train systems simply the train systems, that operate as needed? What on earth difference does the route/map make (outside of potentially wrong voltages etc) to how the LZB/AFB systems function? Does each route have its own version of LZB that requires a train update to use? If so, why? In what janky mess is TSW under the hood?
PS5 Pro I currently only installed the map Stuttgart + BR147 + KWG map (necessary especially for freight trains + ICE1) + BR101 + MKN ... this combination with only HD settings and switched off substitution was on the edge on the Stuttgart-Heillbronn connection and blurred at times, the FPS practically fluctuates between 20 - 30, sometimes up to 40 FPS ....... it doesn't seem like a big win to me yet, there's no overview of what the texture is optimized for, so for me on the PS5 Pro so far it's more bad than good
Platform: PC/Steam Route: All Service: All The door interlock light doesn't work any more after 1 stop. Happens on multiple routes and services .
Agreed. On the original timetable I had no blurriness, but I do on the new one. Especially when starting at or approaching Stuttgart Hbf. Apparently the added trains push it over the edge.
I’ve encountered a few issues with the locomotive: -The voltage of the overhead wires is not displayed; it only shows the status of the MCB. -In the multiple-unit status tab, no useful information is shown. For example, it doesn’t indicate whether the spring brakes are applied. Is this normal? -On the DMI, the power output should be displayed, but the field remains blank. -LZB is switched off on startup, and when I turn it on, it deactivates again after a few seconds or when I leave the cab. Or atleast the 'B' is gone. -The TB0 voice does not work. I can operate the doors, but I don’t hear the “Türfreigabe” announcement. -The pantograph can only be lowered after selecting “Auto.” -The '>5 bar' button does not work. -The 'sifa' and 'zugbeeinflussung' voice bugs sometimes. Other than that its a good loco
DTG delays BR 147 to fix issues with the BR 147 only to release the BR 147 full of bugs. What was the whole point of the delay if the product was gonna be released with these issues regardless? What an embarrassment. I don't have the Stuttgart route but even if i did, I wouldn't buy this slop
Platform: PC (Steam / Epic) Game: Train Sim World 6 DLC: DB BR 147 & Leipzig-Dresden Issue: LZB system broken on BR 147 when entering LZB sections from Leipzig-Riesa ruote section Description: When driving DB BR 147 and entering an LZB-enabled section (on Frankenbahn or other routes): 1. LZB attempts to activate 2. Immediate forced emergency brake (Zwangsbremsung) 3. Cannot release brake / cannot acknowledge / cannot reset 4. Train is stuck; unable to continue This happens every time LZB engages on BR 147. PZB works fine. Only LZB is broken .
I was also confused at first by it but you just need to do it in the right order for it to work: reverser to forwards, move afb to selected speed and finally move throttle.
When under 500Hz restricted, then passing (and acknowledging) a 1000Hz, the yellow banner reads a max speed of -1km/h after the 500Hz times out. EDIT: ...and got stuck in that 1000Hz/-1km/h mode until I stopped, reverser into neutral and back to forward.
OK, service RE19057, approaching Stuttgart. Signal with Zs3 8 (with no forewarning?) and reduced speed distant signal (green/yellow), acknowledge. Slow to 40km/h, don't release PZB. Next main signal is reduced speed (green/yellow). By time of passing this signal, the monitored mode had timed out, all back to normal. Slow to 30km/h for unsigned speed restriction, hit 500Hz - now under 500Hz monitored, yellow bar shows max speed of 45km/h. Continue towards Stuttgart, just before 046' signal (ground, showing Sh1) is another 500Hz magnet. On passing this, immediate emergency brake. Why is there an emergency brake on hitting a 500Hz while already under 500Hz monitoring?
Compressor sound also not audible from the inside of the cab. I have sat in a BR186 where you could definitely hear this from both cab 1 and cab 2. Is this different from the BR147? Doesn't seem logical to me.
Hello again, I've got some additional feedback from two more different services I've played (see below). Just as a reminder, I play on Series X and have everything with exception of the DB BR 145: - RB (19139) - Neckarsulm to Stuttgart Hbf - 1725hrs - DB BR 147 - Predominately Cloudy With this approximately 50-minute duration service, starting from the Heilbronn end of the route, performance overall I thought was quite good with no blurry textures for the majority (which is a major improvement in my opinion compared with when the route came out). However, once you get nearer towards Stuttgart end, namely beginning around Ludwigsburg station (the penultimate stop) I observed that blurry textures appeared briefly on and off. Only once arriving the last kilometer or two to Stuttgart Hbf (as mentioned in my feedback from the other day) does blurry textures appear permanently looking quite bad with a performance drop too. - RE (19502) - Stuttgart Hbf to Heidelberg Hbf - 0817hrs - Dosto Cab Car - Light Clouds Not long after departing Stuttgart Hbf, blurry textures appear relatively quick. So, with your suggestion in mind, I saved the game around a few minutes after - just after passing Stuttgart Nordbahnhof station. Upon resuming the saved game, apart from a random PZB zwangsbremsung and PIS screen not displaying (bugs from the saved game), very importantly blurry textures never reappeared, thankfully. In addition to these, just some further general observations: When there are blurry textures, has anyone noticed that the loco and cab car seem to be less affected compared with the other coaches? Is this because they've since been better optimised regarding the use of 4K textures etc I wonder?: Meanwhile, some further general blurry texture images; also note the AI train on the left without passenger lighting switched on which is a big problem with this route and others: Also, DTG Harry just one final thing I wanted to note again, every AI service with the 147 doesn't have any passenger coach lights switched on which really ruins the immersion, especially at night time. So, if you could open a ticket for this would be really appreciated! As always, happy to help provide more feedback for you and the devs to get this route sorted in a proper way for us to enjoy on console. Thank you.
That's very interesting. For me on Series X, the original timetable and overall route since the beginning was very bad regarding blurry textures. These were some screenshots of my first playthrough of the route back in December with the original timetable: In my opinion, while the route still blurs (as seen by my feedback above this), I think there has been a small improvement at least on Series X - although video memory errors etc are still completely unacceptable meaning it's impossible to play in 4K display mode.
