PC Tsw4 Enhancement | Lighting & Graphic Enhancement V4.7 (inc Lossless Scaling Guide)

No, always TAA. FXAA is bloody awful, you might as well not use it it’s that bad!

 

Yeah for sure its bizar awful than understand your'e text wrong

 

I see what you’ve misunderstood. Even with 4K, 100% screen percentage and TAA there is still aliasing, particularly shimmering of overhead lines and fences etc. With the settings I mentioned above (which are possible because of the frame gen) it appears to have gone which is what I mean by ‘no aliasing’. Without the fame gen it would impossible to run 4K at 125% screen percentage and my ini settings on a 3090. It would cripple it.

 

Yeah with the upscaling that i use i have no shimmer at all... I use the Deep Learning version of upscaling and that looks stunning.

 

I’ve done a bit more playing around and am now running 140% screen percentage at 4K (which is a resolution of 5376x3024 & looks amazing!) with the FSR scaling at 1.1 and Frame Generation on. It’s giving me a constant and smooth 60fps and I can even start to tweak ini settings even higher.

It blows my mind that this, and other mods like it, are achieving this with software alone. It kinda re-writes the script on £2000 GPUs being needed to play the latest and greatest.

 

Are you releasing new version?

 

Not for this, no. Because everyone’s systems are different and very few people seem to use this program it’s not worth the work it would take.

I’d imagine there’s very little chance of another update now until we see where the lighting in TSW5 lands. I’m expecting to have to do a fair bit of work to make the mod compatible with the new game but only time will tell.

 

It blew my mind to. Also the fact that it is'nt well known in any community exept msfs baffels me.
I went from using your Medium settings mod to ultra with more fps and better quality without artefacts like you see with Nvidia or AMD.
A game changer for sure!

I am curous though, has enyone used my other optimization (Amit Timer Res)?
For me this made a huge diffirence, I dont have any stutters at all. I'd like to know if people are using this program and see the same results as I did or if it's just placebo as I have been doing optimizations for a long time

 

i thought those only worked with rtx 4000 series cards. do those work with the 3000 as well? and if they do where can i get them? thanks and your mod is just dope man!

 

since the so-called major core summer update along with your mod. settings remain untouched for now

 

That program works with any card and any game, that’s the beauty of it!

 

ok. gonna try to set this up some how

 

Sounds intriguing, might try this once I have gone through all my routes to register them with my new video card. It's a tedious process and don't want to install anything until its done.

 

What do you mean by "register my routes with my new video card"?

 

Goblin line is a proper stutter fest now. Cant tell if it was the update or what...

 

If you are on pc, have you noted when you purchase a new route dlc, it has a studder for the first several times you run it until it settles down. This is the video card getting used to the new route's graphics. Well with a new video card, this is every route for me, so I am running each one 3 - 4 times to do this and moving on to the next one.

 

No no update at all for this route. I have test it and works perfect here.

 

Yep, the dreaded shader compilation!
https://gameworldobserver.com/2023/04/07/shader-compilation-stuttering-pc-games-explained

 

I can pop a little guide here on how I’ve set up frame-gen in the lossless scaling program if it helps.

 

That would be interesting. I‘ve got it set up and working now, but it was more by luck!

Very impressed with it, I had my doubts about it having much benefit on a high end PC, but it’s letting me max out my monitors refresh rate and most of the time running really smooth and stutter free.

 

Ok, so you did mean the shader complation It is not tied to a new card at all, nor the new card need time to "settle down". Shaders need to be compiled every time they are deleted, either after manual intervention or most usually after a GPU driver update. So each time you update your drivers you would need to go through it again.

My advice? Don't bother, simply drive any route you want, after the first couple of runs it will be compiled. It is really a major waste of time to run every single route "just to compile shaders", when a few days later you might throw all of it away because you might want to update the drivers. Just compile them on the go as you drive wherever you please.

 

