Railworks America

Apparently half between three and four ....

Here is the description:

"Today we have made our fourth update test build for Train Sim World available for you to test, with a view to release the patch to the main game early next week.

Keyboard Support
Belgium - Added number keys for camera views
French – Fixed Q/A mapping conflict
Hungary – Brake keys fixed
Additional keyboard fixes for:
Switzerland
Turkish
Arabic
Danish
Norwegian
Portuguese
Bulgarian
Canadian French
Finnish
Swedish
Slovenian
Spanish
Localisation
Fixes to localisation including Polish and Russian
Rail Vehicles
Additional improvements to the brake pipes.
Over-bright ditch lights fixed
Fixed AC4400CW IFD screens disappearing when not fully visible on-screen.
Some improvements to how End of Train Devices are handled on certain services
Fixed PCS on AC4400CW which was causing emergency brake application continually
Rain/Snow will no longer appear on windows while in tunnels
User Interface
Added FPS limit options to the advanced setting screen
Screenshot Quality settings are now saved correctly
Added keyboard language code ID to setting screen to aid in DTG diagnosing additional keyboard issues.
Added “completed” icon to Services menu
Added clock to screen when in First Person on foot mode
Added a Ctrl+0 command so that if you are driving a train, get up and walk around and end up glitching to somewhere you can no longer drive, Ctrl+0 will now put you back in your engineers seat. A more complete fix to prevent glitching is being investigated.
Route
Fixed errant floating trees at Sand Patch Summit
Slowed melt/freeze speed
A number of art issues resolved as raised by customer support tickets
Optimisation
Further work has been carried out to further improve frame rates in scenarios
Other optimisation improvements
KNOWN ISSUES
Game crash when trying to tab a signal in the Cumberland Charge scenario
One of the ditch lights on the AC4400CW doesn't emit light (very minor).

The Train Sim World Update 3 Test Build download will be approximately 350 MB in size."

Build number is now 50

Thanks for posting! Downloading now. Quite a a list.

EOTD still not staying on it seems ...

FPS limit set to 20, gives the 3.5 GHz I5 CPU a little breather, takes away about 20% of average load. But 980Ti GPU still at almost 100% with all settings maxed out, fullscreen windowed at 200% which gives a nice picture.

It seems the whole simulation and physics thing with all its scripts running on the CPU is still throttling overall performance the most.

Did they roll back the ditch lights on the AC4400 to a previous build because an old bug is back again (the single ditch light flashing)?

I'm getting about 10 or more FPS across the board,but the trackbed gravel between the rails looks very flat and one dimensional to me now.maybe I'm wrong -anyone else think so?(everything on ultra)

plovdiv21 wrote:I'm getting about 10 or more FPS across the board,but the trackbed gravel between the rails looks very flat and one dimensional to me now.maybe I'm wrong -anyone else think so?(everything on ultra)

Could very well be true. Something has to give obviously to get few fps out of a constricted game engine. Draw distance of rail clips etc is still very small, only about an engine length.

It does sort of seem that the ballast shoulder has been lowered.

SPAD seems to be implemented now, at least I got a forced end of scenario when I overran a Stop signal, the first B&O colour position light signal at the east end of Cumberland (Mexico Tower?)

The FPS has improved quite a bit.

Using the benchmark Q353 that I always use. ( Edwin, have you checked Q353? )

Services, GP38-2, Summer Clear, Q353

My settings:
Resolution 3440x1440
Foliage Quality Ultra
Shadow Quality Off
Effects Quality Medium
Post Process Quality High
View Distance Quality High
Texture Quality High
Max FPS Slider = 60

AntiAliasing TAA
Vsync Off


View 1 has gained 10 FPS
View 2 has gained 2 FPS
View 3 has gained 10 FPS
View 8 has gained 0 FPS

Will have to run a scenario or two to test the stuttering issue. Will report back.

Shadows off makes your cabview bathe in light and the environment very flat ....

Your settings on my 3.5 GHz I5 with 980Ti @ 1920X1200 give:
view 1: 48 fps
view 2: 40 fps
view 3: 48 fps
view 8: 34 fps

Your settings on my 4.4 GHz I7 with 1080GTX @ 2160*1080 give:
view 1: 44 fps
view 2: 35 fps
view 3: 41 fps
view 8: 33 fps

CPU power doesn't really matter it seems, both I5 and I7 are more than capable. GPU power apparently doesn't matter either, screen size does however

