Thanks for this Jetwash. Really really nice. Why has it taken me so long to install God Mode. Just one issue...... If playing with a controller, the FOV can no longer be controlled by the left stick. Meaning if I wish to zoom in, I have to use the mouse. We're you aware? Also, you mentioned being able to set the lighting intensity per route in God mode. Can't seem to work out how?
Hi, glad you’re enjoying it! Regarding the FOV, GodMode has its own FOV slider that allows you to set it much much further in or out than default. I suspect you’ll need to use a mouse for that however, although I may be wrong. Regarding the lighting intensity, you need to click on ‘Environmental Settings’ then there is a slider at the bottom of that box for ‘Skylight Intensity’. I would suggest starting with 0.4 then adjusting to your taste. Finally, if people weren’t aware I uploaded v1.4 yesterday that added a command to reduce the brightness of LCD screens making them much less over-exposed. There is also a separate mod/patch for the Class 385 as the global setting wasn’t dark enough for that particular unit.
Thank you. I thought the FOV change maybe locked to the mouse. Regarding the lighting intensity, maybe I misunderstood. I thought you meant you could lock the intensity on a route by route basis.? I can work the slider fine, but as you pointed out, whats fine on one route is not on another.
Ah, I see. I’ve not used it myself yet but in the top right of the menu bar is a little icon marked ini. That’s what you want.
Is there any way to set a semi-permanent skylight level, rather than having to manually reset the rather murky 1.0 every run?
For those having any performance issues, I set the foliage levels one down from Ultra at High within the game settings, and it’s running a treat using the Ultra.ini Thanks JetWash Still try to find the sweet spot with my spec I’ve got a RTX4070 so mid-high range at 1440p 144hz and I’m getting a solid 80-100 FPS with sometimes higher in places!
Hello JetWash Congrats for the mod it makes quite a difference to TSW I have noticed some people are having trouble seeing any difference in stutter reduction even if the right settings are in the config and i think it might be related to the following In the high.ini settings i have spotted that you have the the R.TextureStreaming=0 line Was this line added intentionally or you put this by mistake there ? I am asking you because this setting deactivated the streaming completely, which mean that all the streaming tweaks applied on the lower part are now null. Deactivating texture streaming has negative effects as the game engine now loads all textures into memories even the ones that are not used resulting in more stutter. ( the engine barely does a good job while streaming is active) If you wish to remove this line in other to re enable the streaming and associated tweaks you might want to take a look for its presence in the other ini's since i have only checked the high.ini one Regards!
Just pushed v1.5 with some further tweaks / improvements, including further tweaks to the LCD screen brightness and corrections to, and tweaking of, the streaming parameters to move away from a one size fits all approach.
JetWash , Sorry to be a bother, I've seen some other ini's include/recommend the following commands in the past: r.HighQualityLightMaps r.SkeletalMeshLODBias r.MipMapLodBias r.Streaming.FullyLoadUsedTextures r.Streaming.HLODStrategy Was wondering if they'd been omitted for a reason/don't do anything or something?
Yes. The commands that are there are there because they all do something specific and create a balance between visual acuity and performance. There’s nothing stopping you adding them if you wish, but they’re not part of my settings for various reasons. A number of them don’t do anything anyway!
1st, second to last and last. The other two hurt performance for zero improvement in the image (that I can see at least). Personally I’d rather spend performance on better shadows than loading higher lods on the trains when you can’t even see them. I think many of these commands are kicking around from the first days of TSW and are no longer applicable to the game. My commands are split into roughly; - Improve draw distance and reduce pop-in - Disable the Journey mode lock - Improve the way eye-adaption works - Improve shadows and their draw distance - Alter the TOD system - It is these that predominantly change the lighting and deal with the over-exposure
I’m waiting for some edits to v1.5 to be ok’d on TSC. Unusually it’s taken all day and I’m still waiting sadly. Be sure to grab them when they’re up.
Is there any setting increase that can increase the range you can see your own consist? I know when I'm doing US freight on Cajon pass, there are some corners where I can see the back of my trailers cutting off early in the distance.
I don’t know one that one I’m afraid. I can only think that the viewdistancescale= would help. Anything over 10 does nothing, and higher numbers hurt performance.
Just out of curiosity, why "beyond ultra" is missing "star intensity" parm and has value of 1.5 for TimeofDaySystem.VolumetricCloud.LayerHeightScale? Everything lower than "beyond ultra" has this at 1.8 and includes the stars intensity adjustment, while only beyond does not.
That sounds like an error on my part. Honestly I don’t know how that’s happened but I’ll fix it tomorrow. Thanks for the heads up.
Already responded to privately and changes made a couple of days ago, as mentioned here; https://forums.dovetailgames.com/th...d4-lighting-overhaul.71901/page-3#post-689625 The changes were also detailed in the change-log. V1.5.1 of both ‘Beyond Ultra’ settings now available correcting the errors that had somehow crept in there. TSC has had issues processing multiple file updates which I believe caused the errors. It should be good now.
very good ini´s thx a lot i added some lines for HDR screens looks awesome bUseHDDRisplayOutput=True r.AllowHDR=1 r.HDR.EnableHDROutput=1 r.HDR.Display.OutputDevice=2 r.HDR.Display.ColorGamut=2 r.HDR.UI.CompositeMode=1 r.HDR.UI.Level=0.5 cheers
Quentin thx i see the typo now but game looks perfect even with this wrong command ^^ i corrected now in my .ini
It may be just the current warmish temps in the UK, but since I implemented HDR, my 2070 has to work significantly harder and I get GPU temp warning messages (which I've experienced before in hot weather, without HDR).
I only play tsw and other games which dont have Nvidia Dlss with msi afterburner and so i undervolt my gpu which keeps my gpu/memory temp low with success. You will be amazed how good that works. Depends on your gpu you find tutorials on youtube how to set each Profiles which you can swap then during gaming.
Honestly DTG could package a version of the lighting fixes in this as "TSW4" on console and I imagine it'd be all anyone needed to justify the upgrade.
Having experimented with HDR for a couple of days, I've turned it off again, as it makes all the colours too 'bright' and posterised, undoing much of JetWash's efforts. (This could well be idiosyncratic to my particular monitor or other windows settings.) I've just done a run in the 700 from Hove to East Croydon, and while the framerates were 40fps or just below (which, trust me, is great performance for my PC on my preferred settings), on approaching East Croydon station it suddenly plummeted to a slideshow 5-8fps. Normal service was resumed once I'd passed under the station passenger overbridge. Weird, but if that's the only glitch, I'll happily take it.
HDR can be very hit and miss. Not every game's implementation plays nice with my HDR monitors. Some games look really vibrant with strong contrast between light and dark, others are just incredibly washed out, no matter how I try to recalibrate the screen (and doing so inevitably makes all the games which DO look good in HDR at my regular settings look terrible). It's very inconsistent.
Thank you, Jetwash - you clearly put a great deal of effort in developing these settings. This has been a literal game-changer for me - beyond the masterstroke of the visual enhancements, these settings have significantly decreased the amount of stuttering/choppiness. After trying various .ini settings over the past 2 years, I've finally found my sweet stop for .ini settings. Thank you so much!
Thanks JetWash. Excellent work, and a significant improvement to my setup as a result! But now: In your opinion, to what extent will TSW4 nullify any of your excellent engine.ini improvements, and will Godmode still work, and even be necessary in view of the new utilities?
I would say don’t count on any mods working, in fact expect them not to. That means any and all of them, particularly ones that do anything more than edit textures.
As I shan't be buying TSW4 until these are made the default settings in it, not a concern for me going forwards.
All, there is now a TSW4 specific version of this now available on TSC. I plan to tweak and develop it over the coming days but for now this works nicely and fixes the dim screens caused by the TSW3 version. I will also take a close look at how the TSW3 content looks within TSW4. https://www.trainsimcommunity.com/m...ini-tweaks/i3889-tsw4-to-d4-lighting-overhaul
I have modified my enhancement used for TSW3 and found a significant improvement in TSW4 so far (Based on your very helpful input in this forum, with sincere thanks to jetWash.) Here's my current Engine.ini setup, sorted alphabetically): [SystemSettings] foliage.LODDistanceScale=5 gc.MinDesiredObjectsPerSubTask=20 gcNumRetriesBeforeForcingGC=5 gc.TimeBetweenPurgingPendingKillObjects=200 r.AllowLandscapeShadows=1 r.AmbientOcclusionLevels=3 r.AmbientOcclusionMethod=1 r.CreateShadersOnLoad=1 r.DFDistanceScale=10 r.DFFullResolution=1 r.DistanceFieldShadowing=1 r.GTSyncType=1 r.LightMaxDrawDistanceScale=50.0 r.MinScreenRadiusForLights=0.00 r.OneFrameThreadLag=1 r.RenderTargetPoolMin=3000 r.Shadow.CSM.MaxCascades=5 r.Shadow.CSM.TransitionScale=2 r.Shadow.DistanceScale=2 r.Shadow.FilterMethod=0 r.Shadow.MaxCSMResolution=4096 r.Shadow.MaxResolution=4096 r.Shadow.RadiusThreshold=0.03 r.Shadow.SpotLightTransitionScale=4096 r.ShadowQuality=3 r.StaticMeshLODDistanceScale=0.25 r.Streaming.Boost=2 r.Streaming.FramesForFullUpdate=2 r.Streaming.LimitPoolSizeToVRAM=0 r.Streaming.MaxTempMemoryAllowed=12000 r.Streaming.NumStaticComponentsProcessedPerFrame=500 r.Streaming.PoolSize=24000 r.ViewDistanceScale=5 s.ContinuouslyIncrementalGCWhileLevelsPendingPurge=0 s.ForceGCAfterLevelStreamedOut=0 s.LevelStreamingComponentsRegistrationGranularity=50 s.LevelStreamingComponentsUnregistrationGranularity=10 TimeOfDaySystem.AutoExposure.ExposureBias=-0.5 TimeOfDaySystem.AutoExposure.SpeedDown=5 TimeOfDaySystem.AutoExposure.SpeedUp=10 TimeOfDaySystem.BloomIntensity=0.17 TimeOfDaySystem.Clouds.HighAltitude.CloudDensityMult=0.3 TimeOfDaySystem.CloudShadowVolumetricResolutionScale=4 TimeofDaySystem.LegacyEmissiveAdjustments.EmissiveMultNonLamp=500 TimeOfDaySystem.SkyLightPollutionLuminance=1.0 TimeOfDaySystem.StarIntensity=50 TimeOfDaySystem.SunIntensity=50000 TimeOfDaySystem.VolumetricCloud.GroundContribution=1 TimeOfDaySystem.VolumetricCloud.LayerHeightScale=1.8 TimeOfDaySystem.VolumetricCloud.RayMarchedShadows=1 My Rig: AMD Ryzen 9 5900X 12-Core CPU; ASUS Cross Hair VIII Formula Mobo; Win 11 Pro (64 bit); 32GB RAM; 2TB Corsair Force Series MP600 Pro 2TB PCIe Gen 4.0 M.2 NVMe SSD. 1TB SAMSUNG 960 EVO M.2 NVME SSD; MSI GeForce RTX 3090 VENTUS 3X 24G OC; Dell G-Sync 144Hz Monitor.
I'm still having this long standing issue in TSW3, where some detailed stations bring the game to its knees. This includes Derby on the Midland Main Line, and East Croydon on London Commuter. There aren't even any other trains around. When I approach these stations the FPS drops from 45-65 down to 8-10, and only returns to normal when I have fully left the station / the camera is facing away from them. It's consistent and happens 100% of the time in all times of day. Before using this .ini, this did not happen, instead I just had 35-45fps across the board with more stutters. Playable but not ideal. Any ideas on how to fix/investigate the cause? I tried removing all other mods too, to no avail. I'm using the High preset, did try every single preset but none of them changed the behaviour... :/ Regardless, here's the engine.ini I usually use: Code: [SystemSettings] r.ViewDistanceScale=3 foliage.LODDistanceScale=3 r.StaticMeshLODDistanceScale=0.5 ts2.dbg.JourneyChapterLockOverride=1 ts2.save.CheckpointsEnabled=1 TimeOfDaySystem.AutoExposure.SpeedUp=10 TimeOfDaySystem.AutoExposure.SpeedDown=5 r.LightMaxDrawDistanceScale=50.0 r.MinScreenRadiusForLights=0.00 r.AllowLandscapeShadows=1 r.DistanceFieldShadowing=1 r.DFDistanceScale=10 r.DFFullResolution=1 r.Shadow.FilterMethod=0 r.Shadow.DistanceScale=2 r.ShadowQuality=3 r.Shadow.CSM.MaxCascades=5 r.Shadow.MaxResolution=2048 r.Shadow.MaxCSMResolution=2048 r.Shadow.SpotLightTransitionScale=2048 r.Shadow.RadiusThreshold=0.03 r.Shadow.CSM.TransitionScale=2 r.CreateShadersOnLoad=1 r.Streaming.LimitPoolSizeToVRAM=0 r.Streaming.PoolSize=3500 r.Streaming.MaxTempMemoryAllowed=1500 r.RenderTargetPoolMin=1200 r.Streaming.FramesForFullUpdate=2 r.Streaming.Boost=2 r.GTSyncType=1 r.OneFrameThreadLag=1 s.ForceGCAfterLevelStreamedOut=0 s.ContinuouslyIncrementalGCWhileLevelsPendingPurge=0 s.LevelStreamingComponentsUnregistrationGranularity=10 s.LevelStreamingComponentsRegistrationGranularity=30 r.Streaming.NumStaticComponentsProcessedPerFrame=200 gc.TimeBetweenPurgingPendingKillObjects=200 TimeOfDaySystem.VolumetricCloud.RayMarchedShadows=1 TimeOfDaySystem.AutoExposure.ExposureBias=-0.5 TimeOfDaySystem.SkyLightPollutionLuminance=1.0 TimeOfDaySystem.BloomIntensity=0.17 TimeOfDaySystem.SunIntensity=50000 TimeOfDaySystem.CloudShadowVolumetricResolutionScale=4 TimeOfDaySystem.Clouds.HighAltitude.CloudDensityMult=0.3 TimeOfDaySystem.VolumetricCloud.GroundContribution=1 TimeOfDaySystem.VolumetricCloud.LayerHeightScale=1.8 TimeOfDaySystem.StarIntensity=50 TimeofDaySystem.LegacyEmissiveAdjustments.EmissiveMultNonLamp=500 r.SkeletalMeshLODBias=0 r.TemporalAACurrentFrameWeight=0.2 r.TemporalAASamples=4 r.ToneMapper.Sharpen=0.5 r.SSR.Quality=4 r.SSR.Temporal=1 r.AmbientOcclusionLevels=3 r.AmbientOcclusion.Method=1 r.GTAO.FalloffEnd=150 r.GTAO.SpatialFilter=0 r.GTAO.NumAngles=2 r.GTAO.UseNormals=1 r.GTAO.ThicknessBlend=0
I've found this line can cripple performance in quite a few situations TimeOfDaySystem.CloudShadowVolumetricResolutionScale=4 I've personally just set it to 1. As this is a "scale" it is likely multiplying a 1024px shadowmap to 4096px, which is utterly unnecessery for cloud shadows and absolutely nukes performance in certain weathers. edit - worth noting, do not set this to 0 as it will cause the game to crash if TimeOfDaySystem.VolumetricCloud.RayMarchedShadows=1 I'm running a 5800X and 3080 12GB. My full ini is as below: r.ViewDistanceScale=3 foliage.LODDistanceScale=3 r.StaticMeshLODDistanceScale=0.5 r.LightMaxDrawDistanceScale=50.0 r.MinScreenRadiusForLights=0.00 r.AllowLandscapeShadows=1 r.DistanceFieldShadowing=1 r.DFDistanceScale=10 r.DFFullResolution=1 r.AmbientOcclusionLevels=3 r.CreateShadersOnLoad=1 r.Streaming.LimitPoolSizeToVRAM=0 r.Streaming.PoolSize=7000 r.Streaming.MaxTempMemoryAllowed=3000 r.RenderTargetPoolMin=1200 r.Streaming.FramesForFullUpdate=2 r.Streaming.Boost=2 r.GTSyncType=1 r.OneFrameThreadLag=1 s.ForceGCAfterLevelStreamedOut=0 s.ContinuouslyIncrementalGCWhileLevelsPendingPurge=0 s.LevelStreamingComponentsUnregistrationGranularity=10 s.LevelStreamingComponentsRegistrationGranularity=30 r.Streaming.NumStaticComponentsProcessedPerFrame=200 gc.TimeBetweenPurgingPendingKillObjects=200 TimeOfDaySystem.AutoExposure.SpeedUp=10 TimeOfDaySystem.AutoExposure.SpeedDown=5 TimeOfDaySystem.AutoExposure.ExposureBias=-0.5 TimeOfDaySystem.SkyLightPollutionLuminance=1.0 TimeOfDaySystem.BloomIntensity=0.17 TimeOfDaySystem.SunIntensity=50000 TimeOfDaySystem.StarIntensity=50 TimeofDaySystem.LegacyEmissiveAdjustments.EmissiveMultNonLamp=1750 TimeOfDaySystem.Clouds.HighAltitude.CloudDensityMult=0.5 TimeOfDaySystem.VolumetricCloud.RayMarchedShadows=1 TimeOfDaySystem.CloudShadowVolumetricResolutionScale=1 TimeOfDaySystem.VolumetricCloud.GroundContribution=1 TimeOfDaySystem.VolumetricCloud.LayerHeightScale=1.5 r.MaxAnisotropy=16 r.PostProcessAAQuality=6 r.TemporalAA.Algorithm=1 r.TemporalAACatmullRom=1 r.TemporalAASamples=5 r.AmbientOcclusion.Method=1 r.GTAO.FalloffEnd=100 r.GTAO.SpatialFilter=0 r.GTAO.UseNormals=1 r.GTAO.ThicknessBlend=0 r.color.min=0.001 r.color.mid=0.6 r.color.max=1 r.Shadow.DistanceScale=2 r.Shadow.CSM.TransitionScale=2 r.Shadow.MaxCSMResolution=6144 r.Shadow.RadiusThreshold=0.005 r.Shadow.CSMDepthBias=7
Thanks for the suggestions. Unfortunately, despite making this change, I don't see any difference. Just tested and still 12FPS at Clapham Junction, for the entire length, and a few other stations briefly go down to 18FPS, etc. Wasn't an issue before I started using this mod, if I take it all out it works fine. I've played these routes many times so there should be shader cache, by the way. I remember seeing a post here reporting the exact same issue with a few other details, can't seem to find it now though.
What’s your machine spec, what resolution are you running and which version of the ini are you using? What do you have the Sky Quality set to?
Thanks again Jetwash. I spent 3 hours this afternoon trying various combinations of ini / no ini and different detail levels on my laptop. Found the sweetspot seems to be DTG's default High setting with your High Ini settings (@ 1080p i5 + 3060) . After dong a run to let the shaders do their thing, I ran a couple of the ECML scenarios and they were nice and smooth (just very occasional micros stutters) with no pop in or colour changing trees. Really enjoyed them.