I have to agree. I see some minor stuttering for the first 10-20 minutes on a new route or after a driver update but it stops after that. 90-95% of my gameplay experience is smooth to be honest.

 

What i have noticed with a better card it brings less stutter also with a new route.

 

OK, well then, there must be something wrong in my settings. I say studders, but the first time I drive a route since getting this new machine with the GTX 4090 card, it is really multi second stops that I am seeing and depending on the density of the tile, city's worse than countryside. After running a route several time though, it settles right on down and runs smoothly. So only the first and second runs over a route are bad. This is the reason why I am doing each route, then moving on to the next. With screen resolution, no matter what resolution or windows mode I put it in, when it starts up it reverts to what you are seeing here. Though, even if I change these setting on game start, it has no effect on that first or second runs pauses. Also, I am running the latest version of the NVidia driver, 560.70.

 

yes please do. Been busting my brains (as said in high school) trying to figure it out

 

I don't understand anything of what I've just done with the Amit Timer Res thing, but... it's some kind of black magic devilry. I'm now running in x2 resolution and 125% screen size... more smoothly than I was with 4k alone...

It's astonishing the difference.

 

Since the latest update to the game and nvidia driver 560.86
Used it without windows HDR but used it with RTX Dynamic on

 

Super glad it worked so well for you.. So I'm not crazy after all lol
What timer delay did you set?

 

If I read the question correctly, for me it was 0518.

 

oh is it possible if you could post a link to this? i've searched google and have been led to other sites but I'm not sure if they're the right ones.
thanks for your time

 

It’s in this thread;

https://forums.dovetailgames.com/th...ic-enhancement-v4-7.74685/page-21#post-870883

 

I have a question JetWash concerning the enhanced ini settings and if there is a single one or several that can be altered just a little, I have only seen this happen with older routes mostly. I am just guessing here that it has something to do with the shadows.
Please see the attached images.

What I did with my daughter's assistance, was remove the enhanced ini file [Godmode.sav_v4.7] as well as the added engine ini file in the spoiler.

Ran the route with the vanilla engine.ini "sandpatch grade" also where I noticed the Flickering odd black artifacts.
When doing this there were zero Flickering odd black artifacts.

Then [Godmode.sav_v4.7] was reinstalled as was the engine.ini file and there were zero odd black artifacts.
Or could there be a conflict happening of a sort that is? After a period of gameplay time, these Flickering odd black artifacts appear.

Spoiler

[SystemSettings]
au.MaxConcurrentStreams=5
au.DisableParallelSourceProcessing=0
AudioCommand.FenceWaitTimeMs=0
AudioThread.BatchAsyncBatchSize=10
au.Concurrency.MinVolumeScale=0.00001
au.SoundDistanceOptimizationLength=0.5
au.VirtualLoops.PerfDistance=500
au.VirtualLoops.UpdateRate.Max=1
au.VirtualLoops.UpdateRate.Min=0.5
ts2.dbg.JourneyChapterLockOverride=1
ts2.save.CheckpointsEnabled=0
ts2.RewardMonitor.ShowLowImpactNotificationsAsFull=0
TimeOfDaySystem.VolumetricCloud.GroundContribution=1
r.FogStartDistance=40000
ts2.dbg.Camera.MaxVerticalHeight=50000
ts2.dbg.Camera.MaxVerticalHeight=20000
ts2.dbg.Camera.MaxLinearDistance=50000
ts2.dbg.Camera.MaxHorizontalDistance=50000
ts2.dbg.MaxFreeCameraDistance=400000
ts2.dbg.MaxFreeCameraDistance=200000
ts2.dbg.Camera.CameraBoomMaxLength=4000
ts2.dbg.RelinquishPromptWaitTime=60
ts2.dbg.RelinquishPromptWaitTime=0
ts2.dbg.MaxReskinsPerTimetable=0
ts2.dbg.SteamParticleSize=0.5
ts2.dbg.SteamParticleSpawnMultiplier=5
ts2.CameraMotionSway.EnableUprightCompensation=0
ts2.CameraMotionSway.KSitting.Y=150.0
ts2.CameraMotionSway.KSitting.Z=55.0
ts2.CameraMotionSway.LSitting.Y=15
ts2.CameraMotionSway.LSitting.Z=1.25
ts2.CameraMotionSway.SittingPivotOffset=-200
ts2.CameraMotionSway.LSitting.X=10

