Public Beta Build 77.1a

Very Nice, Steve.
My poor Elderly Cat, She passed away on 17th Feb, So I have not been looking at the Alpha or Beta Builds or anything as of late. But I am just getting back into things again.
I have noticed quite a few Lua scripting errors (stack overflows, Missing funtions getting called etc) in log mate, But sadly they are not DTG or any active Developer, they were from UKTS, and they have been compiled to .out So I cant really investigate those.

But if I find any DTG or any other active developer with any scrpts giving errors, I should be able to give them a shout out, that something is amiss.

Also, Is there anyway of setting up one of the Lua IDE's, that they can access the DTG functions? In signals, Locos, whetever, so you can spot errors in your scripts? That would be really nice, and useful.

 

KrisKol I'm really sorry to hear that. You've given her so much love during her life, I hope that gives you some comfort at this heartbreaking time.

 

Thanks for the update.

Had a quick test with BPE2 64-bit.
It doesn't preview any blueprint (no mesh or childs are loaded in the preview window)
If I export a loco it crashes the game. If I use 32-bit it works.
Will try to get some details from the logs after some more testing.
(CrashRpt-Log-20240327-124813-{854b8466-a64b-4f9f-878e-35d6d3497424})

The "Create Scenery Blueprint" is missing from the IGS right-click menu

V72.4:

 

Great update across the board, minus one small issue. It seems a side effect of the locked paused scenario fps causes the player camera turn speed to be wildly inconsistent. From what i can tell the less performance heavy a spot you are looking at is, the slower the camera turns. It would be nice if we had the option to opt out of the fps lock with a command line if this cant be resolved.

 

Some line height spacing/column spacing seems to be required for the new -ShowScriptTiming function as its all overlapped and near impossible to read. See attached. Sim was running at full screen, 3440x1440px

Some sort of method of filtering script types would be ideal as well, so signal scripts arent getting thrown in with loco etc scripts.

FPS seems to be improved, I am guessing due to the improved heap, so thats a plus!

 

Agreed - don't lock the FPS when using the "Pause" key - only lock them when using "Escape"!

(I use NVIDIA control panel to lock FPS at 75, and 20 when the game is minimized.)

I'd love too see that feature become an option (as I do not need it and let the GPU driver control it.)

 

Will this update cause steam to verify files.

 

It hasn't for me. Just trying out the update now.

 

Steam checked my files

 

What is Fast Sound ?

 

The sound made when the stock is moving fast I presume.

 

I just ran Script Performance and am amazed how many suggestions it created for a few seconds of the brand new Feather River Enhanced route.

 

The 64-bit Blueprint Editor 2 in the Railworks folder under Tools/x64 cannot be opened or gives an error message

 

That serious or are you joking ?

 

What does the error say?
Try to run it as administrator.

 

that is the error
S:\SteamLibrary\steamapps\common\RailWorks\Tools\x64\Temp\BlueprintSchema.xml is missing.Run RailWorks at least once to create this file
No errors are displayed with the other blueprints

 

