As a side note, I know it was mentioned by DTG that they were looking into implementing it and it looks like they did.. When you restart after a graphics settings change or clearing the cache it now restarts in 64bit not 32bit as it always used to before.
There is a small tweak, rename the Railworks.exe into Railworks32.exe and make a copy a Railworks64.exe into Railworks.exe. This way, the game always starts with the 64 bit executable after a restart from the Settings menu. You now have to start Railworks32.exe by hand if you really want the 32 bits version.
That's my point, you no longer need to do this workaround (which I myself posted a while back here btw)
After the update basically all my AP content, searchlight and a few other mods got wiped (sound packs, tracks, weather etc). Anyone else have the issue
I doubt the bugs won’t be fixed, DTG were immediately transparent with their process and released an article and addressed the bugs that they will be fixing. And for the first step for future major updates, it’s a low possibility they’re going to just leave this one as is with all the bugs still there because for one, the team at DTG seem to care about this and future updates and they’re putting lots of hard work and effort in to make the game better. It just seems this first update was a misstep and will serve as a lesson for future updates when the bugs are hopefully fixed. Also it is speculated that the reason in the first place for the announcement being made for this update and future ones was some kind of requirement with the Focus Entertainment purchase as this whole thing has happened close to the announcement of Dovetail Games being purchased by them. But I am not 100% sure of that, after all it could just be a coincidence in timing.
I did loose a couple of things. AP weather was strange, Some of my costum camera cabviews got wiped. And signals on RSSLO routes were suddenly unusually bright.
File verification will be the cause for most of that, so you'll need to reinstall those mods. I also theorised with my friends that these updates for TSC are to make the company more appealing to buyers, as they can say they have two different train simulators that are supported and popular.
If TSC does not get updated, then it’s only a matter of years before it wont run on new hardware/os. If DTG (or anyone who owns the code) wants to sell it to the users, it’ll have to work and it’ll need maintanence. The company already has been sold to Focus, so really that’s a moot point.
Just because DTG says they will do something does not mean they will actually do it. And the problems with .lua files, arguably the most serious issue, they have explicitly made no promises on fixing. There are many ways to keep old programs running.
As far as i am aware, its only a small handful of third party addons having issues with Lua scripts. So probs not at the top of their to do list at the moment. Non the third party stuff i have that relies heavily on Lua is having any issues that have ruined the driving experience. Given that its only a small number affected compared to how many there are, i would be willing to think that those addons original script wasn't actually correct but a few small errors in the code somehow did correct the result. So far i believe its only the Smokebox stuff affected, and they have already come out with a temp workaround.
Just set your Steam Client to start in the mode you want - 32bit or 64bit - just a matter of picking the option.
But still a handful compared with the large amount that DTG have made and sell. There is a lot of third party stuff that works without problems It has been said that the updating progress might cause some problems.
It is not an Excuse. It is a statement of Fact. DTG have said they will look in to the problems and after the first day a message appeared on the Help Section https://dovetailgames.freshdesk.com...99-how-to-fix-the-tsc-menu-crash-after-update Which do you think DTG should look at First? A problem affecting 90% of Players or a problem affecting a smaller amount? There are a lot of players that only buy from STEAM - even if available elsewhere. Somebody I was speaking to the other week likes the vR BR101 but would not buy other vR Products as he could not get them on Steam.
It is completely impossible for DTG to have found every single bug in the update. There is nowhere near enough capacity for them to test everything, especially stuff they're not even responsible for. It was pretty clear for a long time the update would have some minor issues with it and most people understood and accepted that. The issues with LUA scripting affect a small amount of trains. From what I've seen, none of them are from developers who can't update the content to work properly. DTG are already working on an update for this and other issues, and the developers of the affected content can work something out if they see fit.
The problem with the injectors has absolutely nothing to do with my LUA scripts, which continue to work perfectly all the time. I narrowed the problem down to something wrong in the way the core code now deals with the injector size value in the engine simulation blueprint. I had to change it from 78mm (the correct value) to 15mm just because 78 now causes the injectors to stop working. Again, nothing to do with LUA.
Exactly. That's why they should have used the Steam beta feature to let the community find bugs before pushing it out to everyone.
They hadn't when I posted that. But I see the Support Page has been updated today since I posted, no doubt I will get that update next time I fire up. Update: Yes, now updated and all working as it should be. A big THANK YOU to Dovetail for resolving this issue so quickly.
Are there any updated developer guidelines available? Or is it guesswork? virtualRailroads' pro locos also suffer from non-working AFB...
I didn't say they did. There is an argument for that, although there are issues with that as well. Railroads Online gets most of its updates in the beta branch only (I'm not sure how far behind the main branch is now, but when I played it frequently it was several months behind - this was before Astragon got involved in the project, when the work ethic was terrible), and as a result the majority of players play RRO in said branch, so it isn't really a beta branch at all. Depending on how DTG do the upcoming beta branch it's entirely possible they accidentally make an unstable main branch, because people will always prefer to play the latest-and-greatest version. It also means that bug fixes will need to be released for yet another version of TS that handles things differently, which is in part why the new update has had basically no benefit to 32-bit players. I know I won't be playing in the beta branch, unless DTG start putting major new features in it.
For those that are curious but mostly for those that don't want to copy over the whole Steam install to their isolated playable game and have to reinstall some 3rd party content that gets returned to default (i.e. me)..
I think it's time for Dovetail (or whatever they're called now) to roll back to the pre-update version of TSC and then set up a volunteer beta test site. It seems like the unused code that they trimmed from TSC was actually being used by 3rd party developers, and they are going to be chasing those issues for a long time. I get it...TSC had more arms of code than the Kraken, and it's a big job trying to update legacy software like this. And I like the enthusiasm of the project manager in charge of the update. But it is starting to sound like there is tons of spaghetti code involved, where you have no idea where it winds around the plate and is being used by another company. And this is a big deal. I saw someone say at full retail all of the Train Simulator Classic DLC is about $7000.00 And another person said it was more like $12,000.00 TSC is not a $50 computer game. It is a major investment, and Dovetail can't just hose it and then start working on fixes for years to come. They could face a class action lawsuit. They need to roll the update back.
The change to the Trackside Camera hasn't worked, it's still broken but in a different way. It now only lasts a few seconds before changing to the next view, but still doesn't move as the train goes past.
How many times have the likes of Microsoft and Apple rolled back their updates? "This Windows 10 is a bit duff - we need to go back to Windows 8 " And they find errors with their products all the time which is why patches are released. When the game was updated to allow 64bit there were problems but they worked thru them and people are happy with 64bit.
The difference there is that 32bit was kept as an option. They could have done the same this time, at least until the bugs were ironed out, but decided not to.
Come on eldontom2 I didn't think you were that new to the game.. Ok DTG could have called it "Play Train Simulator 32-bit Edition" and named the .exe RailWorks32.exe but did they really need to? If it doesn't quack like a duck and it doesn't waddle like a duck and it doesn't even look like a duck then it probably in all likelihood Isn't a duck! Same principle with named 64-bit and non named 64-bit
Don't quite think that's how this works. I believe the now older version would have had to have been set up as one you could opt into via the beta menu, which I don't think DTG has ever done
Didn't miss your point as much as you worded it badly I think, it's the part where you say "They could have done the same this time" that implies to us on the outside that 32bit is no longer available. I get what you're saying now though,
There is no way the relatively minor issues with the update justifies rolling back the whole thing. A very limited amount of third party content not working as intended post update Thumbnail images causing a soft lock (now fixed) Lineside camera broken Those are the three main issues with the update. One is already fixed, one is for a camera option I last used at least five years ago and one statistically affects a small amount of the TS playerbase. I roll my eyes when I see people calling the update catastrophic, a failure, or needing to be rolled back. It's a ridiculous statement. When TSW2 got the Rush Hour update on PS4 and made the game completely unplayable, that justified anger. The Train Simulator update does not. It can be annoying at times, but anyone with common sense would have accepted the update would have issues and prepared for it in advance. In fact I think the overall success of the update surprised a lot of us, because implicit or explicitly I think most of us expected the worst.
Agreed. I'm positive and feel the dev team are working their butts off atm - yet I do critize not using the Beta option, simply because bad news ("Game is broken") are easily spread, and good news can't repair, or take longer to, the damage done to the players' trust. But I have to admit even with a beta there'd be a lot of yelling (as is with ETS2's betas - the people complaining their mods stopped working do not understand the point of a beta release and the nature of mods, that's why I hardly ever comment in the Steam forums, too many crybabies) And if in any case there should be issues with some 3rd party stuff that won't get updated (have to check the Chessie U30), I can use the backup installation to play these. And for the new version, I've created a vanilla install for bug tracing and Steam not messing with mods due to many udpates ahead which could trigger verification and would want to redownload 500GB in my case. I think next update will probably replace RailSimulator.com with Focus Entertainment in the splash screen Hope they address the uncoupling freeze that my friend KodiakJac described (Montana HiLine). So in the end: DTG, thanks for taking TSC forwards! And thanks to our great community here without whom the game could already be dead and gone! I have content to play for years ahead, and TSC never gets old for me, even after 6,000 hours now...(ok half of the time was probably bug fixing )
I presume I’m not alone in finding the behaviour of the ‘4’ camera seems to have broken since the update?
according to the SteamDB the "4" camera file has been changed, but the camera still doesn't pan. It moves in smaller increments DTG's devs working 'their butts off' could have been avoided if their trusted 3rd parties were involved in testing, which by all accounts (AP, Smokebox, Searchlight) they were not. So much for DTG's trust? Go figure ... Anyway, damage control is being done now, but one could assume the new owners' management will frown upon the staff of their newest acquisition. Still, the v73.6b gave a marked improvement in FPS on my modest PC, so that's good for starters.
“Stuff” happened with the update for sure. BUT with the performance improvement we got, for an update was just a code cleanup, and not designed at all to give performance improvements at all, imagine what could be achieved when actual work on performance enhancements has been done.
They're a business; DTG 's a business. Senior management's concern will be focused on revenue and profits. As long as the outlook looks clear that both revenue and profits will continue to grow they won't be concerned about comparitively few people whinging their 3rd party addon isn't working.
On the contrary. The very fact that there is (so much) third party stuff available, is a driving force for the platform, as well as a selling point. So DTG is ofcourse concerned about keeping third party addons working as well.
Another issue that people should take into consideration is my computer bottlenecking ie is my CPU or GPU slowing my computer down. There are plenty of ways to check this on the internet. Just use a search engine and there are plenty of topics on this and how to test. I just ran one and it told me my GPU RTX 3050 is causing a bottleneck with my Intel i5 10600k running at just over 4.0 GHZ and suggested I upgrade to an RTX 3060 GPU.
That happens all the time with min (9th Gen i5, RTX 2070 Super), so I lowered the framerate to be compatible with my 144hz monitor (36fps) and the GPU bottleneck stopped.