[ConsoleVariables]
AllowAsyncRenderThreadUpdates=1
AllowAsyncRenderThreadUpdatesDuringGamethreadUpdates=1
AllowAsyncRenderThreadUpdatesEditor=1
<<< Also that is if any of the above Orange Text is needed or should be here >>>
[/script/engine.renderersettings]
r.SkeletalMeshLODBias=-2

[/Script/Engine.UserInterfaceSettings]
ApplicationScale=0.700

Would greatly appreciate your assistance.

 

Shader compilation is done entirely by CPU, so the stutters while they are compiled will be the same on RTX3050 as well as on 4090. On 4090 they will be most probably even more pronounced, because 4090 is creating much more load on your CPU, so CPU will be overloaded by supplying the data to GPU while doing also shader compilation on top.

So those mulit-second stops you are seeing are from your CPU - what CPU do you have? Getting a 4090 without CPU upgrade in case you have some older one is not a good idea, everything needs to be balanced. And TSW is CPU heavy quite a lot in some places, and probably even poorly optimized in this way.

 

Do you really add any graphical related setting into engine.ini beside the GodMode.sav? Why? Everything needed is already included in the .sav file. This is probably the reason for your issues, some settings are colliding.
Let the system generate new default engine.ini, then add the one single required line there as described in the installation notes and then install the latest GodMode.sav and test it like this. My bet is it will be just fine.

 

Teflon490, it is a totally new system that has the AMD Ryzen 9 7950X3D 16-Core Processor 4.20 GHz with 64.0 GB (63.2 GB usable) installed ram.

 

None of that stuff is actually in my ini settings so I’m afraid I can’t really help with it.

In short, the content of my mod I’ve put in for a reason, and things that are left out are left out for a reason too. I’ve never seen some of those commands before, so couldn’t even begin to guess what they are or what they’re meant to do. Sorry I can’t be more help.

 

thanks but the one i was referring to was AMD FidelityFX Super Resolution . Unless I'm getting them all mixed up. But I do know about the lossless scaling. I'll have to buy that one in the future

 

Yes I do know this, and before the enhanced ini was made into the Godmode.sav as it is today, I did volunteer to assist in testing multiple ini files for Jetwash, not that I understood what all the settings were for, I added them and tested and reported what I saw as well as with screenshots.
I also did do my own research on some settings for the reasons as stated below. And I used, see links below, again understanding the full scope of these settings is another issue, and while some are explained many are not in a way that explains what the values are for.
https://sites.google.com/view/foobiansmoddingworld/commands/tsw
https://www.kosmokleaner.de/ownsoft/UE4CVarBrowser.html
PC - Please Optimize Tsw4 Engine.ini | Dovetail Games Forums by geloxo

Most of those settings have to do with the camera and motion sway.
The setting
r.FogStartDistance=40000 <<-- not in Godmode.sav, I got this from the Godmode Mod after a fair amount of testing, I added this to the engine.ini in hopes of not having to change it on every route via God mode.
It is for how far the Fog starts, and without getting into personal issues, It's easier on my eyes...

After doing more research and looking at the Godmode.sav the following settings should not have been left in the engine.ini as shown and will be removed.
ts2.dbg.SteamParticleSize=0.5
ts2.dbg.SteamParticleSpawnMultiplier=5
The settings:
ts2.dbg.RelinquishPromptWaitTime=60
ts2.dbg.RelinquishPromptWaitTime=0
Are not in the Godmode.sav to my knowledge and are there to mitigate/stop the popup asking to give up A scenario to the AI

