Fence Draw Distance

Hi

Is there any settings that an be changed in the game config file to extend the draw distance of the fences to stop them popping into detail in front of you?

 

No.

It isn't actually the static asset draw distance- that can be extended by command and isn't bad by default- what you are seeing is the shadows popping in, and nobody has found a way to increase the shadow draw distance.

 

thanks for the reply. i understand and will wait. thanks bud

 

Are we talking about shadows or are we talking about the popping effect you get with palisade style fencing for example?

If it's the latter have you tried the following setting:

r.StaticMeshLODDistanceScale=0

This is the one that I think significantly improves certain types of fencing changing from low to high detail right in front of you.

 

I'm noticing this a LOT lately on SEHS. I was using the engine.ini settings that Hightower posted a few months ago & mine is set for this:
r.StaticMeshLODDistanceScale=0.70

 

Yes that setting helps to get better quality in both track draw quality, fences and structures/building detail and textures. Don't go too low with this setting as you performance may die in the tile loading process, specially if there are big stations or yards involved. If you lower it too much also lower render distance to avoid overloading your system. I use it at 0.3 together with a x1.5 viewdistance, but this depends on each system specs, so probably you could even use a x2 viewdistance:

r.StaticMeshLODDistanceScale=0.3
r.ViewDistanceScale=1.5

Cheers

 

thanks for the advice guys. whats your setting on screen persentage?

 

I run at 1920x1080 with 200% scaling in game.

Cheers

 

I use these settings as well, all comes down to what your GPU is capable of. Press F3 to check your FPS and adjust accordingly.

 

Wow, those settings from him on my file were as follows:

r.ViewDistanceScale=8
r.StaticMeshLODDistanceScale=0.70

My system is old - an i7-4771 + GTX 970 + 16GB of RAM. I wonder what else I've got set wrong in that file, based on the age of my hardware...

 

Ha! YOUR machine is "old"? Mine has less HP than yours, and I have turned StaticMeshLODDistanceScale right down to 0 without a meaningful performance hit.

