I don't know if the update caused it? I found that I lose the ability to feel the speed. I only look at HUD speedometer, I can't feel the speed by game screen. Deceleration too fast at idle. Decelerating too fast uphill, and hardly accelerates downhill. When braking, these deceleration effects do not apply. The brake become relatively weak. Sometimes when stopping in platform, press "8" and you will find that train is moving slowly. Sometimes game screen is inconsistent with HUD speed. Especially when braking in platform, the "speed" is not continuous. I can't park perfectly. These make my brain feel confused. It is difficult for me to explain it in English. I mean it's like driving a train on another planet where the laws of physics are different. Some DLC should be normal, I test many DLC, and it confuses me. I stopped playing TSC. Now I watch YT cab videos to heal my feeling of speed.
I didn't notice any differences just now. If you post DLC names, ideally a video, it can be better investigated. The game has fairly flexible physics and there are substantial differences between DLC. Old rolling stock has much more elastic couplers, combined with massively different brake effort per wagon, it results in aggressive consist yoyo. Also, at some point people decided that a freight train takes a minimum of 5 minutes to stop from 25mph, and air propagation scripts must be adjusted accordingly. Some wagons automatically push, some of my coal trains can climb a 1% hill without power at 25mph. Yes. Flip it around and now you don't have to brake, ever. Gravity and grades work in steps. 0.5% has no drag at all, but 0.6% is a heavy grade. Might be related to low precision data types. On some routes it's more refined, on NS Coal District the 0.2-0.3% does have an effect on acceleration. Sometimes physics change over the course of a scenario. I'm climbing in notch 4 at 25mph and suddenly notch 8 struggles to maintain 20. Which could be an issue with the grade display, however, I can continue descending a 1.2% without braking. So probably drag. Consist crawl is well known since forever Point is, I don't think it's related to the patch, although there were mentions of data type changes, but with the previous iteration actually. FPS can also have an effect on you. I also have to watch the HUD because one day I'm driving a slow mountain route, the next I'm on a suburban train. All in all, realistically you have to accept how it is
Train moves when it stops. https://forums.dovetailgames.com/threads/train-simulator-classic-update-now-live.69714/#post-660470 I think these are also key! But those seems to be random, sometimes it happens and sometimes it doesn't, so I'm confused. About grades, try the difference: BR 442: Leipzig - Dresden Class 375: Chatham Main Line London-Gillingham The latter decayed too quickly. Does FPS affect physics? Should I increase FPS limit from 60 to 120?
There are some miniscule details, but no. What I meant is consistency. 30fps can also feel worse. When my game can't maintain fps I sort of feel it slowing down. It may actually, simulation is not allowed to drop below 15fps or so, if I'm well informed. Stutters usually pause the simulation as well. Given it sometimes jumps I guess it tries to match fps somehow. So yes, slow rendering might cause an actual simulation slowdown. Might be the cause of my many comments on the two independent clocks in the game running at different speeds, neither matching real time clock well either. Using the Steam overlay I did occasionally see how much faster or slower the clock runs, changing when I look east or west (0.85-1.2 seconds / second). My standard deviation on Settle Carlisle is three minutes per hour. (It's observed when you notice the ETA is diverging from the clock above it.) If anything, lower fps should have less rounding error effect - numbers per frame are larger.
What has not been mentioned here is FOV - Field of View. This may differ between addons. And FOV has an enormous effect on the sense of speed. Try adjusting the FOV and/or camera location. Regarding gradients the "Drag coefficient" in engine/wagon blueprints plays a huge role on how the train behaves. By default this is set to 2.76 if I don't remember wrong. TS has an calculation error and multiplies the value across the cars, instead of adding them. (Source: Discord, NZTS Saw) Try changing the value to 1.
That's not true, if you put it on a computer with too little power it will run far below 15fps. Until two years ago most of my time playing Train Simulator was at 3fps or so on laptops and workstation computers.
I believe the in-game FPS counter (Shift+Z) won't drop below 14 fps iirc but the Steam overlay FPS counter (that doesn't work on DX12 version btw) will go to 0 fps as will the Vulkan FPS counter through RWEnhancer2 and probably any other 3rd party software like Fraps for example (not tried the latter so cannot confirm that).
I use the same FOV and zoom often. UK EMU narrow cab shouldn't be a problem. I usually zoom in to 50%. Some routes used a lot of 2D trees that can spin, will it affect? German trains usually have AFB, which may cover the effect of discontinuous speed. How to do?
High FOV means higher "sensed" speed (more objects move past the same physical screen distance in the same time) but lower FOV means more immersion (gauges etc appear in the actual size you would see them IRL). I'm using 75 on a 27" 16:9 (default is 65, press the right button in the Options ten times.) - higher values will introduce distortion due to the fact that your screen is flat, so distances near the edges will get stretched like the Mercator map due to 3D > 2D planar projection. "Sprite" trees that always face the player are only noticeable if you turn your head whilst passing them. Don't think many of these are still used. So to come back to the original post, as the game has not changed, it must be your FOV setting.
If you zoom in this will make it look much slower. Changing the engine/wagon blueprint. But this doesn't change the "sensed speed", but the actuall speed in gradients etc.
In fact, zoom up will be more obvious, especially low speed. The game screen is full of mini stutter, not smooth. I updated NVidia driver and reduce Graphics Settings (View Distance). Seems to fix some routes.
I found that lots of light bulbs will kill FPS. After disabling "Dynamic Lighting", FPS increased greatly. Disabling "Dynamic Lighting" can fix mini stuttering. The disadvantage is that you need to adjust "Ambient Light Intensity" every game.
Do not deactivate dynamic lighting, as this restores the game's lighting to how it was in 2011. It is unbearably bad and should not be disabled.
Dynamic Lighting Off will kill all light sources (except the sun and baked light), use simple shadows, disable AA and AdaptiveBloom, and raindrops on windows. It will look like Kuju Rail Simulator. Not sure FPS can be that important, better to invest in better hardware imho.
i5-12400, 3050-8G, ram-16GB, SSD, win11, monitor 27 inch 1920*1080 60HZ. This computer can play lower quality RDR2. My request is not much. 60fps is acceptable, but must be smooth. TSW3 stutter makes me feel like I am in a car accident. Currently TSW have a solution to stutter, but I found the route scenery is too poor. TSC mini stutter in some UK routes is awful, that use lots of repeating trees. Sometimes the trees cause illusion that I'm going backwards, not forwards. Smooth 60fps TSC feels good. I like to go through sharp turns at high speed. I feel like an F1 player. I don't play racing games because my reflexes aren't dexterous. I think you can try disabling dynamic lighting, just as an experiment.