As for the setting:
TimeOfDaySystem.VolumetricCloud.GroundContribution=1
was also added to my engine.ini to assist in having one setting for all, well in the hope of that is, and again much of it is due to ease things on my eyes.
I never asked or looked for anything special, and why I rarely ask for anything, and why I do my best to learn and do it for myself so it doesn't look like special treatment. All mods should be for all not for a single individual.
:EDIT: looking at this bright white Forums does not help much either, a dark mode would be nice.

Okay, thanks I will do more research.

 

Ok then, CPU is not a problem here I also get 1-2 second stutter when driving a route for which the shaders were not compiled yet, although it is very rare and it depends on the complexity of the route. Simply go through it a few times and then it is gone, subsequent runs should be very smooth for you.

 

Ok, fair enough. But did you really test it with the default engine.ini? In other words, if you only have the JetWash's config installed, and nothing else, do you still get problems with shadows? Because I did not see any such thing using it, so it must be down to your other settings somewhere else.

 

with just vanilla ini settings, and nothing more but the Godmode mod there were no odd artifacts, in the images it's a freeze frame of what looks like black artifacts jumping around. Ran the same route again after re-installing Godmode.sav_v4.7 and the same engine.ini as shown there were zero artifacts, which leads me to think it is something that develops over time maybe...
But...
I am still testing and searching to get a better handle on the ini settings and what the numeric values stand for as they are changed, and yes I will let the game rebuild the vanilla ini and see how it goes, but the odd thing is it never happened as soon as the scenario loads up.

 

That seems to be a bug that has appeared after TSW4. It happens in the clean vanilla game and goes away after time generally. I think there’s some sort of GPU driver issue causing it maybe. I haven’t seen it for ages but saw it Bremen-Oldenburg the other day but it is definitely not my ini settings that are causing it though, I went to great pains to rule it out.

 

I never intended to imply it was caused by the enhanced ini_v4.7 you created, I figured there was something that was not working well together like oil and vinegar and I was looking to figure out what it could be, and now that I think about it that has been there on Xbox long before I switched to PC. But whatever I did with the engine.ini caused a conflict with Godmode v4.7.
I just finished MineHead Shunter Pt 1 & 2 ran them three(3) times back to back and recorded each session once, with no odd artifacts, for the most part, 59 - 60 FPS steady with the exception of the camera in the exhaust it dropped to 45.
This was done with Godmode v4.7 and the edited engine.ini I use I believe what I removed from it may have been the issue.

Spoiler

[SystemSettings]
AudioCommand.FenceWaitTimeMs=0
AudioThread.BatchAsyncBatchSize=10
au.MaxConcurrentStreams=5
au.DisableParallelSourceProcessing=0
au.Concurrency.MinVolumeScale=0.00001
au.SoundDistanceOptimizationLength=0.5
au.VirtualLoops.PerfDistance=500
au.VirtualLoops.UpdateRate.Max=1
au.VirtualLoops.UpdateRate.Min=0.5
ts2.dbg.JourneyChapterLockOverride=1
ts2.save.CheckpointsEnabled=0
ts2.RewardMonitor.ShowLowImpactNotificationsAsFull=1
TimeOfDaySystem.VolumetricCloud.GroundContribution=1 << this is till here to test
r.FogStartDistance=40000
ts2.dbg.Camera.MaxVerticalHeight=50000
ts2.dbg.Camera.MaxVerticalHeight=20000
ts2.dbg.Camera.MaxLinearDistance=50000
ts2.dbg.Camera.MaxHorizontalDistance=50000
ts2.dbg.MaxFreeCameraDistance=400000
ts2.dbg.MaxFreeCameraDistance=200000
ts2.dbg.Camera.CameraBoomMaxLength=4000
ts2.dbg.RelinquishPromptWaitTime=60
ts2.dbg.RelinquishPromptWaitTime=0
ts2.dbg.MaxReskinsPerTimetable=0
ts2.CameraMotionSway.EnableUprightCompensation=0
ts2.CameraMotionSway.KSitting.Y=150.0
ts2.CameraMotionSway.KSitting.Z=55.0
ts2.CameraMotionSway.LSitting.Y=15
ts2.CameraMotionSway.LSitting.Z=1.25
ts2.CameraMotionSway.SittingPivotOffset=-200
ts2.CameraMotionSway.LSitting.X=10

