PC Tsw 6 Enhancement | Lighting & Graphic Ep V6.1

Happens to me with Nvidia 5090 on this route

 

So, it's probably not the video card. It seems like a minor issue, but it keeps distracting me. If Jetwash can solve it, we should definitely erect a monument to him for his services to TSW.

 

From what we can tell this is an issue on all routes, and is because the ballast mesh pokes above the sleepers to represent stones scattered along the line. It is this that you are seeing drawing in in front of you.

So, to re-iterate, it is no different on Medway Valley to Southeastern Highspeed as it is the same track (given we had to build off the CML section). We are looking at ways to fix it.

May I suggest in the meantime you try increasing the r.viewdistancescale= setting somewhat. Beast is set to 2 and it’s not something I particularly notice. You could try 3 or 4 if your machine can cope with it, but bear in mind this forces better draw distances for everything.

 

No, I don’t - it’s an Nvidia 5080.

 

Try this
[SystemSettings]
ts2.dbg.Track.SleeperViewDistanceScale=0
ts2.dbg.Track.SleeperViewDistanceScaleMax=0

You will have to set Engine.ini to write protect if you want to keep this setting

 

Unfortunately, there's no noticeable difference, even if you select a value of 10. I did my own little test. This flaw is present on all routes, but on other routes the gravel is so perfect that it's not noticeable. I tested it.I looked at Frankfurt Fulda, Liberec Stara Paka, GWR and East Coastway remaster + Riviera line.

 

This is exactly what I was looking for. Is it possible to write these commands into a dynamic INI specifically for MVL and SEHS?

 

Sorry no Idea I expect some one can tell you

 

It will be, yes

 

I have the same problem as vodka#2734, even using the JetWash ini-file for optimaziation.


I did not notice that on any other route before and my tests delivered the same results as for vodka: not noticeable on other routes but on the MVL. I did not test SEHS yet.

 

Is there a way to combine imperfect ballast as the default on the route, but have it disappear much further than it does now? I'm no expert, but changing the values of these commands other than 0 and 1 doesn't make sense. The draw distance does not increase.

ts2.dbg.Track.SleeperViewDistanceScale=0
ts2.dbg.Track.SleeperViewDistanceScaleMax=0
Add these commands to the route's ini file. The problem will disappear.

 

As I am not an expert on those things, please help me with one question: I have one engine.ini file but struggle to find inis, specific for one route. Can you "guide" the way?

 

Yes. Use my mod and all is explained in the manual

 

Well, I do use your mod and tried the following. Sadly, it did not solve the problem.
- the general engine.ini is modified as described in your manual.
- I copied the Godmode.sav into the directory as indicated.
- I added the two lines above to the MVL part of the godmode.sav (in your manual you wrote "godmode.ini" but I did not find a file with this name).

Nothing changed. Would love some help.

 

In the upper right corner of the god's mod is an icon with the word "INI." This is what it looks like on mine.

 

Hi everyone.

I don't know if anyone can help me, but I can't find a solution for the freezes that occur on all the routes I run.

I'm using the ultra settings, Lossless Scaling, and God mode, but every 10-15 seconds the game stutters. It's not a micro freeze, but it's something around 1 to 2 seconds, and it really irritates me because I don't have a smooth gaming experience. I've already run the route several times to clear the cache, and it still happens.

My specs are:
Ryzen 5 5600x
RX 9060 XT 16GB
RAM 32GB DDR4 2666Mhz
1TB NVMe SSD

If anyone can shed some light on this, I'd appreciate it.

 

Did you add -dx12 in the startup settings in Steam?

If so did you try without lossless scaling? You can try AMD Fluid Motion Frames what is the same solution but way easier to use.

 

You can also use smooth motion in the nvidia application that works the same for TSW.

 

I’d agree with the above. As fantastic as lossless scaling has been, I now use Nvidia Smooth Motion as it is an all round better solution and more reliable.

 

I tried the settings you recommended, but the game isn't running smoothly with AMD, and I was already using the -DX12 command. Thanks for the tips, everyone.

 

