It is an interesting question. For non Rush Hour passenger routes it definitely increases density, for Rush Hour routes its actually hard to say. Its possible it has no effect on Rush Hour passenger routes as BML is mostly empty.
The highest your hardware will support with a frame rate that you personally find acceptable. Its very subjective as to what is "acceptable" . I would encourage experimentation. I see some people have suggested FXAA over TAA for the antialiasing - this is also highly subjective so I would suggest experimentation ranging through Off, TAA, FXAA). For me FXAA causes issues with overhead wiring - TAA lowers my framerate but I prefer how it looks. Your mileage will vary . These are all my settings note percentage on 149 - it won't stick on 150! Some of the settings on the advanced screen are either enhanced or overridden by my engine.ini settings I cap at 60 even though my monitor is gsync and capable of 145 sustained and peaks of 165 - above 60 after the 4.26 update it sometimes gets the flickers and I have to turn it off and on to resolve that. Definitely experiment and find out what you enjoy the most for your play & immersion.
Who did the tweaks you used? What was the frame rate in Victoria? And what is your graphics card? Sorry for the questions, it is just I would like to get the best display possible on my 3060 so like to mess with the settings. With the tweaks from Paul is it better with DX11 or DX12?
I used Paul's set of tweaks. I will run a service again later to capture the FPS at Victoria. RTX 3070 OC'd. I've been running on DX12 mode for a week or so after others here confirmed that the custom liveries & the livery manager now work in DX12 mode. Update: I went back to TAA as my AA option & ran the tests. When I first load into Victoria, the game is giving me about 28 to 30 FPS. There seems to be a major amount of frame loss on initial load-in on just about every TSW2 route since the 4.26 update. After 20 seconds, the frame loss subsides & it rose back to 48 to 52 while in motion when leaving the station (both inside cab view & exterior cam).
Credit where its due, the tweaks I use are a very cut down version of those from geloxo - the knowledge so freely shared helped me to understand what the settings actually do which helped me work out what was good for my setup and tastes.
Anyone have any tips on improving or eliminating the flickering catenary? Its my big issue with Riesa Dresden, as the constant "shimmery" nature of the catenary, even when stopped, breaks the immersion. I'm currently running these settings: [SystemSettings] r.ViewDistanceScale=15 foliage.LODDistanceScale=7 r.SkeletalMeshLODBias=-5 r.MipMapLODBias=-3 r.EyeAdaptationQuality=0 r.MaterialQualityLevel=0 r.HighQualityLightMaps=1 r.PostProcessAAQuality=6 r.MaxAnisotropy=16 r.TemporalAACatmullRom=1 r.TemporalAASharpness=2.0 r.TemporalAASamples=4 r.TemporalAAFilterSize=1.0 r.TemporalAACurrentFrameWeight=0.2 r.TemporalAAPauseCorrect=1 r.TemporalAA.Upsampling=1 r.ToneMapper.Sharpen=1 The TemporalAA settings I think I got from an older thread about catenary quality, but they've only helped a little. Otherwise I'm running at 4K resolution and try to stay around 140% screen percentage depending on how bad my performance is on a particular route.
Joe Wagner hey try this and report if the flickering is still there thx [SystemSettings] r.ViewDistanceScale=2.0 foliage.LODDistanceScale=3 r.BloomQuality=3 r.TonemapperGamma=2 r.SkylightIntensityMultiplier=0.5 r.EyeAdaptationQuality=1 r.ToneMapper.Sharpen=0 r.TextureStreaming=0 r.MotionBlur.Scale=2.0 r.MinScreenRadiusForLights=0.00 ts2.CameraMotionSway.EnableUprightCompensation=0 ts2.CameraMotionSway.KSitting.Y=200.0 ts2.CameraMotionSway.KSitting.Z=200.0 ts2.CameraMotionSway.LSitting.Y=40 ts2.CameraMotionSway.LSitting.Z=5.0 ts2.CameraMotionSway.SittingPivotOffset=-200 ts2.CameraMotionSway.LSitting.X=50 ts2.save.CheckpointsEnabled=0 r.Shadow.RadiusThreshold=0 r.AmbientOcclusion.Method=1 r.GTAO.FalloffEnd=300 r.GTAO.SpatialFilter=0 r.GTAO.NumAngles=2 r.GTAO.UseNormals=1 r.GTAO.ThicknessBlend=0 r.Shadow.DistanceScale=1 r.Shadow.TransitionScale=1 r.Shadow.CSM.TransitionScale=1 [/Script/Engine.UserInterfaceSettings] ApplicationScale=0.600
I hope you know what ts2.save.CheckpointsEnabled=0 do. I don't but can imagine what it means according to the name. This setting gets copied blindly around as it seems and is not necessary for graphic quality.
There are no antialiasing settings in this one, so it will be like in the default / selected in game settings. I've been using these temporal AA settings for some 2 months now. They've been working quite nicely with eliminating flickering: Code: r.TemporalAACatmullRom=1 r.TemporalAAFilterSize=1.5 r.TemporalAAPauseCorrect=1 r.TemporalAASamples=5 r.TemporalAASharpness=2.0 r.TemporalAACurrentFrameWeight=0.2 However, these settings may get different results with a different resolution scaling. I have mine set to 1.25 (125%).
4.26 [SystemSettings] r.ViewDistanceScale=1 r.SkeletalMeshLODBias=-5 r.StaticMeshLODDistanceScale=0.25 foliage.LODDistanceScale=2 r.MaterialQualityLevel=1 r.DepthOfFieldQuality=0 r.BloomQuality=0 r.MotionBlurQuality=0 r.HighQualityLightMaps=1 r.PostProcessAAQuality=6 r.MaxAnisotropy=16 r.TemporalAACatmullRom=1 r.TemporalAASharpness=1.0 r.TemporalAASamples=64 r.TemporalAAFilterSize=1.0 r.TemporalAAPauseCorrect=1 r.ToneMapper.Sharpen=1 r.SSR.Quality=2
i know what this setting do and the point behind that is that disabling checkpoints save may reduce stutter..in any case for me a good option because i dont need auto save.
i dont have flickering so maybe some other settings causing that problem the AA from game doesnt cause that problem.
Indeed. orb if you've got flickering issues take out your engine.ini changes configure AA in game and see if that solves it. They reintroduce your settings one at a time to see if one of them is doing it.
Hi, what setting do I use to make the track render further away. I hate the way it renders right in front of me when driving.
try with r.ViewDistanceScale=2.0 up to r.ViewDistanceScale=10 depends on your machine 10 for high spec
How do I add "r.ViewDistanceScale=10"? I'v added it to "Engine.ini" but don't see any differance in game. Running on RX 6900 XT.
distance render for trees pop up is = foliage.LODDistanceScale=3 or 5 try this with r.ViewDistanceScale=10
Make sure it is after [SystemSettings] - you may need to put this in yourself - some thing sonly work in combination with other things and do nothing by themselves. [SystemSettings] r.ViewDistanceScale=10
Unfortunately, to date nobody has found an .ini command that helps with the sleeper draw distance (actually the sleeper shadow draw distance) ahead of the train. According to Matt this is because they are essentially different in kind from the scenery, and are run by a different graphics routine.
I recall Matt saying Fences, and Track are splines it'd be interesting to see performance and visual impact of increasing their draw distance.
thank you for this, were did you find this cvar? at least we can resize a bit the UI, only if i could eliminate the top left UI
i found this setting right here at the forum if i remember correct it was a thread made by a user dont know right now the name
sandosan Why are you posting this on a Train Simulator forum? Your post is completely irrelevant to these forums.
new pc ROG MAXIMUS Z690 HERO+i9 12900k+ROG-THOR-1200P2-GAMING+ ROG RYUJIN II 360 ram ddr5 32gb 5200 +RTX MSI 4090
I do realize this an old post, which ini settings did you use, if you don't mind me asking. I have been testing / experimenting with several ini settings as well through steam launch options "-HIGH -USEALLAVAILABLECORES" the PC I'm on is a Ryzen 5600 CPU and Asus RTX 3070 and SSD game drive, and I'm having mixed results to low FPS in the teens.
I was going to start a new thread on this so you bringing this back up is just as good I’ve been bemoaning Ultra not being Ultra and had given up on trying to find solutions from the usual places. I’ve had a trawl of some settings for other UE4 games and adapted them for TSW. I'm not 100% sure that they're all doing something but the overall look is what matters, and the overall look is good! They’re punchy (so beware!) and you’ll need a good GPU but they transform the look of the game, particularly shadows and draw distance. I would suggest using DX12 with this as it’s all but stutter free for me. [SystemSettings] r.BlurGBuffer=-1 r.AmbientOcclusionLevels=2 r.AmbientOcclusionRadiusScale=1 r.AmbientOcclusionMipLevelFactor=0.5 r.DepthOfFieldQuality=3 r.RenderTargetPoolMin=400 r.LensFlareQuality=3 r.SceneColorFringeQuality=1 r.EyeAdaptationQuality=2 r.BloomQuality=5 r.FastBlurThreshold=7 r.Upscale.Quality=3 r.MotionBlurQuality=4 r.Tonemapper.Quality=5 r.ToneMapper.Sharpen=0.3 r.TonemapperFilm=1 r.Tonemapper.GrainQuantization=1 r.DefaultFeature.AmbientOcclusion=1 r.DefaultFeature.AmbientOcclusionStaticFraction=1 r.DefaultFeature.LensFlare=1 r.ParticleLightQuality=2 r.LightFunctionQuality=3 r.HighQualityLightMaps=1 r.ViewDistanceScale=3 ts2.dbg.JourneyChapterLockOverride=1 r.DFDistanceScale=10 r.DFFullResolution=1 foliage.DitheredLOD=1 foliage.LODDistanceScale=5 foliage.DensityScale=1.0 r.LightMaxDrawDistanceScale=50.0 r.LightMaxDrawDistanceScale=5 r.MinScreenRadiusForLights=0.00 ts2.save.CheckpointsEnabled=0 TimeOfDaySystem.AutoExposure.SpeedUp=10 TimeOfDaySystem.AutoExposure.SpeedDown=1 r.VolumetricFog=1 r.VolumetricFog.DepthDistributionScale=32.000000 r.VolumetricFog.GridDivisor=120 r.VolumetricFog.GridPixelSize=16 r.VolumetricFog.GridSizeZ=96 r.VolumetricFog.HistoryMissSupersampleCount=1 r.VolumetricFog.HistoryWeight=0.900000 r.VolumetricFog.InjectShadowedLightsSeparately=1 r.VolumetricFog.InverseSquaredLightDistanceBiasScale=1.000000 r.VolumetricFog.Jitter=1 r.VolumetricFog.LightFunctionSupersampleScale=2.000000 r.VolumetricFog.TemporalReprojection=1 r.VolumetricFog.VoxelizationShowOnlyPassIndex=-1 r.VolumetricFog.VoxelizationSlicesPerGSPass=8 r.VolumetricLightmap.VisualizationMinScreenFraction=0.001000 r.VolumetricLightmap.VisualizationRadiusScale=0.010000 r.StaticMeshLODDistanceScale=0.25 r.LandscapeLODBias=-1 r.LandscapeLODDistributionScale=3 r.LandscapeLOD0DistributionScale=3 r.LODFadeTime=2 r.UITextureLODBias=-1 r.LevelStreamingDistanceScale=10 grass.CullDistanceScale=2 r.ShadowQuality=5 r.Shadow.CSM.MaxCascades=5 r.Shadow.MaxResolution=8192 r.Shadow.MaxCSMResolution=8192 r.Shadow.RadiusThreshold=0.03 r.AllowLandscapeShadows=1 r.Shadow.DistanceScale=3 r.ContactShadows=1 r.Shadow.FilterMethod=0 r.Shadow.TexelsPerPixel=3 r.Shadow.CSM.TransitionScale=2 r.Shadow.Preshadows=1 r.AmbientOcclusion.FadeRadiusScale=1.5 r.Water.SingleLayer=1 r.Water.SingleLayer.Reflection=1 r.Water.SingleLayer.SSR=1 r.Water.SingleLayer.SSRTAA=0 r.Water.EnableShallowWaterSimulation=1 r.Water.EnableUnderwaterPostProcess=1 r.Water.SingleLayer.RefractionFullPrecision=1 r.MaxAnisotropy=16 r.VT.MaxAnisotropy=16 r.RefractionQuality=3 r.ReflectionCaptureResolution=1024 r.SSR.Quality=3 r.SceneColorFormat=4 r.DetailMode=2 r.TranslucencyVolumeBlur=1 r.MaterialQualityLevel=2 r.SSS.Quality=1 r.BasePassForceOutputsVelocity=1 r.DefaultFeature.AntiAliasing=2 r.TemporalAA.Upscaler=1 r.Reflections.Denoiser=2 r.PostProcessAAQuality=5 r.TemporalAA.Algorithm=1 r.TemporalAASharpness=1 r.TemporalAASamples=32 niagara.CreateShadersOnLoad=1 r.CreateShadersOnLoad=1 D3D12.PSO.DiskCache=1 D3D12.PSO.DriverOptimizedDiskCache=1 r.HZBOcclusion=0 r.AllowOcclusionQueries=1 r.Shaders.Optimize=1 r.Shaders.Optimize=1 r.ShaderPipelineCache.StartupMode=3 r.ShaderPipelineCache.Enabled=1 r.ShaderPipelineCache.ReportPSO=1 r.ShaderPipelineCache.GameFileMaskEnabled=0 r.ShaderPipelineCache.LazyLoadShadersWhenPSOCacheIsPresent=1 r.ShaderPipelineCache.BatchSize=50 r.XGEShaderCompile=1 r.XGEShaderCompile.Mode=1 r.XGEShaderCompile.Xml.BatchGroupSize=256 r.XGEShaderCompile.Xml.BatchSize=16 r.XGEShaderCompile.Xml.JobTimeout=0.500000 r.GPUParticle.Simulate=1 r.GTSyncType=1 r.OneFrameThreadLag=1 r.D3D11.UseAllowTearing=1 r.D3D12.UseAllowTearing=1 r.Shadow.WholeSceneShadowCacheMb=4096 gc.TimeBetweenPurgingPendingKillObjects=900 gc.NumRetriesBeforeForcingGC=5 gc.MinDesiredObjectsPerSubTask=20 s.ForceGCAfterLevelStreamedOut=0 s.ContinuouslyIncrementalGCWhileLevelsPendingPurge=0 r.ShaderPipelineCache.BatchTime=2 r.ShaderPipelineCache.BackgroundBatchTime=0 r.ShaderPipelineCache.PrecompileBatchTime=0 r.Streaming.Boost=1 r.Streaming.LimitPoolSizeToVRAM=0 r.Streaming.UseMaterialData=1 r.Streaming.UseNewMetrics=1 r.Streaming.UsePerTextureBias=1 r.Shaders.FastMath=1 r.UseShaderCaching=1 r.UseShaderPredraw=1 r.UseAsyncShaderPrecompilation=1 r.TargetPrecompileFrameTime=13 r.PredrawBatchTime=13 r.AccelPredrawBatchTime=0 r.AccelTargetPrecompileFrameTime=0 r.Streaming.DefragDynamicBounds=1 r.Streaming.PoolSize=8192 r.Streaming.MaxTempMemoryAllowed=2048 r.Streaming.MinMipForSplitRequest=0 r.Streaming.HiddenPrimitiveScale=0.5 r.Streaming.AmortizeCPUToGPUCopy=1 s.AsyncLoadingThreadEnabled=1 s.IoDispatcherCacheSizeMB=2048 s.MaxIncomingRequestsToStall=1 s.MaxReadyRequestsToStallMB=0 s.MinBulkDataSizeForAsyncLoading=0 s.PriorityAsyncLoadingExtraTime=0 s.PriorityLevelStreamingActorsUpdateExtraTime=0 r.FastVRam.Tonemap=1 r.FastVRam.Upscale=1 r.FastVRam.VelocityFlat=1 r.FastVRam.VelocityMax=1 r.FastVRam.VolumetricFog=1 r.FastVRam.MotionBlur=1 r.FastVRam.SceneColor=1 r.FastVRam.SceneDepth=1 r.FastVRam.ScreenSpaceShadowMask=1 r.FastVRam.ScreenSpaceShadowMask=1 r.FastVRam.HZB=1 r.FastVRam.Histogram=1 r.FastVRam.HistogramReduce=1 r.FastVRam.LPV=1 r.FastVRam.DistanceFieldNormal=1 r.FastVRam.DistanceFieldShadows=1 r.FastVRam.DistanceFieldTileIntersectionResources=1 r.FastVRam.DistortHistory=1 r.FastVRam.Distortion=1 r.FastVRam.Downsample=1 r.FastVRam.EyeAdaptation=1 r.FastVRam.ForwardLightingCullingResources=1 r.FastVRam.DistanceFieldAODownsampledBentNormal=1 r.FastVRam.DistanceFieldAOHistory=1 r.FastVRam.DistanceFieldAOScreenGridResources=1 r.FastVRam.DistanceFieldCulledObjectBuffers=1 r.FastVRam.DOFPostfilter=1 r.FastVRam.DOFReduce=1 r.FastVRam.DOFSetup=1 r.FastVRam.CombineLUTs=1 r.FastVRam.BokehDOF=1 r.FastVRam.ShadowCSM=1 r.FastVRam.ShadowPerObject=1 r.FastVRam.PostProcessMaterial=1 [ConsoleVariables] AllowAsyncRenderThreadUpdates=1 AllowAsyncRenderThreadUpdatesDuringGamethreadUpdates=1 AllowAsyncRenderThreadUpdatesEditor=1
I thank you very much, I will give it a try and will let ya know how it works out. Between finding / reporting / documenting as well as getting play time in and just trying to stay on top of things, I have followed all of what you have stated on the Ultra settings and I Agree with ya 100% & ya took the words outa my mouth on that issue, while I may not have a nasa powered PC, I try to make the best of it, and if modding the ini settings does it then Great
I've found a lot of ini settings have got closer to GPS hits since What GPU are you running and what about in heavily dense or bad weather, EG Kassel or Bremen are the the FPS sitting at?
3090 FTW3. I’m getting 60fps (which is my monitor refresh rate) in DX12 (with 4K & Ultra in the settings menu, VSYNC on). It’s giving my GPU a workout for sure, much more than TSW has ever done. DX11 reduces the load on the GPU a bit but even with a very very fast CPU (5800x3D) I now see the stutters & pauses that people have complained about. None of that in DX12.
For me this is a pretty useless post. If you really want to be helpful, please describe something you want to accomplish, the settings that belong to that goal and why you have chosen this particular value ond how each setting contributes to the goal you have. I think the wishes are very much player dependent and I think it always is a bad idea to copy settings because somebody says these are good. Routes you, type of graphics card and so on may be important to find out if it really may help.
Useless? Bit harsh don’t you think? I’ve already said I copied them from another UE4 game (I tried a number of different ones in fact) and added them to the ones I already had. End goal wish - game looks much much better. To that end, the goal is accomplished. I don’t have the time or inclination to sit testing endless variables, and the suggestions that have always floated around TSW don’t really cut the mustard. They make the game look a bit better, but not like this. I’m not claiming it to be a public information guide either, I’m just merely stating facts. The choice to use them or not is entirely yours. You will need a good GPU though, as I said, and I’m getting no stutters, as I said. I also said I’m not 100% sure that they’re all contributing, but nor do I have the time to go through and test each one individually. The game looks much better, that’s all I’m bothered about at the end of the day.
However, without any commentary, others have no idea (1) which commands are actually useless in TSW, or accomplish little, and (2) which commands have a decent ratio of improvement to performance hit. It's simply a long block of text, which if cut and pasted into my .ini file will doubtless slow framerate to slideshow speed without any hint of where the sludge is.
Well, that depends on your machine of course. If you’re struggling anyway then it’s not for you. As I said, it’s not a public information broadcast. I’m simply stating that if you copy and paste that into your engine.ini your game will look pretty good. Nothing more. If you try it and it doesn’t work for you then so be it. If you try it and does then great. There’s really no issue either way, is there? Interesting that not a single other person in this thread has posted a commentary or breakdown but somehow I’m supposed to?!
I tried this on a 2080ti and I lost 15-20fps taking me down to about 40 on bremen before losing more to the bad weather. Personally for me this wasn't a win, just a curious explore. Reverted back now
What did you think of the visuals? Give it a shot on SEHS with clear skies from St Pancras to somewhere, the shadows look the best I’ve seen in the game. For the first time it actually felt ‘Ultra’ to me. You could always try dropping your screen percentage to 90-95% if you’re in 4K and see how that plays. That said, I think in reality you’d need a 3080 minimum if you were running it at 4K. My 3090 can only just keep up, which is a measure of how poorly optimised the game is. By comparison MSFS with everything turned up to 11 never really gets above 70% utilisation with DLSS set to Quality. TSW desperately needs DLSS/FSR.
I've done a bit of investigating and trimmed it down significantly. If you're finding it's still too much you can reduce the shadow resolution a bit more from 6144 to 4096. That should really help. I'm going to make a video demonstrating just how good it looks. [SystemSettings] r.ViewDistanceScale=3 ts2.dbg.JourneyChapterLockOverride=1 r.DFDistanceScale=10 r.DFFullResolution=1 r.Streaming.FramesForFullUpdate=1 r.Streaming.PoolSize=4500 r.Streaming.MaxTempMemoryAllowed=500 r.Shadow.DistanceScale=2 r.Shadow.FilterMethod=0 foliage.DitheredLOD=1 foliage.LODDistanceScale=5 r.LightMaxDrawDistanceScale=50.0 r.MinScreenRadiusForLights=0.00 ts2.save.CheckpointsEnabled=0 r.TemporalAACurrentFrameWeight=0.15 r.TemporalAASamples=2 r.DefaultFeature.AntiAliasing=2 r.PostProcessAAQuality=4 r.TemporalAA.Upsampling=1 r.TemporalAA.Algorithm=1 r.ToneMapper.Sharpen=0.3 r.SSR.Quality=4 r.SSR.Temporal=1 TimeOfDaySystem.AutoExposure.SpeedUp=10 TimeOfDaySystem.AutoExposure.SpeedDown=1 r.CreateShadersOnLoad=1 r.StaticMeshLODDistanceScale=0.25 r.ShadowQuality=4 r.Shadow.CSM.MaxCascades=5 r.Shadow.MaxResolution=6144 r.Shadow.MaxCSMResolution=6144 r.Shadow.SpotLightTransitionScale=4096 r.Shadow.RadiusThreshold=0.03 r.AllowLandscapeShadows=1 r.ContactShadows=1 r.Shadow.CSM.TransitionScale=2 r.Shadow.Preshadows=1 r.DefaultFeature.LensFlare=1 r.LensFlareQuality=4 r.AmbientOcclusionLevels=4 r.HighQualityLightMaps=1 r.DistanceFieldShadowing=1
I have been trying out the two ini setting you posted and surprisingly the one you posted in #79 worked pretty well on the timetable Edge Hill Coach Shunting that has been patched and changed yet again and made shorter, it's starting at 06:30 am, it's pretty dark, my fps was bouncing from the mid-teens to 30 and all the while was smooth a few stutters here and there. see attached screen shots, it really looked good, I liked it and I added -DX12 to the steam launch options. The only thing is when I tried a day time scenario when it was well past 0900 hrs my fps was stop motion, my GPU was crying but I expected that, the ini settings I quoted here the cutdown version was a fair bit better, but the Plain Jain 3070 GPU just can't cut it, I even added a bit of oc to it and it's still screaming HELP I did also add the CameraMotionSway ini setting londonmidland had posted in another thread. This also helped make things better, ts2.CameraMotionSway.EnableUprightCompensation=0 ts2.CameraMotionSway.KSitting.Y=100.0 ts2.CameraMotionSway.KSitting.Z=50.0 ts2.CameraMotionSway.LSitting.Y=10 ts2.CameraMotionSway.LSitting.Z=1 ts2.CameraMotionSway.SittingPivotOffset=-200 ts2.CameraMotionSway.LSitting.X=10 For now I will make do and hope I can getting some $$$ to get a better GPU. I appreciate all you have done and still do, thank you.
Did you try adjusting the shadow values down from 6144 to 4096. That should make a decent difference and make just tip the scales firmly in your favour. You could even try 2048 if 4096 isn’t enough of a reduction. It’s crazy that decent shadows are so intensive in this game. They really chew up GPU processing power, but I feel that Ultra level should look like this all the same because the hardware exists that can deal with it.
JetWash Thanks for post #79. I just rebuilt my PC with a 4080FE and i7-13700KF so it's great to have some updated settings for a high end PC. Hopefully, my rig can still handle it. I'll give it a try and report back.
Is there a way to reduce the overall brightness? I really like your settings but on certain occasions, feel like the highlights can be a bit blown out! But yea these settings really does elevate the game nicely )
I wish there was, unfortunately DTG are the only ones that can do that. There is a great mod here that helps; https://www.trainsimcommunity.com/m...3-auto-exposure-eye-adaption-compensation-mod I’d also recommend using reshade with the TAA shader as it helps get rid of TSW incessant flickering
You don’t need a mod for this. Simply type r.EyeAdaptation.LensAttenuation 0.1 into the console. I wouldn’t recommend this at night though as it’ll make everything look too dark,
This is what’s so frustrating about this whole endeavour. Fix one thing break another. I think Bescot’s eye-adaption mods really help, I’d recommend 1a if people haven’t used them before. The Autoexposure tuning in those ini settings helps the faff entering and exiting the tunnels.
Okay, I redid the ini settings as quoted to 4096. The timetable scenario I used is Reliving History, LMS Jubilee Crimson, West Cornwall Local. See the attached pictures they show various FPS. The SD40's was done in the training center. The HDR settings in red I got from Panico747 ("I removed the HDR settings from OBS because things were getting WAY too over saturated and too much work had to be done to correct it in Davinci Resolve") and I have Auto Exposure Compensation (Level 2) by Bescot installed. I know some of the pictures are over saturated the reds are REALLY red but, in some cases, it doesn't look too bad, but I was getting 30+ and in some cases upwards of 35 FPS. This was just to see what I can do, and I want I can't do with my plain jane 3070. Game screen size is 100%. I have my daughter helping me with video editing, so it'll be interesting to see what it'll look like in Davinci Resolve. Spoiler [SystemSettings] bUseHDDRisplayOutput=True r.AllowHDR=1 r.HDR.EnableHDROutput=1 r.HDR.Display.OutputDevice=6 r.HDR.Display.ColorGamut=1 r.HDR.UI.CompositeMode=1 r.FullScreenMode=0 r.HDR.UI.Level=0.6 r.ViewDistanceScale=3 ts2.dbg.JourneyChapterLockOverride=1 r.DFDistanceScale=10 r.DFFullResolution=1 r.Streaming.FramesForFullUpdate=1 r.Streaming.PoolSize=4500 r.Streaming.MaxTempMemoryAllowed=500 r.Shadow.DistanceScale=2 r.Shadow.FilterMethod=0 foliage.DitheredLOD=1 foliage.LODDistanceScale=5 r.LightMaxDrawDistanceScale=50.0 r.MinScreenRadiusForLights=0.00 ts2.save.CheckpointsEnabled=0 r.TemporalAACurrentFrameWeight=0.15 r.TemporalAASamples=2 r.DefaultFeature.AntiAliasing=2 r.PostProcessAAQuality=4 r.TemporalAA.Upsampling=1 r.TemporalAA.Algorithm=1 r.ToneMapper.Sharpen=0.3 r.SSR.Quality=4 r.SSR.Temporal=1 TimeOfDaySystem.AutoExposure.SpeedUp=10 TimeOfDaySystem.AutoExposure.SpeedDown=1 r.CreateShadersOnLoad=1 r.StaticMeshLODDistanceScale=0.25 r.ShadowQuality=4 r.Shadow.CSM.MaxCascades=5 r.Shadow.MaxResolution=4096 r.Shadow.MaxCSMResolution=4096 r.Shadow.SpotLightTransitionScale=4096 r.Shadow.RadiusThreshold=0.03 r.AllowLandscapeShadows=1 r.ContactShadows=1 r.Shadow.CSM.TransitionScale=2 r.Shadow.Preshadows=1 r.DefaultFeature.LensFlare=1 r.LensFlareQuality=4 r.AmbientOcclusionLevels=4 r.HighQualityLightMaps=1 r.DistanceFieldShadowing=1 ts2.CameraMotionSway.EnableUprightCompensation=0 ts2.CameraMotionSway.KSitting.Y=100.0 ts2.CameraMotionSway.KSitting.Z=50.0 ts2.CameraMotionSway.LSitting.Y=10 ts2.CameraMotionSway.LSitting.Z=1 ts2.CameraMotionSway.SittingPivotOffset=-200 ts2.CameraMotionSway.LSitting.X=10 ts2.dbg.Camera.MaxVerticalHeight=20000 ts2.dbg.Camera.MaxVerticalHeight=10000 ts2.dbg.MaxFreeCameraDistance=200000 ts2.dbg.MaxFreeCameraDistance=100000 ts2.dbg.MaxReskinsPerTimetable=0 [/Script/Engine.UserInterfaceSettings] ApplicationScale=0.700
Are you using 4K? You can definitely reduce your screen percentage to 95% which will help. I think I’ve done that and notice zero difference.