Gotta say, I'm very impressed with the advances the team have made over the last twelve months, very rarely now do I get OOM's and any error at all really, ( I do sometimes on some janky third party content but nothing a reload doesn't fix ).

Lets hope to see more features and improvements in the coming weeks/months/years .

 

Did you run x64 RailWorks as indicated?
You could also try and copy the file present on the path without x64.

 

Just fired it up on my system and have that same notification (v76.4a)

 

Mine did this, I had to click Tools -> Options, then set the correct path for TS.
Then I had to click Tools -> Reload BlueprintSchema.xml

That made it work, however, I cannot preview anything. If I try it reports 'Please log in to steam' even though I am logged in...

 

Thank you, everything worked as you described, but I can't work with the Blueprint under RailWorks Tool

 

Hang on.
You need to tell it where the ROOT of your Railworks folder is.
Mine is:
E:\SteamLibrary\steamapps\common\RailWorks
In the E:\SteamLibrary\steamapps\common\RailWorks\Tools\x64 Go into the >Tools>Options... menu in the BlueprintEditor64
And show it where the root of your railworks installation is. Then you should be good to go.

I have my Installation on the Big SSD so mine is not the usual default location, replace that path with the one where yours is Located.

 

I have noticed a few errors so far, when I run the TSC with Vulkan and use the TAB key in the game, the TSC hangs.
Furthermore, BPE2 64-bit does not work with Vulkan. I have also noticed that when I use the Task Manager (whether with or without Vulkan
that the TSC cannot be started reliably and also in BPE2 (32-bit) the function "create Scenery Blueprint" only works once and not again.
If I close the task manager, everything runs fine.

Edit: I have now noticed that the TSC also freezes in the game when pressing the TAB key without Vulkan. So actually not usable.

 

Just noticed a new command line option . . . . ShowFunctionTiming

Any info on that one TrainSim-Steve ?

 

Yeah, not 100% sure that's exactly what's being referred to here but I know Armstrong Powerhouse use layers of sound samples to give the feeling of speed changing through the sounds so I assume there's a fast sound a slow sound as well as the points sounds even at a basic standard level.

 

I have a problem here.
I seem to be locked at 14 FPS. No matter what route I drive.
It was all fine until this version of the beta. I have looked and looked at what could be wrong, But I havent found the problem yet.

UPDATE: I found the problem. The Stupid Microsoft Store thought it was being prudent and rudely installed another version of the NVIDIA Control Panel.
Now that that is sorted, I will keep testing.

 

Hooray! The latest update when you go to look at a Geo file while the game is running it no longer crashes every time.

 

Seems to survive alt-tabbing when in fullscreen (though seems to do a partial asset reload on returning to the game?).
I still get OOM on big QD runs which I need to look into further.

 

In the previous BETA thread (so NOT this BETA version) I read....

dose anyone else see that the sliverlining 3d clouds are not working in quick drive on this beta patch? i have the dynamic clouds on in the settings but when in quick drive it turn off and it run the tsc old default 2d clouds.

Never knew that. Will do a test tonight to see if it works or not. Normally I pick summer weather, so never see many clouds anyway

 

I'm not in the beta but I'd gladly take that as a feature.
There was something about disabling Silver Lining in certain conditions - a command line option was mentioned, but having full screen selected could (should) be a cause, too.
To be fair I wouldn't mind replacing the weather choice with a drop down, with the ability to choose from all core (and route specific) 2D and 3D weathers. For a plethora of reasons. I like to drive under 3D but it's rather annoying for photos (due to the shadows).

 

You are not in the BETA ? Why not ? Is the best TS version on the market!
What are your reasons if I may ask?

BTW: All command line options are listed overhere --> https://forums.dovetailgames.com/threads/all-119-command-line-launch-options-which-ones-are-current-obsolete-incorrect-or-missing.74961/

The one you are referring to is: -DisableSilverLining

 

I prefer stability over experimental versions. The first versions have triggered a lot of reports.
I could fire up alternative versions if they were all available in their respective folders on the public (production) branch.

 

I agree, stability is important. That is why I run the BETA

 

Very stable, indeed.

 

why i get in dx12 5 fps ?
is there something i must change in my settings from nvidia ?

 

Make sure TS is using the correct video card. Also ... for many people the 64 Bit version runs better than tge DX12.

 

Today I hit a problem (OOM scenario load) when trying to edit a large scenario on the Cambs/ECML route - which I didn't have on v75.8.

I checked logmate which had all the usual stuff - but also showed several hundred lines of:

Code:

2024/04/07 10:46:52.130 - [Content] - Trace D:\RGBuild\CoreRelease\Code\DLLs\DataManagement\cBlueprintLibrary.cpp : 421 = Blueprint set not found : JustTrains, LNER_V2

very early in the log.

Usually this just refers to some small blueprint foible (often in very old scenery items) and I ignore them. However this occurred earlier in the log and seemed excessive and unusual. So I took a punt and checked the ScenarioProperties.xml file and found that an old reference to this loco was still in the <RequiredSet> section (the JustTrains loco was in an old version but I had replaced it with the RSC version of the V2 some years ago).

Now, this never used to be a problem - however when I deleted the un-needed entry and tried to edit the scenario I found that it now worked ok.

So it seems that 77.1 is more finicky in the ghost references - something to look out for - especially when editing older scenarios that may have seen some loco swaps in their lives.

 

Perhaps a regular fresh install. . . . . .delete everything and re-install might have prevented that.

 

It's a thought - but I'm not sure that re-installing the scenarios would make any difference. It seems that any affected scenarios need manually editing to remove stray references. I'll keep an eye out for others.

 

The high 85 degrees Celsius and more with the AMD Ryzen 7 7800X3D has also been fixed. TSC runs back under normal CPU temperatures. Thank you!

 

Hi All

Thought I would give the beta a run but once loaded none of my programs that interact with the raildriver dll would work (Cobras program, Third Rails etc).

Is the raildriver dll functionality disabled for the beta purposes?

 

You may need to point the Cobra one software to the Railworks DLL Just as if a new setup. You should not need to reinstall Cobra one software.

 

Cheers for the suggestion but Cobras software only asks for the location of the Railworks directory it doesnt actually ask for the raildriver dll file location.

Having a look around I cant see any new raildriver dll files so I dont think that is the cause of it not working and Third Rails is not working either

 

After a bit of playing around both programs started working but now Im only getting about 10fps both with the programs running and then not running so something about my setup is not playing nicely with the beta, I will play around further when I get some spare time.

For the record this was with the dx9 version of the beta, I have no doubt this will be peculiar to my setup

 

I think I have overcome this:
Log came up with cRailSimSoundSystem out of memory
found I could edit the location in Rw32 and removed sound domes
it now loads in Beta.
Thanks
PeterG 17:14 13/4/2024



I have a problem with one large station/yard (Banbury) which has become a kill zone on my route (Wycombe).
The track there was mostly built about 7 years ago.
Entering the area in the World or Scenario editors causes an instant OOM crash.
The rest of the route seems okay.
In Map view the track and markers are all there and the points work.
The Scenario editor works and I created and watched on the map as an AI loco traverse the area.
The crash happens in both the beta and RW64 and I have done the clear cache and verify/reacquire.
So, a feature request for a crash proof way of accessing a route for editing.

LogMate file - '1984 = Ribbon not found while loading curves, are all network files in synch'
https://drive.google.com/file/d/1lb_r4V7kK6qsuLs_O6nc3ww2cDrWOvua/view?usp=sharing
https://drive.google.com/file/d/1lb_r4V7kK6qsuLs_O6nc3ww2cDrWOvua/view?usp=sharing

PeterG

 

Hi Peter, sadly the ribbon not found message crops up in many routes and has never been shown to actually make any difference to anything at all. Can you post the full log so we can see the start andend of the logging?

 

Thanks
there are several logs here
https://drive.google.com/file/d/1Nq6CIoIDOAWvan7DHJQxv5ew7_9hhwr9/view?usp=sharing
https://drive.google.com/file/d/1Nq6CIoIDOAWvan7DHJQxv5ew7_9hhwr9/view?usp=sharing


2 fresh ones here 1 from world editor the other from scenario ed.
https://drive.google.com/file/d/1Nq6CIoIDOAWvan7DHJQxv5ew7_9hhwr9/view?usp=sharing

 

If you have an NVIDIA card be sure to add Railworks64.exe to your programs list in 3D settings.
I am using The same interface v 3.3.0.6 without any issues and dx9 as well. I have set fps at 30.

 

Has anyone had a problem with the Print statement in this release? I've just been testing changes around the new performance log msg and realised that I'm not seeing any bespoke debug msgs. I've got -LogMate -SetLogFilters="All" so I'd expect to see something.