Train Simulator 2019 is available now

[wacampbell]

BoostedFridge> FPS counter displayed 17fps,

Not terrible considering the density in that scene.

[Caffeine]

I've always kept Steam and most of my larger games on other partitions and drives from C:, so the refresh process will leave these untouched.

In fact, it should be a golden rule.
Overloading the less possible the operating system and its partition.

[trev123]

This is what updated for me plus 5 scenarios in the contents folder. A 2.4gb download.

[ET44C4]

Screenshot_Portland Terminal_43.65622--70.25201_17-02-44.jpg

I ran the 64 bit version for the first time today. Before the upgrade, the street running section of the Portland Terminal had very low frames, even without running a train. Now, it runs smooth.

[BoostedFridge]

ET, has the actual frame rate increased for you, or is it just playing smoother in game?

[ET44C4]

ET, has the actual frame rate increased for you, or is it just playing smoother in game?

That's a good question, Boosted. I will take a look at both versions and see if the frame rates did indeed increase or not.

[ET44C4]

Okay, I checked with both versions and it turns out you right. Using 32 bit, the frame rate averaged at 15 fps. On the 64 bit version, frame rates were in the 16-20 range; this time much smoother, but not much of a difference regarding frame rates.

Thank you for the insight, and sorry for providing false information!

[BoostedFridge]

Okay, I checked with both versions and it turns out you right. Using 32 bit, the frame rate averaged at 15 fps. On the 64 bit version, frame rates were in the 16-20 range; this time much smoother, but not much of a difference regarding frame rates.

Thank you for the insight, and sorry for providing false information!

It's all good man. If it wasn't for notes I took last week, I would have made the same observation. Regardless of what the FPS counter says, the game running smoother for the user is what is really important here.

[dr1980]

Yes, consistency of frame rates can be more important than the frame rates themselves. Interesting observation.

[mikesimpson]

No bat file here either, the luac.bat is a completely different thing.

Had no problems running Railworks64.exe from a desktop icon though, but had to run it as administrator here, would not run by just clicking on it. Have fixed this by right clicking on icon, selecting Properties/Compatability and ticking the box 'Always run as administrator'.

As another point, if you have previously used RW_Tools to change rolling stock in scenarios, you would have had to extract RouteProperties.xml and ScenarioProperties.xml files to do this. The TS2019 update has removed all of these extracted files, so you might need to use RW_Tools again to fix ones that no longer work (or of course if you had backups, you can fix everything by just copying the backup files).

Mike

[peterhayes]

Mike
I have all of my extracted (outside the .ap file structure) routeproperties.xml and ScenarioProperties.xml files all intact after the TS 2019 upgrade.

None have been removed as can be seen in your case.

It has been quite a strange update.


pH

[GSkid]

So I did some quick tests on Cajon Pass, Pacific Surfliner, Donner Pass and Stevens Pass at..... x8 AA..... 1x2 SSAA and 3x3 SSAA..... with all settings maxed, same trains and with both cab/outside camera angles. In most cases my frame rates increased using the 64-bit version.... with Cajon Pass getting a 21fps increase!

I haven't played with it long enough to see if it's cured any stuttering, but I'll pipe in if it has. So far so good!

[KevinWS]

Mine updated today.

Tried 64 bit and while it didn't hang, all I got was the startup screen as an icon when I hovered over the TS icon that opened up in the bottom bar. And the start-up sounds. It was running as I watching the disk, memory, cpu useage etc.

After 50 mins it was still loading! Tried 32 bit with a similar result.

Will leave it to the weekend now, as I am busy at the moment. Was just curious to see how it would work...).

[buzz456]

Try the verify. Obviously something is amiss.

[jalsina]

So I did some quick tests on Cajon Pass, Pacific Surfliner, Donner Pass and Stevens Pass at..... x8 AA..... 1x2 SSAA and 3x3 SSAA..... with all settings maxed, same trains and with both cab/outside camera angles. In most cases my frame rates increased using the 64-bit version.... with Cajon Pass getting a 21fps increase!

I haven't played with it long enough to see if it's cured any stuttering, but I'll pipe in if it has. So far so good!

I have been playing TS2018 in the last couple years with an Anti-Aliasing setting of FXAA+8xMSAA and Anisotropic x 4 wich gave me a good graphics.
With RailWorks64 I have been experimenting with all SSAA, mostly the 3x3 SSAA, using Minerman´s Bergen Line. And I notice a more smooth game with slightly better FPS in these more complex SSAA. I can´t find a fps improvement with FXAA+8xMSAA.
In The Bergen Line when you transit the flora scenery you note a smooth game with never seen before fps (better). In the dense urban areas, the smoothness is still there, but the fps don´t seem to be improving.
I am now playing with Scenery Quality and Shadow Quality rulers totally to the right (which I did not with the 32 bit). I also use Anisotropic x 8.

However at the beginning of my tests, I experienced a weird crash with 3x3 SSAA using Zawal´s Montana Rail:

error1.jpg

The lack of MSVCR100D.dll (which can be downloaded) is only a problem related with the Crash sender, but not the TS2019 crash itself. It has to be in this folder:
...\RailWorks\data\CrashReport\x64 so I downloaded and installed it there.
I don´t know yet the reason of the TS crash and I haven´t been able to replicate the crash or know the cause of it (route, train, AntiAliasing setting, etc)