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

Very good thanks!

 

Thanks gang

 

I have now updated my Lighting Enhancement engine.ini mod to include all TSW6 routes except (I believe) Heilbronn which I don't own.

This version of the mod has not been tested so I can't account for typos etc but it should absolutely be compatible with all routes, including Medway Valley, stopping any ini related crashes people have been having. You must update both the main engine.ini and GodMode save as explained in the accompanying manual.

Should there be an error in the mod I'm happy to correct it but I’d like to clarify, should people still wish to use their own ini setups, or ones made by others and still encounter crashes at any point with TSW6 then that is obviously your own choice. I will not be providing any more support in these circumstances for those suffering crashes related to engine.ini modifications.

The updated mod can be found here:

TSW 6 | Lighting & Visual Quality Enhancement vTSW6.1 - Train Sim Community

Enjoy

 

Works great for me, thanks very much JetWash for finding time to do this, much appreciated.

 

Very cool! Thank you so much. This will make the Medway Valley even better. What a super nice route is that

 

Thank you Jetwash for this update. The manual still describes the old configuration:

r.Streaming.PoolSize=
r.Streaming.MaxTempMemoryAllowed=

That's no longer necessary, right?

 

Oh balls. Yes, you are absolutely correct, those are some of the lines that have been causing crashes for me in TSW6.

I’ve updated the download page, thanks for spotting that.

 

Updated my engine.ini to your latest, nothing else custom in there. Updated the GodeMode save file and GodMode pak file, still getting crashes.

 

IGNORE THIS! I went back and took another look at my Engine file and I somehow messed up the copy because I still had the streaming lines in there. My mistake but I’m glad it was. Fixed now, and checked, will try again tomorrow.

 

I’m almost certain that the lines that I have removed that relate to memory streaming, garbage collection and a host of others are to blame for the crashes. This started happening for me the minute TSW6 was released and I’d long since removed them. Once I did that my game has been rock solid since across all DLC.

It is imperative you copy across the text in it’s entirety and overwrite what is already there making sure you save it when you have done so.

 

Thanks for the update, JetWash!
Does that mean we can now enjoy all your optimisations to the routes as before AND enjoy the new MVL without the need of changing anything?

 

Well, you need to update my mod to the latest version as described above. I can only guarantee what my mod does, and using ini settings from elsewhere is likely to cause unpredictable results.

 

I have loved this Mod for years and now I have the perfect route to go with it. I extend my gratitude to you and the whole team at Firefly for all you have done!

 

Are there any ini-lines to make shadows less contrast(lighter) especially in the morning/evening hours without changing the brightness of the game? Maybe there is a command that changes the color of the shadows to make them lighter? Or a command that disables shadow multiplication when they overlap?

 

I thought DTG gives keys to all DLCs to its developers.

 

I have a problem. The ballast is loading right in front of the train. Is there a way to fix this, or is it some other mod interfering with it? I launch the game without this mod, but it doesn't help. This problem is especially noticeable in bright sunlight.

 

The track on MVL is the same track as on every other route in the game for what it’s worth.

 

I wouldn't say it's a MVL issue, it's just that I've started playing it now, and because of the high number of sunny days, it's really noticeable. I don't use ballast mods. Maybe there is a way.Maybe there is some parameter that can help?

 

Your most recent mod versions "godmode.sav" file breaks the Zoomier Zoom in Foobians mod. I've tried the "godmode.sav" file from both the beast and ultra folders and while the Foobian interface loads the only way I can get the Zoomier Zoom to work is to remove your godmode.sav.

 

We’re looking into it for MVL because what we see in the editor and what some (not all, not me anyway) people are seeing in the game is not the same thing. Will keep you posted.

 

I'm pleased to report that removing those lines has finally cured the annoying crash on Birmingham-Crewe that I last mentioned a couple of weeks ago.

Incidentally, I'd cured the crashes in your previous version by adding in a line from the SEHS settings that wasn't in the Birmingham to Crewe ones, namely r.Shadow.CSM.MaxCascades=4 - out of interest, any reason why that line is in some routes but not others?

Anyway, I can now finally enjoy Birmingham to Crewe with your mod, at 1440p and a decent framerate, and no crashes. Huzzah!

 

Honestly, I’m not sure. Keeping track of this stuff is getting increasingly difficult to be honest.

FWIW Birmingham to Crewe and Riviera were routes that were crashing for me with those lines in the ini. The core is constantly changing and they are no longer robustly safe to use in a mod. I also believe they are no longer necessary as the game is much smoother now than it was 18 months ago.

 

That would be great. Other routes suffer from this too, but not always.
P.S. Thank you very much for updating the mod. Liberec - Stara Paka has become much better. FPS is much more stable.

 

Thanks, and thanks again for updating your mod; couldn't be without it!

 

Query about Lossless Scaling:

On my old machine, this magic utility was the only thing that made it possible to run TSW 4+ at all. But now things are a bit different- with a 180 Hz monitor, even in Mode 3 I'd still be driving TSW at 60 fps, which really seems to defeat the purpose of the exercise. Have I outgrown it now?

(Ryzen 7 9800X3D, RTX 5070, 32 GB RAM, 12 GB VRAM)

 

Do you by any chance have an AMD graphics card?

 

Yeah I have a amd GPU with this problem... Is there an option to fix this? I have seen this on different add-ons.

 

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.

 

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/

 

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