Try to remove the gpu driver With DDU Driver remover (Full Clean Removal) and update to the latest version is my last advice. I have no clue whats wrong here.

Download DDU here:
https://www.guru3d.com/download/display-driver-uninstaller-download/

 

Requires an RTX 40xx (or better) GPU and the latest drivers.

 

I don't know what type of monitor you're using, but I have found with my 240hz one that limiting my desktop to 60hz and setting the max frame rate in game to 60 gives a much smoother experience than setting the desktop to 240.

 

JetWash
Okay, so I was just about to test the new version of the mod, and I tried it on Dresden Leipzig. I’m honestly a bit shocked by what I noticed there. The difference between the old mod and the new one is really extreme and not in a good way. The new version shows a lot of micro‑stutter, unfortunately.

I don’t know what’s causing it, but check both videos and you’ll clearly see what’s wrong. The red line is constantly visible, which indicates micro‑stutters, and both recordings were made twice under the exact same conditions and at the exact same location for 45 seconds.

How is this possible?! I haven’t tested other routes yet, but this alone is bad enough for me to switch back to the old mod. I never had any issues before, not even on the Medway Valley Line.

Maybe it’s an idea to revert to the older version and only change things inside the godmode.sav? I suspect the stuttering might be caused by the many changes made in the Engine.ini file. If you can reproduce this, great that would really help. If not, I’ll stick with version 6.0, because the difference is simply too big, unfortunately.

Here you can see the old version 6.0:
https://streamable.com/jbv1a8

Here you can see the new verion 6.1:
https://streamable.com/u31fbk

 

My guess is that the old version's garbage-disposal routines worked really well at limiting stutters; however those .ini lines conflict with DTG's recent optimization work, which I would reckon make use also of improved junk clearance, but in a way that's incompatible with the old JW .ini, and thus cause crashes

 

I can not confirm that in any way! For me the old mod works perfect with no issues at all so i'm confused now?!

 

The mods are identical except I removed the memory streaming and garbage collection elements. I’m sorry, but at this point I simply haven’t got the capacity to deal with this right now.

 

No worries at all, totally understandable! I’m just reporting it and for now I’m using the old engine.ini parts together with the new godmode.sav, and that combination works perfectly.

So there’s no rush on my side it’s just for your information. Take a look whenever you have the time. For anyone experiencing the same issue as I did…

The old engine.ini together with the new godmode.sav seems to work fine and gives much more stability in the game. If anyone needs something from version 6.0, I can make it available if necessary. Just let me know if you have any objections to that JetWash

 

Okay, I’ve now tested it on the Medway Valley Line as well, and indeed it does cause a crash:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000000000000010d

It’s a shame that this is happening now, and that the only real option is to stop playing the Medway Valley Line. This basically trades one problem for another. I also don’t really understand why all of this is necessary for PC, because for me the game actually runs just fine. But anyway…

In reality, you can’t run the PC and console versions side by side anymore. If you decide to implement performance updates specifically for consoles, what does that actually achieve on PC? In my opinion, very little.

Making the PC slower and worse just to make the console look better?! That’s insane, isn’t it!

 

Using Jetwash’s High setting and working great here, including Medway. I have had occasional issues in the past with Ultra High and Beast on heavy routes like Birm-Crewe, so I just stick with High these days as it looks good and doesn’t upset TSW. Fire and forget.

 

Yeah but you talking about the 6.1 version? You did not experience less performance? That should be due to missing things those are very needed for less stuttering

 

6.1 is as smooth as silk for me

 

My videos shows a diffrent situation i have no clue whats wrong there then. Can you try Dresden Leipzig by any change? Maybe there is something wrong with this route. I don't l know if you have test that since the 6.1 update?

Anyway i have an work around now....
I have clean the engine.ini in the my documents folder and i have add all the stuff in the game section so i have only the Medway Valley Line with the new 6.1 data the rest the 6.0 version

 

