Public Beta Build 76.3a

That is great news !

Hopefully the Alpha Team will include some non-hardcore train simmers as well.

 

Got it, only 20+ MB

 

You may need to restart Steam to recognise the new BuildID and opt into Beta again incase you're not seeing an update.

 

Running Public Beta 76.2c

Looks like I need to re-adjust my full screen resolution. There is a huge black frame around the image. . . some time later, the "issue" was resolved by going to windowed-mode and then back to fullscreen-mode

Just did a swift QuickDrive run and after exiting TSC I got this pop-up . . .

 

Report:

RailWorks64.exe (Windowed Fullscreen, Win 10)
Peninsula Corridor: San Francisco - San Jose
Scenario UP Mission Bay Hauler

still crashes to desktop on loading (error in dispatcher module, already discussed in a thread and demo scenario uploaded for team to investigate)

Logfiles attached.

Vanilla installation. (Only Academy and Peninsula Corridor SFSJ installed)

Gold Star achieved on TSC v72.3

 

Screen froze on first running after update, but this could probably be due to the previous running including some editing of a route I am building. Menu freeze is a frequent issue after route building, will be interesting to see if this beta has cleared it.
Shutdown and restart and all good so far.

 

It's advisabe to delete/backup Content\PlayerProfiles.bin when testing the new Beta. It stores a lot of values which could cause issues after updating.

The Menu freeze only happens if you enter the game and go to Build menu directly, do your stuff and then quit to main menu. This avoids the processing of the SDBCache.bin for the Drive menu, which will then happen on exiting the Build menu (as it then needs to show route icon). Clicking Drive first, and it's done. Time depends on the amount of routes and scenarios installed. Also it syncs with your career.xml in the Steam folder when creating a new scenario.

TrainSim-Steve A progress indicator when the SDBCache.bin is processed would be nice, as the process appears to be dead (not responding) during that time (ingame, not splash screen). This can take quite some time on big installations. (up to a minute here)

 

I can provide you with a fixed version if you like. (moving the consists in the sidings a little back and deleting one car from the third rake).

 

Still running off screen after the update.

 

LOL I did, twice. Before installing and before posting. Just thought it was odd Steam did not offer to install and that all runs fine, except exiting the game.

What is this dot net stuff for. Am I missing out anything ?

 

I'll DM you.

 

No worries Steve. Never even knew I did not have it. What is this dot net stuff for? Am I missing out anything ?

 

Very nice news altogether, Steve! Will look into it later today.

 

It looks like the beta does not recognize routes in the workshop. Under required Add-ons it's showing the route required like I don't have it even though I do have it.

 

did you fix the out of memory error?

 

Why don't you read the release statement?

 

Installed and ran the new beta and updated.net this morning. Reset frame rate limits from 30 to 60 and noticed much better frame rates. Noticed better use of my discrete GPU. Scenarios that were in the teens went to 30+. Did not notice any stuttering, Ran smooth and no crashes.

 

There wasn't one single OOM error. It was a generic message related to all sorts of issues which have been eliminated step by step.

The most likely cause still left is bad assets or corrupted workshop items.

 

Trainsiom Steve
Do we need to install ,NET 6 - SDK 6.0.417 in both x64 and x86 versions?
https://dotnet.microsoft.com/en-us/download/dotnet/6.0 (BUT SEE POST BELOW)
We now have .NET 8 is that the best option?

Check what version you have
Windows - Control Panel - Programs and Features - Scroll down to Microsoft .NET and that will show the version installed - must be at least 6.

NOTE: Post below by triznya.andras gives a much better solution and his/her link should be used,

 

You only need the runtime, at least according to the error message.

SDK is useful if you are developing, and want to build new .Net executables. That could include just having your own CI/CD pipeline, or building your custom version of RW Tools.

The error message above points at the x64 Desktop Runtime. Stackoverflow suggests that x64 includes x86.
A thus irrelevant argument about x86 - If you never run the x86, you wouldn't need it. In general, however, many .Net apps are targeting x86, also you may want to check something in x86 mode because reasons.

So, I'd go for this: https://dotnet.microsoft.com/en-us/.../runtime-desktop-6.0.25-windows-x64-installer

 

So I am building this one scenario, and when trying to either edit it or simply to play it, I always get thrown out with the typical error message.

