It is day 24 since the April 28th core update and we all are still are having issues, some major (game unplayable), others with minor annoyances (some DLC unplayable). Will our patience be rewarded soon?
Which "Game Unplayable" do you refer to? As mentioned DTG are working on a Fix https://forums.dovetailgames.com/threads/train-simulator-classic-launch-update.69927/#post-654923
Several are still reporting that the game will not load at all, or run in 64 bit. Others reporting increasing OOM issues, crashes and scripting errors. I am aware that DTG did state that they are working on fixes but this is now day 25 and they are still cranking out DLC and patches for routes but not the core game. They have effectively "taken" the game away from quite a few people by this core "update". The proof of concept is that it worked before the update. Sadly this all could have been prevented if it was released as a beta with a revert option. This way they could have collected input from a variety of players on different systems and made adjustments before subjecting the entire community to results of this "update". IMHO a very poorly executed and thought out rollout. I can fix some of these issues my self but I am hesitant, not knowing what havoc the next update will bring. I know that you are a DTG supporter and generally so am I, but in this point I hope that there is some consensus. Make the next one a beta release, please!
The issues reported need to be adressed - and rushing things won't help anybody. I'm playing the new version with DTG content only atm, which is very stable. The rest I'm playing from my backup using v72 core. Just be patient.
I have no choice but to be patient. Finding more broken things on a daily basis. The sad thing this could have all been avoided. In the words of that most articulate baseball player Yogi Berra, it's Deja vu all over again.
That's why I made a core backup to secure play in troubled times What's interesting is, I've not yet come across a bug related to the core with any DTG route I've played in default 64bit - it is as if they were keeping to coding and blueprint standards, and some 3rd party devs crossed an invisible line which hopefully can be pinpointed. Then, the issue with the injectors accepting a maximum value of 15 (0xF) seems like a typo in the code to me, that's just a nibble (half-byte) maybe accidentally masked, AND'd or declared wrong. (Just vague speculation) For example, from my experiences, as much as I praise G-Trax, there's always some "glitches" to be found in their assets, be it duplicate entry IDs in their blueprints, typos - and Stevens Pass has a building missing the texture in winter (probably no one noticed it, fixed that). Concerning 3rd parties, I've found Taurus Mountains to play well, also Boston Albany. Haven't had time for more testing yet though.
I've had no issues since the release and use a variety of payware and freeware (UK-focused) including some assets (Incl Locos) that date back to 2008. I realise that this isn't helpful to those who are suffering problems - but I'm throwing it in to give some balance. Having said that, I agree that providing a fall-back option might have been nice (British understatement). DTG have followed a more user-controlled approach to DX12 which has consequently raised fewer hackles in the community - but probably given less usable feedback too. If they are to build on the new core then they have to know if it is stable - otherwise whatever subsequent improvements they make will always be bedevilled with complaints from people with unrelated core-based issues. IMHO the majority of the new core bugs are down to issues in 3rd party addons and DTG cannot be held responsible for those. My final thought; if it hadn't been for the images issue causing real immediate pain then how many actual errors have been reported with the core release? My guess is - 'not many'. Given the scale of what they have done (for free) I've been impressed.
What I've gathered: (DX9 64-bit) - Headlights not working (ALCo DL-109) - AFB on virtualRailroads Pro Locos not working - Uncoupling freezes game (Montana Hi-Line) - Steam injectors not working (quick fixes released by developers) - Savegame issues, disappearing locos - Trackside "4" camera still broken - various Lua scripting incompatibilities These issues are reportedly affecting everyone. Let's see what the next core update will bring.
We had a update on how things are going on the 18th, when we have more news we will keep you updated, https://forums.dovetailgames.com/threads/train-simulator-classic-launch-update.69927/#post-654923
I have probably been lucky, the main issue I had was after trying DX12 version the screen size reverting to a little 1920 x 1080 box in DX11 64 bit with no option to restore UHD resolution. Eventually got round it with a devil of a job. Most of my previous save games no longer load, just return to the main menu. When I started a scenario on Stainmore Summit, the loco was sat stationary, brakes on and showing as experiencing wheelslip, when it patently wasn't. Probably a scripting thing.
For clarification, I was relating to the standard DX9 64 bit version - DX12 is still experimental and optional and has its own feedback thread.
Day 38, I will not purchase any DLC unless this is fixed properly. Filed a complaint on Steam against DTG. They have effectively removed some 3rd party content from the platform by breaking the scripting and making it unplayable.
Please be reminded that this is probably, content-wise, the biggest game that's around. The reason it takes so long is probably testing all available DLC - I have found no issues with RSC/DTG content, and the game is the most stable it has ever been. And also be reminded that for removing the OOM, the engine is probably more strict about bad assets - and there is a lot of sloppy 3rd party stuff containing typos, duplicate blueprint IDs, people just did not keep to standards. This resulted in TSC running these, but often just quitting with the infamous OOM at some seemingly random point. Pushing for a deadline would be counter productive now. I can wait until I'm running virtualRailroads locos again, apart from that, there's no issues for me. The menu image bug was fixed quickly. And if something really wouldn't work - which might be the case - I play it on the v72.3b backup. You can have as many installations as you like.
As I have stated repeatedly, this should have been a beta that could have been reversed. With all the unknown consequences this would have been the prudent way to go and we would have been left with all of our DLCs in a playable condition and not 38 days later in this mess.
I agree that it should've been released as a beta. It wasn't, and that was foreseeable and that's why it was recommended to make a backup (just the core files) The reason why it takes so long is an indicator they'll want to make sure everything that's being sold will work - having only testing their own content before initial core update release. And I know how much time it can take just to test a single loco in various conditions. Who knows - maybe a bunch of DLC must be udpated too. Still I wouldn't call it a mess. A few locos do not work, that's bad, but they are working on it. And then there's that issue I've often pointed out with G-TraX PennSteam/BLE terrain texturing blueprint which is so badly composed/copy-pasted that it will sooner or later stop working in future versions because it clearly is breaking rules. It broke the route in 2022 for me until I manually fixed the blueprint. https://forums.dovetailgames.com/threads/g-trax-pennsylvania-steam-from-rwa-oom-solved.51964/
Tis the wonderful age of order from the comfort of home, same day deliveries, almost instantaneous high speed downloads, wanting for nothing because Mum and Dad both work and guilt buy their kids whatever they want just so long as they aren't required to do any time consuming real parenting. It's also the age of spoilt, self entitled, self important impatient children that demand to be treated like adults.
I take umbrage at your assumption. A child neither I am. Patience I have along with aged wisdom. A situation that was preventable deserves noting. I have, I will call them out. This is not the first time this has happened with DTC. I have over the years replaced the mediocre stock with better rolling stock better repaints, advanced scripted locomotives,and better sounds and effects. While the supplied DLC may be working a lot of the advanced scripting is not. Just roll it back while you futz with it is all I am asking. Release the next update as a beta to keep this from happening again.
In the same way Microsoft, Apple, Google, Firefox etc release all their updates as betas? They don't.
rwaday Have you read this post? https://forums.dovetailgames.com/threads/train-simulator-classic-launch-update.69927/#post-660389
Installed and all known issues have been resolved. You can't compare DTG to Microsoft, Apple, and Google. BTW All four do have betas that you can opt in to. I have done so. Happy to have it up again but still does not excuse the manner in which it was released without all the unknown repercussions. Reports of new issues that now need to be addressed. Hopefully can be done more expeditiously without causing damage to those things that v74.4a has fixed.
Don't believe every "bug" report - especially not those on the Steam forums. Latest I saw was that the AP Class 37 was broken. Which is not true. False rumours spreading fast... I'm happy with the update, and when virtualRailroads AFB is fixed it's pretty much done - I heard a lot of people complaining but no specific details what else exactly would not be working, mostly the usual rants. So DTG can focus on the next step of TSC's future, DX12. Again I do recommend everyone to keep their backup v72.3b core files in case some locos refuse to work and the developers are far away over the hills. If you have that backup, start RailWorks64.exe directly from that folder and it will work. Just copy Assets and Routes you need there from your main installation. (Not verified yet, but AHS Eurotunnel (3rd party, non-Steam) could be such a case. Only if the dev reveals the source scripts to DTG the bug can be located.) And another option would be talking DTG into providing a link for the old core (it's only 330 MB zipped) here on the forums for those - of course clearly stating that they do not offer support for it. Or allow distribution of it - still you need a valid Steam key to use it, so it would not be piracy. But then I'm not an expert on legal issues. Edit: I've contacted AHS. Hell these endless captchas are difficult!
Day 67 since the April 28th update. DTG is plugging along applying patches and fixing issues with their dedicated group of professionals with the help of 3rd party developers and knowledgeable TSC forum members.Thanks to the members of other TSC forum members and developers for making patches to make routes playable in 64 bit mode and DLC playable. It is both a labor of love of the game and customer satisfaction achievement that allows this consortium in solving problems. Thank you for your continued efforts.