Due to the poor optimisation of many German routes, I'd say the issue lies there. I'm personally having no issues with Beast on a 4090, it's silky smooth.

Blaming a developer of a mod for micro stutters that they have no control over is like blaming a tyre fitter for you hitting a pot hole and getting a flat tyre.

If you're getting micro stutters you're pushing your PC past what it can comfortably handle.

 

That’s not fair, what you’re saying! I’ve clearly supported my point with two videos that show exactly where the problem lies. The videos show a clear difference between version 6.1 and 6.0, and no, I’m absolutely not “blaming” Jetwash. I’m simply pointing out an issue I’m running into. I find your reaction really strange and honestly quite unkind. I’m very happy with Jetwash and always have been.

The point I’m making is meant to improve the mod, not to point fingers. At most, I’m pointing at DTG for not improving the PC version and for the fact that they should separate the console version from the PC version, like all major games do. You can’t run a PC and a console version together they are two completely different types of hardware.

 

So, you simply took the missing lines from the engine.ini and added them to the specific Leipzig-Dresden route ini?

 

I'd think what vodka says would be the best option to get all routes working smoothly if you have issues with stutters on 6.1 v 6.0. Take the streaming and garbage collection lines out of the engine.ini (so they don't crash Medway) and add them to the dynamic route specific sections in godmode for any routes that you have the issue with.

 

You’re absolutely correct, and that is 100% the best way to deal with it. That is the beauty of GodMode.

There’s a few things in play here though;

1) Those lines have caused crashes for me on ALL routes post TSW6
2) There is nothing at all that we have done to Medway that is any different to any other route regarding this stuff. The only thing is that a small number of the lighting tweaks have been applied but that is lighting, not performance
3) The improved performance on MVL on consoles is simply a consequence of it being properly optimised, both asset and texture wise. Nothing else technical to do with memory (or whatever else people imagine we have done) has happened

As always, things that mod the game can have unintended consequences and they may be stable one minute but not the next. Developers can’t be making content based on whether or not it works with a mod, even if the mod is made by one of the developers. It just doesn’t work like that. Additionally, those changes also only benefit PC, they in no way make it worse.

 

I have removed all stuff from the engine.ini and put them in the game it self. I can now control there what is working and what not. So for the Medway Valley I have the 6.1 part for other routes the 6.0 and when I see other routes are infected in the future I can switch easily now

 

Yes including the latest 6.1 version. Smooth and no crashes here.

 

Also running 6.1. I have it capped at 60 FPS and it's as smooth as ever.

I did 3 runs on Dresden Leipzig last night. First I got the usual shader compiling (as I recently did a clean install) 2nd and 3rd were very smooth. No idea what Nvidia driver I'm on and can't check as I'm away for Easter, but for certain it is not very up to date as I avoid updating things that work.

 

I can only speak for my own setup, but for me, the lines removed have no discernable impact on the stuttering in the game.
Your mileage may vary, but I really notice very little difference, if any, with them in or out.
The biggest change for me has been the use of Smooth Motion. I now lock my FPS at 45, and smooth motion delivers a constant 80-90 fps, Allowing me to up the screen to 150%. Almost eliminating the dreaded shimmering.
FWIW, my system is I5-12400, RTX 4070 super. 32G DDR4 1440p

 

Doesn't have to be the latest.... the 40** cards were given SM support later than the 50** series from driver 590.26 so anything after that enables SM on the 40**.

I'm currently on 591.86 as there are a good few of us 4070 owners that have been suffering from screen flicker in games (TSW for me) when using any of the current 595.xx branch drivers (either game ready or Studio versions)

 

I have updated the NVidia driver for my GeoForce 4090 and enabled Smooth Motion and after a run, do think it has made a difference in the running of the sim.

 

Use Alt + r to bring up the smooth motion overlay. It will tell you your FPS and if Smooth motion is active and working correctly.

 

Thanks to those who called out Nvidia Smooth Motion above - I'd previously used LS, but having done a few runs with Smooth Motion the difference in quality/artifacting/general smoothness is night and day.