[ConsoleVariables]
AllowAsyncRenderThreadUpdates=1
AllowAsyncRenderThreadUpdatesDuringGamethreadUpdates=1
AllowAsyncRenderThreadUpdatesEditor=1

[/Script/Engine.UserInterfaceSettings]
ApplicationScale=0.700

and I spent a fair amount of time looking through UE sites

Spoiler

https://treert.github.io/ue-consolehelp/ue4.html
https://forums.unrealengine.com/t/console-command-to-adjust-fog-start-distance-camera-bound/231842
https://dev.epicgames.com/documenta...calability-reference?application_version=4.27
https://dev.epicgames.com/documentation/en-us/unreal-engine/scalability-reference-for-unreal-engine
https://dev.epicgames.com/documenta...dio-console-commands?application_version=4.27
https://dev.epicgames.com/documenta...ne/volumetric-clouds?application_version=4.27
https://dev.epicgames.com/documenta...eaming-configuration?application_version=4.27
https://dev.epicgames.com/documenta...l-rendering-overview?application_version=4.27
https://dev.epicgames.com/documenta...atency-frame-syncing?application_version=4.27
https://forums.unrealengine.com/t/how-to-enable-v-sync-in-unreal/50977/3
https://forums.unrealengine.com/t/a...w-to-get-it-working-check-its-activated/50433
https://forums.unrealengine.com/t/framerate-stuck-at-30-with-vsync-on/244031
https://train-sim-world.fandom.com/wiki/Console_Commands
and here
Steam Community :: Guide :: Big Optimization Guide - AllowAsyncRenderThreadUpdates=1
https://sites.google.com/search/foo...onsAsFull&scope=site&showCloudSearchTab=false
Results from this site
TSW commands
... ts2.platform.MinSpawnInterval ts2.RewardMonitor.EnableRepeatingRewards ts2.RewardMonitor.ShowLowImpactNotificationsAsFull ts2.save ...
Last modified on Nov 19, 2022

 

Ok...can anybody explain the last few pages in simple terms please?

 

Hey all.

I noticed this morning that, for me at least, yesterday's game update seems to have overwritten the main engine.ini (to my knowledge, for the first time ever) which will take out a few commands that are pretty vital to this mod. The giveaway was my journey chapters were locked again.

If this has happened to you too there are instructions in the manual, but you will need to make sure that at least the first of the following line(s) are in your main engine.ini file. The rest are up to you but the first is imperative. I would suggest you copy and paste all of the following to the engine.ini situated here C:\Users\******\Documents\My Games\TrainSimWorld4\Saved\Config\WindowsNoEditor and save;

[SystemSettings]
TimeOfDaySystem.VolumetricCloud.GroundContribution=1 - This is an absolute must!
ts2.dbg.JourneyChapterLockOverride=1 - Unlocks all journey mode chapters to be played in any order you see fit
ts2.save.CheckpointsEnabled=0 - Disables the annoying autosave. Some people want this on, so just don't add this line
ts2.RewardMonitor.ShowLowImpactNotificationsAsFull=0 - Reduces down to a single notification related to miles driven all those annoying 'Congratulations, you've used the windscreen wiper' notifications

Finally, a couple of shots, just because...

 

I will check this. Thank you.

 

That's odd - mine was in tact as it should be. but yeah thanks for the heads up.

 

You’re not the first person to say that. Very strange, maybe it was just me!

 

For me the same there was nothing changed....

 

Same here, nothing changed for me either