Well nice update but wtf? I have Problems When spawning trains and wagons just like the Livery designer what the hell happened here??? this train and cars have spawn problems DB 110 linke Rhein Strecke DB 110 Bremen The 642 is now half perfect but who is the Cane chair symbol for the inside? Same line the Steuerwagen 463 (Just the car IC car from Rhein Ruhr photo Modus bug UI Bug(It doesn't matter on which route and vehicle as well as mode that can not be switched off( () ()
You don’t know ? When DTG updates the game they break stuff too. I can’t place some trains at all on free roam on the training center, because there’s not enough space:
Hello, Thank you for the feedback (and videos and screenshots!) since we pushed the patch this morning, I'm taking notes of the Free Roam and Livery Designer UI issues you've mentioned above and logging them for our development teams to investigate. We'll keep you informed of any updates to these systems when we have them.
Hi Alex Have you updated east coast main line and southeastern high speed because it keeps crashing on my PS4
Getting the same when trying to spawn Blackpool Class 47s on Southeastern. Flying Scotsman also does not spawn after positioning the green marker and placing it.
Always normal, and I did some more experimenting since then. Turns out the same thing applies to literally any vehicle from those entire addons, be it a Class 47/4 with a full 10 coach consist or a single TEA wagon, they all read as not enough space. Flying Scotsman the same, the entire addon is now completely unusable in free roam on that map either in a consist or as individual coaches.
Hi I thought the winter update 2 was supposed to include a way to save the mini hud as last used, but every time load the game on ps5 it reverts to normal hud which is really annoying .
Regarding the photo mode UI bug, I've seen this too. However the hud still disappears when the picture is taken and uploaded to your Railfan Shots, or at least that's what happened to me moments ago. Screenshot through hiding overlay and taking in PS5: Same exact screenshot through Railfan:
Well I try it and it looks so (The picture is from the PlayStation app) Well yea now I see it sorry hm yea the hud is not visible on the other pic
Part 2 to my prior post about free roam spawning bugs, I tried it on Blackpool Branches and Flying Scotsman initially worked fine. So I was on it for a while and down the line I spawned in a JNA wagon from Southeastern, it spawned properly. I then deleted it to instead spawn a HKA wagon from GWE, then went to spawn the SEH JNA again. The bug repeated, the green outline appeared but when I pressed to spawn it, nothing appeared in its place. On top of that, I now can't spawn Flying Scotsman again either. This leads me to only one logical conclusion, that being that mounting addons to each other is now broken in Free Roam. And that more than likely means that the issue is part of, you guessed it, Addon Manager. Edit: It's actively spreading. The ECW JNA had the same repeat process, it worked and then it didn't, mere seconds later.
A little update from further exploration, the 'not enough room on the map' bug also applies to trying to spawn Peak Forest content on GWE.
Is there a reason why I have good frames on BML but when i place a 16 car ICE3 and 14 car ICE1 on training centre the game has a fit? Also theres a bug where it doesnt let me delete trains that ive plaved
https://forums.dovetailgames.com/threads/update-notes-february-8th.78451/#post-795247 Hey folks. We've just pushed an update on consoles to resolve the Free Roam spawning issue. Should be making its way out over the next few hours.
Sorry to add salt to the wound but I am having multiple crash issues happening on Hamburg - Lubeck using 2 different trains. I am on PS5. These issues wern't there pre update at least not for me. Possibly/probably more however I don't have time to keep running broken services and check. It's happened on 4 of my last 5 runs and for me I can't really play it in this state. 3 express and 1 freight. Thanks
Ok thank you appreciate it. As I say at the very least it's worth looking into to see if it's a local issue. I doubht very much it is though as I've run the route previously without Incident and have no other other issue occurring on my machine.