I am having problems with certain locos in free roam on certain routes namely the older locos class 52, 47 etc, I spawn them, climb aboard set route, but then unable to move the train the brakes release ok, but nothing happens when applying the throttle?
I’m glad I’m not the only one… it seems that free roam don’t really like trains from TSW OG, every time I had an issue trying a train, it was with one from the first TSW. I wasn’t able to the BR182 as well. I tested every trains on the training center.
Strangely i didnt came across this problems. I noticed the cl52 & 47 cant pressurize the brakepipe. The solution is to release the brakes, activate the aws and acknoledge. Then the pressure should rise and everything is working as intended. Tested on WSR, which is an old route. Could get all of the locos to work.
Ok I have submitted a support ticket, but will probably get the known issue closed ticket response or whatever.
Sometimes the older BR locos spawn with the brake switch set to the wrong type (vacuum rather than air). You need to switch this and apply the brakes
I'll make sure to follow the ticket and log it in our community list for Free Roam issues. Development should get visibility either way, however we can keep an eye over its progress more easily. Can I get any confirmations of affected platforms please?
The GWR HST 4 car set spawns with the DSD active in the rear power car. When you go to isolate it, the switch is already in isolate so you need to toggle it to on and back to off. The same happens when you change ends. On PS5.
Spawned a Class 52, noticed that theres no driver figure shown inside cab when viewed in photo mode or external cameras, dont know if this is the same for any spawned loco (player controlled or ai controlled)
One of the issues I've been having is that I can't spawn trains on some of the tracks at Princeton Junction as they show red even though there is space available.
I noticed sometimes, I don't know if it's randomly or if it's because of some specific conditions that I don't know of, that some trains I spawn are completely bugged - all buttons, switches and keys (even valves and other stuff that cannot be used unless unlocked with a key) that are non-static in the train are actively pressed/clicked/activated on spawn - wouldn't be a problem if the train spawned wouldn't have brakes that require unlocking with a brake key to use it, because when it spawns bugged in the way like I said before, then the brakes are also active; meaning they are stuck on Release instead of Off, and to insert or unlock the brakes using the brake key, it needs to be in Off position, otherwise it's not possible because the game doesn't let you. This happened to me on the BR 103, 110 and 628. Also another bug since TSW 3 (lol) is that sometimes, the BR 628's reverser handle gets "stuck" where the player cannot use the handle anymore at all, being unable to switch directions, to set to neutral, and removing the handle, even after reloading. Sometimes it works suddenly again, and sometimes I even had or have to restart the whole game. Another thing is that I am not able to uncouple the BR 612, but that wasn't possible before I think, but I hoped it would be possible now. Aaaaaaaaaaand the crashes in free roam when you remove trains from a timetable still persists.
I’ve spawned trains in for a free roam and found the brakes applied in every cab. Could be worth checking.
Done a few tests, and as far as I can tell its just the class 47 and 52 that is affected for me, all the other British diesels work fine for me.
Some locos are not spawning correctly - in some cases an "im stuck" on the pause menu will fix it, but not all. One of our engineers is working on it. Matt.
I also submitted a support ticket yesterday with the list of symptoms with US locos freeroams issues (BNSF SD40-2, BNSF SD70ACe, BNSF ES44C4, CSX GP38-2, CSX SD40-2) . As Matt and Alex are both following our freeroams issues, so we can be reassured of a solution
Ok, the issue is also affecting the Pacer from the JT Blackpool route, spawned one in freeroam and the brakes wont release, so cant drive it. Needless to say the class 47 from the JT route is also effected but I expected that, as it is a reworked version of the already existing class 47.
I would rather they fixed it, since freeroam was promoted as the new thing on TSW 4 it should work every time without users have to fudge it to make it work.
Maybe Matt could inform us (the customers!) what is the progress of this engineer. Maybe two engineers could help to solve faster.
Nothing rushed about it, it was a big feature to get implemented and working even to the level it's at right now, we have big plans to take it forward over time but none of this stuff "just happens" - the big thing for me was getting the underlying feature in and people using it, figuring out how to get the best out of it and seeing what issues crop up since this works with the entire back catalogue and there's no practical way to fully test everything anyone might want to do (every train on every route in every situation? heh). We're going through ironing that kind of stuff out now and that gives a firm foundation to then build on. I hate this "it doesn't go as far as it could potentially go / as far as I wish it would, therefore it was rushed" attitude, there's nothing rushed about this at all. Engineer is making decent progress on it - he was diverted for a fair while finishing suspension core feature set off but that's been done for a while now and he's working his way through this. It's proving to be much more of a "death by papercuts" type problem though which isn't ideal as it means fixing per-train but there are some fixes which come in across multiple trains. I suspect we're going to end up either pushing the release of it out a little more - or - splitting it in two and doing a release very soon of what's been done so far and if we do the latter (which is my preference) then we'll provide a list of the trains that are fixed as a result. The latter however depends on a number of critical things like how much testing is required for the changes that have been made - if the fixes specifically only affect how its working in free roam its easy, if they affect the train more widely, it could mean needing to re-test all those trains (and any others affected by common code) in all existing situations such as scenarios, services etc, as well as proving it actually fixed the bug in question. Don't want to release an update and have "yay fixed free roam, but broke all the scenarios and half the services" type result I think... Once he gets his current work wrapped up and into a beta build i'll work with the beta team and QA to start doing some broad testing of it to get a health check on where we are at and if we're looking good to go. If I'm being brutal though - my strong feeling here is that rushing it before christmas is not the answer and i'll be instead aiming for something shortly after new year, with all locos, and a more robust test plan behind it. Moving in the right direction though. BTW him finishing suspension core work deosnt mean we're "done" on suspension - now the features are there, it needs to be added to trains, tested and then almost certainly refinements made to the core features as the engineers who work on the specific trains come back with "thats great for these types of trains but doesnt work for this type, can i have extra settings for this too please" type requests. It's a good milestone to have achieved, but not yet one you can actually expect to see coming through soon - but hopefully not *that* far off now. Matt.
There is a huge difference between wishing VS wishing for things that were promised, marketed and labeled as such from a company that sells products. If you cannot provide customers what you say, then DON'T. I'm really sorry but you are clearly thinking software development from the view of a salesman instead of a software engineer. This is exactly what I was taught in application engineering classes, and this goes for the development process as a whole. You are not valuing quality here.
Dear Matt, thank you for your clarification but I have the impression that you are trying to justify yourself with "blah blah blah" when it would have been simpler and more honest to admit that you did not fully test your product before its commercial launch, notably its compatibility with TSW2 and TSW3 locomotives in freeroam mode. Do not forget that we are above all DTG’s customers, we had confidence in your statements when we purchased your product. So please do not disappoint us.
Spawning some trains have the throttle set to neutral not off preventing the master key from being turned on.
This has so far only happened on class 166 and class 45 spawned in the trains sat down Master key won’t turn to on because the reverser is set to neutral it needs to be off, on most trains before the master key will turn. And because the master key is off the reverser won’t move.
I am dissapointed by the attitude of DTG: my ticket opened on November 9th concerning the issue of the impossibility of running the GP38-2 and SD40-2 has suddently been closed by a guy called "Rafal" without any technical explanation and solution!!!!!!!!! Strange attitude, maybe they can't solve the issue, maybe the guy called "Rafal" never spawned a loco in the game I wonder if there is an engineer really working on fixing the problem? Maybe they buried the issue
A class 484 would release brakes but not move after spawning at 10:00 at Victoria. The unit runs on 750V DC - is there another reason it will not work or is it just an in-game technical problem?
Haven't touched the game for 2 months now, but I see there's been multiple patches. Have the bugged diesel locomotives been fixed for free roam yet? Wish I could get a refund for this broken game.
I went on free roam yesterday, the 313 didn't spawn at all. I tried to spawn it on NTP in the Bury platforms at Manchester Victoria but they failed to spawn.
The spawning breaks are due to Addon Manager failing to mount the content. It's the same exact issue as was plaguing Scenario Planner, but now it has spread into Free Roam too due to the Formation Designer code being added.
I don't know whether this is related to the Spring Core Update, but I spawned a 150 into GWE to drive from Slough to Pad. The AWS and Vigilance wouldn't allow me to cancel so it went into emergency stop. I had to disable them. Also on the approach to West Ealing on the Up Relief passengers were spawning at about the height of the OHE on the Down Relief and falling onto the track.
That's problably not happening because you are trying to spawn an electric train on non electric tracks
Can I get a little more info as to which routes you are trying to spawn items on, also is it in full free roam or timetable, I'm trying to re-create the issue you have
Yep, also finding this on the 150 in free roam for PS5 and it was defo working last week i.e. pre update