Those are some really nice FPS you are getting Edwin You are right about the shadows though. I have changed shadow quality from off to medium. Looks nice, but it comes with a cost of loosing about 8 FPS. I am now seeing 32 in View 1. However the sim still stutters really bad at 3440x1440. I have tried turning down the resolution, but it looks "wrong" and stutters just as bad. The best experience I have in the sim in its current build are night runs. Seems smoother and FPS are higher.

I wonder what results the rest of the guys are seeing? Any improvement? Would like to know if it stutters really bad even though FPS are quite "good"..

Your 3440*1440 = 4953600 RGB pixels
My 1920*1200 = 2304000 RGB pixels

Your GPU has to work at lease twice as hard to keep the same picture up.

I've put the fps limit at 30 fps. That should be enough for my middle aged eyes, that 1920*1200 old technology LCD is not so fast on screen refresh anyway. It also will perhaps leave the CPU some headroom, hopefully less stutter and odd effects on scripted things.

My 2160*1080 is a 144 Hz monitor and set as such in the nVidia panel. I do not intend to keep TSW on that VR rig, it was installed only for comparison.

Have you seen screen tearing? Perhaps UE4 renders the screen is such a way there is no chance of tearing and vSync doesn't matter in windowed modes anyway?

I will have to try out some different FPS limit settings and see if it helps any. Yes I have seen some screen tearing, when panning too fast, but its the stuttering that kills it for me.

Off topic perhaps. Nvidia announced yesterday news of the new GTX Titan card. That is one monster GPU. https://blogs.nvidia.com/blog/2017/04/06/titan-xp/
I wonder what kind of performance you would get running a GPU like that with TSW.

imnew wrote:I will have to try out some different FPS limit settings and see if it helps any. Yes I have seen some screen tearing, when panning too fast, but its the stuttering that kills it for me.

Off topic perhaps. Nvidia announced yesterday news of the new GTX Titan card. That is one monster GPU. https://blogs.nvidia.com/blog/2017/04/06/titan-xp/
I wonder what kind of performance you would get running a GPU like that with TSW.

Stutter can have many causes, but usually indicates data is not delivered fast enough. I have an occasional white flash/screen tear and some light stutter when the hard disk light blinks, but other than that, gameplay seems quite smooth on the I5.

About that Titan XP: it probably doesn't matter much in TSW at its current state. The game seems CPU constricted, too many threads not yet optimised or scaled over all available cores.
If DTG keeps cutting back on view distance, details, shadows and cheats by reducing the number of rail vehicles in a Service in order to mask the game's deficiency in physics and simulation complexity nothing is really gained, right?
I still think UE4 graphics engine is more than capable in world rendering, it is the trains stuff that is choking the cores. Here lies the biggest challenge for DTG's programmers and experts.
And that is before prototypically long trains with 6 or more motors, big junctions with lots of trains moving in all directions, better exhaust emitters suitable for steam engines, multiplayer, intelligent AI and more 'life' in the scenery.
There are very few people walking, and only a white delivery van roaming the deserted streets.

Has anyone seen a difference between display port and HDMI inputs on their monitor with TAA in TSW?

Train is dark going through tunnels. At least at night Improvement.
On a side note, I was having issues with accidental emergency applications in all locos and jumping throttle notches. I found that the repeat keystroke function was too sensitive. This can be adjusted in Windows 7 and 10. Go to control panel>keyboard and adjust your delay setting. This will add additional time before multiple keystrokes will start after the key is held down.


EDIT: Update no fix on the tunnels. Ditch light issue fixed. Check your monitor resolution settings in settings. TSW changed my default settings.

When I first got TSW I was getting 20 and below FPS on maximum graphics settings, dropped them all down to medium and got 25fps. FPS have increased with each update. I'm using the same scenario each time Powering America Pt2 with the AC4400 in the rain. I'm now getting around 44fps on this route in the 3.5 update. Not really interested in fps doing shunting as I don't like doing it. I think that they have fixed the issue (which some reported) of the rear loco not working in this scenario and you couldn't start the train on a small incline, seems to have been fixed, and now you can but still tricky. I have found to get moving on a incline is to use between notch 1 and say 4 to get moving. As your speed slowly increases move the throttle up another notch. Don't know whether this is how it is done in real life. If you push the throttle strait away to notch 8 you don't move.

I might try the graphics setting on high and see what fps I get then.