(PS: The effective max setting for ViewDistanceScale is 5; you can set it to a higher number but it won't make a difference)

 

I used the settings geloxo suggested & saw a major improvement in fence textures & the FPS was holding pretty solid at 40 FPS. Here's what my entire settings look like - can you guys look this over quickly & see if there is anything else I have set way too high or low?

r.StaticMeshLODDistanceScale=0.3
r.ViewDistanceScale=1.5
foliage.LODDistanceScale=5
r.ShadowQuality=5
r.Shadow.DistanceScale=2.0
r.DefaultFeature.MotionBlur=0
r.TextureStreaming=0
r.BloomQuality=1
r.TemporalAASamples=64
r.SkeletalMeshLODBias=-2
r.Color.Mid=0.4
r.HighQualityLightMaps=1
r.PostProcessAAQuality=6
r.MaxAnisotropy=16
r.Tonemapper.Quality=4
r.Tonemapper.GrainQuantization=1
r.SceneColorFringe.Max=0
r.SceneColorFringeQuality=0

I'm at 1920x1080 with TAA @ 115%

 

40? You lack ambition.

I'm running a locked 60 with this:

[System Settings]
r.TextureStreaming=0
r.Streaming.FullyLoadUsedTextures=1
r.Streaming.HLODStrategy=2
r.Streaming.PoolSize=1494
r.MaterialQualityLevel=1
r.DisableDistortion=1
r.DepthOfFieldQuality=0
r.DefaultFeature.LensFlare=0
r.DefaultFeature.MotionBlur=0
r.BloomQuality=1
r.SceneColorFringe.Max=0
r.SceneColorFringeQuality=0
r.EyeAdaptationQuality=0
r.Color.Max=0.7
r.Color.Mid=0.4
r.Color.Min=-0.3
r.TonemapperGamma=0.5
r.Tonemapper.Quality=0
r.Tonemapper.GrainQuantization=0
r.LightShaftQuality=1
r.LightShafts=3
r.MaxAnisotropy=16
r.TemporalAASharpness=0.0
r.TemporalAASamples=64
r.TemporalAAFilterSize=1.0
r.TemporalAACurrentFrameWeight=0.05
r.TemporalAAPauseCorrect=1
r.PostProcessAAQuality=6
r.Shadow.CSM.MaxCascades=10
r.Shadow.DistanceScale=5
r.ShadowQuality=5
r.Shadow.FadeResolution=8
r.Shadow.MinResolution=64
r.Shadow.RadiusThreshold=0.01
r.Shadow.TexelsPerPixel=1.6
r.ViewDistanceScale=5
r.LandscapeLODBias=-2
r.LandscapeLODDistributionScale=3
r.LandscapeLOD0DistributionScale=3
r.StaticMeshLODDistanceScale=0.0
r.SkeletalMeshLODBias=-5
r.MipMapLODBias=-3
r.HighQualityLightMaps=1
r.SSRQuality=3
r.AmbientOcclusionLevels=4
r.AmbientOcclusionFadeRadiusScale=50
foliage.LODDistanceScale=5
foliage.ForceLOD=0
foliage.DitheredLOD=8
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​

With an i5 3GHz machine (1080, not 4k). Note that I'm just using 100% scaling and instead have 4x supersampling set in my GPU control panel: works better, not nearly the performance hit.

 

Those settings look very complete guys. One I recently discovered was the grass density, with no apparent impact on fps:

grass.densityScale=5

This make grass amount 5 times higher resulting in more flowers and taller grass. The viewdistance is not changed and remains short as in the default game setting but the distant grass is a bit better due to the higher amount it has. You may want to try it. On WSR route this is very noticeable as there's grass all over the place along the track.

Cheers

 

ok i go to text

 

Ah, interesting.

 

One I haven't found yet in my mad quest to use EVERY .ini command!

Geloxo, is that an r. command, or unprefixed like the foliage commands?

 

It´s just unprefixed like the foliage one. Just paste what I wrote and change the number to your own needs. As you would be familiar with the unreal console now you can test different values with it to see the effect in real time and choose the best for you. Take into account that in the console the parameters don´t use " = " but just a space. So open console, type there:

grass.densityScale 5

and press enter. The same is possible for many other commands used at the engine.ini, but not all are available in the console and it drops a message about command not existing.

Cheers

 

This is something dtg want to improve across all platforms

 

I don't see where to do 4x supersampling on my GTX 970's Nvidia control panel......

 

Nvidia don't call it supersampling, they call it "DSR" (Dynamic Super Resolution)

 

That's what I thought. I just saw something on Reddit that referenced DSR & I don't have those options.

I copied your settings verbatim, and put the screen back to 100% instead of 120% & now I'm getting 58-60fps myself. What I don't like is the tree textures 'popping in' between 100-200yds now. Something in my settings (or lack thereof) did not display that behavior...

 

You should have DSR in your control panel, but only in the general 3D settings, not the app-specific panel for TSW2. It means it's on all the time, but I'm fine with that.

 

Found it & enabled it for 4x. Doesn't seem to be affecting the normal ops on the PC for now. Still got 60fps in the sim!

 

This is because DSR enables higher resolution selections within the game. If you enable DSR in Nvidia Control Panel, but don't change the in-game resolution, you haven't actually changed the internal rendering resolution. The reason you (or solicitr, for that matter) can maintain high FPS is because you have not changed the window resolution in TSW's graphics settings to 3840x2160, for example, and are still rendering at your normal resolution (1080p?).

For anyone who has enabled DSR in their control panel and neglected to change game resolution in settings, but experienced an increase in graphics quality: you are experiencing a placebo.

It is preferable to use in-game resolution sliders versus DSR whenever possible, because the latter can mess up the layout of your desktop or size of the HUD in many games. Performance hit should be nearly (if not) identical for both.

Cheers