It seems just like on the previous versions of TS Classic, the only way to access my scenario is to do the "Wash and Go trick".

Long story short: The game crashes when reaching almost 3GB of RAM usage. By editing the Wash and Go scenario from the Munich to Augsburg route, and then clicking "play", and then going back to the main menu, opening the scenario that crashes the game, magically doesn't crash the game and the RAM memory goes well over 6GB usage if necessary. The game is rather stable, though. But only after that strange trick... There's a Czech video about it:

I'm attaching the crash log and a compilation of 3 log files created from LogMate. Please note, that the things I'm putting to test are third party content.

I'm also sharing this information here, as it seems to be one of those strange memory usage issues for which might not have been found the cause for them.

 

The launcher app TSC cannot be opened. I have the beta build 76.2c and the latest dot framwork, but the launcher app TSC doesn't work, or you don't have to open the new app

 

Thank you for the information Steve

 

Thanks for your response Steve!

I have actually made another test and instead of editing the Wash and Go scenario, I just went directly into it via Career Scenario mode and after closing that, the game was again stable with over the 3GB RAM usage.

I shall look and see if I can fix and / or remove the files being highlighted by log mate and we shall see what happens next.

 

what is the memory usage and CPU load of v76.3c sitting on the selection screen after scenario and rail vehicle databases have been updated and the game is waiting for you to start it?
I have it at 30-35% CPU and ca 820 MB.
What is it actually doing when idling?

 

A bit of feedback on two situations, where my TS always crashe (and all the updates never changed this):

1. Going "in and out" of the the editor multiple times. For example when testing different weather patterns. Do this 5-10 times and the game dumps.
2. Another situation from the editor. "Looking at rolling stock". Not even placing it on the tracks, just clicking on rolling stock from different providers and viewing it without placing will cause a crash after 30-40 vehicles. This is annoying, when you have a huge collection.

 

Sorry, not right now. I still have to test the new beta today. Just something I have noticed over the years and never seems to change, even through all your new builds where you are trying to erase crashing from the game.

 

If I'm not wrong, once a texture is loaded in TS (and in memory) it won't be removed until you restart the game/scenario. So my guess is that you just fill up the memory until it crashes. Each rolling stock can have several hundred of megabytes in just textures.

 

Ryzen 7 7800X3D CPU temp 84 degrees at 48 watt load with that beta thing. With my V72.0 version 52 degrees on a 55 watt load... This is crazy...

I think I will continue to work with my rock stable version V72.0a for good. Have no problems at all with V72.0a...

 

I decided to test this compilation even though I know that the full screen and tab switching problem was not fixed, the error is now generated instantly with new errors, before it was on the second tab change where the D3D Vertex Buffer Error was generated.

Error being in the menu.


Error when being in a scenario.


If this were a final compilation, they would be bombarded with complaints.

In versions prior to this, I discovered the reason for the D3D Vertex Buffer error, the problem is a conflict with the SilverLining plugin (because it also handles DX9 apis), I can even switch between tabs in full screen without errors when removing the plugin.

 

Have you locked the framerate?
I've set mine to 120, I don't need my PC to work hard to give me 800FPS.

 

The beta 76.3a has no problems so far. I always work in Editor for 4 - 6 hours, mostly using the TSC 64 DX12 and also DX9 64 bit, the only thing I did was remove the install folder in Railworks I don't use 32 bit. my CPU temperature is always at 45 -55 degrees, and utilization 14 -30%

 

I don't think there has been a response to this. Can anyone else check this and see if they have the same condition?

 

I have sometime an OOM error replacing a loco in the Scenario Editor, immediately after moving with the mouse the instructions from a loco to the other. This doesn't happen in the previous version 75.8a in the same situation and locos.

 

Here's a new one. Doing a re-paint and did a .xx on a texture to see what all was on there and the game immediately gave me the OOM and crashed. This has always been a fairly normal method when having a little trouble finding a particular object on a loco or car. Usually you just went in and hit restart to see what that texture was doing. I got it to repeat so it's not a one off.

 

Still having issues unfortunately, I have attached two logs, both from different scenarios I've tried to load up, as well as the below error message which appeared on both.

 

This looks like corrupt assets / missing files. Probably a file verification will solve this.

I see it's Portsmouth Direct Line, which scenario? And what you mean with "load up"? Play or Edit?

The more precise your information, the easier to reproduce.