Thanks but I'd like that guarantee from DTG before I part with any cash! There's no mention of it on the Steam store page hence my scepticism.
But not in today's unless I've missed it. Anyone from DTG able to give an update to a potential purchaser?
I searched the Roadmap thread for "Mildmay" and it didn't turn anything up - missed that small bit at the bottom of the screen you posted, thanks.
I’m on Xbox series x and for some reason I can use a class 166 (GWR) to drive/ sub in for the class 378 odd only just recently appeared after GWE remaster/ hotfix patch
The 166 spawns as a 3 car followed by a 2 car, except when I did it it spawned with the "inner" coach of the 2 car unit facing the wrong way;
Why was the 166 added to this route? It doesn’t look right. Plus it’s a slog to drive at slow speeds.
There is a bug on London Overground - Mildmay Line. Trains arriving at Highbury & Islington station, platform 3 are colliding with the bridge wall. EXPECTED BEHAVIOR: Trains should not come into contact with the bridge wall when driving past it. ACTUAL BEHAVIOR: Retaining wall is positioned too close to the tracks, causing trains to collide with it when passing. REPRODUCIBILITY: Always HOW TO REPRODUCE THE BUG: 1. Start TSW on Playstation 5 console 2. Select London Overground - Mildmay Line route. 3. Select Timetable mode 4. Select Class 378 train 5. Select timetable 2Y58 STRATFORD - CLAPHAM JUNCTION 06:44 6. Begin playing the service When approaching Highbury & Islington Station, you will pass under the bridge. The left side of the train will collide with the bridge support, as it it is positioned too close to the tracks. Switch to external train view and you will have a better view of the train clipping into the retaining wall.
Birmingham to Crewe had horrendous blurring issues on console, but All Aboard Studios actually did try and solve it. They made it better, it not fully gone. Incredible trains not even bothering to try and lessen the blurring after all this time is appalling. I know it's a core issue, but as AABs and Firefly have shown, it can be mitigated.
AAB made steps to solve it? I can't even play the route with it's main train, the Class 350, being turned on without it immediately becoming a blurred mess
I did a service the other day and it blurred for a short while around Smethwick, before easing up (not going back to full detail though). Maybe time of day is a big factor?
The AI class 345 and 720 pantographs are not raised to contact the overhead wires. This was noted at Stratford Station. On top of that, the headlights and driver were on the wrong end as the train was moving in the other direction.
There is a broken piece of track between the NLL and the WLL meaning that it is impossible to run AI services in Scenario Planner on a modded system. A bit of a shame as it is about the only piece of the WCML lines at Willesden that it is impossible to see trains run on. Also could you please ensure that there are more markers placed on this route when the extension is produced. At the moment there are very few on loops at Stratford, at Highbury / Camden and at Willesden TMD meaning that these cannot be used in scenarios even though they would be very handy. You can only do so much with a mod. Scenarios - Proof Of Concept - Mildmay Finally would you go to the trouble of updating the little bit of MML between St Pancras and West Hampstead. I have run a service along this and can see that much of the scenery work is done. It would be lovely, and a surprise, if this short bit of line could be brought into play. Thanks
Should I be sitting for 10+ minutes waiting for the brake reservoirs to fill in the "route learning" scenario? They're at 7.5 and don't appear to be going any higher. I'm sure this was an issue a year ago, why hasn't it been rectified? Or is part of route learning sitting for a interminable long time waiting for brake reservoirs to fill?
So just picked this up in the sale however noticed that passengers don't embark or disembark at any stations enroute. Is this the same for anyone else? Requested a refund until fixed.
Yes this is a known issue. The free extension to Richmond that’s coming soon is also going to include updates and fixes so worth hanging on to I reckon.
i can’t help feeling that this route should’ve been held back by a month or so for extra polish. i’m well aware that as a single dev, there’s huge financial factors in the release timeline but issues such as the exaggerated bounciness of the 378 the 378 having the wrong HUD (the irl one goes up to 90) the 378 not having its own soundset passenger spawning issues a few light baking issues here and there, nothing major but still needs addressing and of course, blurry textures have been unresolved since launch. as i say, i know that the product needed to be released for johannes to earn money, but dtg or another third party could and maybe should’ve stepped in to iron out the main things. i know that most of the listed issues should be resolved with the richmond extension, but this is a product which is nearing 18 months old and i can’t help feeling johannes has been slightly let down, he’s helped with other dlc and received little in return
Thanks for this, I had read about a possible fix in the pipeline so thanks for clarifying. It's such a shame and as historicalduck7 says, the product is 18 months old. Hopefully the fix comes soon...!
Beware of buying known buggy DLC in the hope that a patch might be forthcoming. Plenty of previous examples of patches coming a very long time after the issues were first reported or not appearing at all.
