Railworks America

Anyone know why Solider summit and Stevens Pass get bad FPS I know on Solider Summit one reason is the headlights are on max. Also here are my PC's system specs


i5-6400 CPU @ 2.70GHz

16. installed ram
Graphics card NVDIA Geforce GTX 1060 3GB

Directx 12

I suggest you fiddle with the shows and mess around with the anti-aliasing settings to see if that helps. Also try shutting off the procedural flora if you don't miss it too bad.

buzz456 wrote:I suggest you fiddle with the shows and mess around with the anti-aliasing settings to see if that helps. Also try shutting off the procedural flora if you don't miss it too bad.

what does procedural flora do? Also my anti-aliasing is on lowest not sure but I'll see what happens when I mess around with it

From my experience, the AI traffic on these routes really seems to kill the FPS, especially in quick drive. You'll probably notice better performance if you drive in free roam.

Procedural flora is the weeds and stuff that grows out of the terrain that we paint on.

buzz456 wrote:Procedural flora is the weeds and stuff that grows out of the terrain that we paint on.

thanks for the info

JohnTrainHead wrote:From my experience, the AI traffic on these routes really seems to kill the FPS, especially in quick drive. You'll probably notice better performance if you drive in free roam.

I'll try that and see what happens

JohnTrainHead wrote:From my experience, the AI traffic on these routes really seems to kill the FPS, especially in quick drive. You'll probably notice better performance if you drive in free roam.

I did what you said and the frame rate is very good

buzz456 wrote:...Also try shutting off the procedural flora...

Nine years of fiddling around with the editor and I never gave much thought to disabling Procedural Flora. Sure, it's a pain when it grows through a road within a couple dozen meters of the tracks but I would wind up under-painting the road with a texture that had no procedural anyway. I never would have guessed that a feature that seemed rather lame and ineffectual would impact performance to the degree that I just found out that it does.

I've been running a scenario on the Powder River Basin that has crashed near the end (or caused a train separation at the same spot) four out of four times. So, I come across this thread and think;

"If Buzz thinks that procedural flora is in some way connected to performance than maybe I should disable it and try that scenario again... It won't help, obviously, but I can say I tried it"

Well, the scenario finished with no crash for the first time. Results in one scenario should not lead to a definite conclusion one way or the other but here are some numbers I was looking at as I was running the scenario;

With Procedural Flora: Low memory usage 2700MB, HIgh memory usage 3100MB+

No Procedural Flora: Low memory usage 2450MB, High memory usage 2915MB

A savings of roughly 200MB across the board in memory usage in this particular scenario on this particular route has me convinced to leave procedural flora disabled from this point forward.

In Buzz I trust.

I should get that printed on a T-shirt.
Thanks for the verification Tomcat!

Procedural flora doesn't seem to look that flash anyway by modern standards, at least in my opinion. I prefer asset blocks with a foliage density that doesn't push the fps below about 30 with a Radeon 4800 series graphics card.

I replaced this card and the fps are higher, but it's not just myself that I'm thinking of in this regard, hence why I haven't increased the density.

Without touching any other settings you can also try lowering your main graphics settings to reduce lag. I think there are four settings, Highest, High, Medium and low. Whatever one you have TS set to try the next lowest setting. You can also play around with the settings in your Nvidia control panel too.





Settings something like these.

You should first check if it's a GPU bottleneck or a CPU bottleneck that lowers vor FPS.

Here an example for a CPU bottleneck:



You can see that I get 35 FPS (all settings on max 1080p) but my GPU, which should be as powerfull als your GTX 1060, has not much to do.
In this screenshot the CPU is the bottleneck and the root cause are the shadows of the Headlights (these are only active in the editor or when pressing a special key combination in the game)

You can also get low FPS if the (not very well optimized) game engine has to do many draw calls (you can watch this on the bottom of the editor) this is usually the case in dense areas or if there is much (AI) rolling stock in your environment.

To check the GPU activity I used the tool MSI Afterburner

May I ask which route is in the background in that screen capture?

SAR704 wrote:May I ask which route is in the background in that screen capture?

1869 extension.