Railworks America

I just D/L the newest beta update. I had not been involved in looking at this until now but all I have to say is WOW! As you all know I do a lot of re-paints and am actively working on a route and periodic crashes to the desktop and OOM messages have been a pretty frequent occurrence since the core game update back in April when doing the frequent restarts involved with these two activities. Just spent two hours trying to do things to get it to crash and nothing. This looks to be a huge breakthrough in stability so far! Fingers crossed.

Great to hear. I may download it as well soon.

I have installed the beta and the issue I am having is the sky is white from the ground up like fog. I am using RWEnhancer as well. How do I change the settings to get a natural sky?

I suggest you do a clean install , how else can one find out how good / vad the Beta is ?

I did not do a clean install. Just let it do its thing after doing a backup.

Early morning.

Later still morning.

Oh my, that looks cracking. The lack of dump files when reloading and such with reprints sounds exciting too.

I feared the beta would be quite buggy but this may change my opinion, as a little more time elapses.

Thank you for the information.

‘PullmanCar’

I let them go through a couple of versions before I got involved. It was pretty hard to get much from the feed back since the know it all people were either off topic or just blabbing nonsense.

I will play around with the settings today. I am encouraged that buzz has good visual results.
UPDATE: Disabling RWEnhancer PRO seems to have eliminated the issue. Anyone else who is using this on BETA and getting good results I would appreciate any input.

New additional beta released. Anyone have it yet? 76.5a

Just loaded it.
From DTG:
"Hello everyone, we'll shortly be pushing out the next Public Beta build for your attention. Please post your feedback relating only to the build version 76.5a here. If you wish to discuss things not relating to this beta, please use the other forums.

What's Included/Changed

We've spent a bit of time looking at some of the crashes that had been identified in the last build. We felt these were fairly important to get into your hands as soon as possible given the nature of some of the crashes. The specifics of our latest work are:

Reverted Dispatcher change that was intended to make node deletion on pathing failure more robust, but instead could make it more unstable.
Fixed an STL assert failure in Debug build (this could also cause a crash in release builds) - tunnel iterators were being used after deletion when rendering 2D map.
Removed assert in Landscape texture that causes a crash/break in Debug builds.
Fix for crash in loading of Lingbao to Mianchi Scenario 3 (and other scenarios that include reversing sections). Caused by fix to prevent decrementing a stack pointer when at the beginning of the stack. Previous fix was to change loop check, new fix is a special flag to prevent and recover.
Added command line option "-DisableSilverLining" to fully disable Silver Lining to aid debugging the graphics device lost crashes on alt-tab and screen sleep.
Updated to Silver Lining 6.42 to fix D3D device lost error on screen sleep (and potentially others)


With this update, we believe we have resolved the D3D Device Lost error which is caused when alt-tabbing when in full screen. Thanks to wellington's note pointing us at SilverLining as the cause of the crash, we were able to find the specific part in their code and implement a fix. We're hopeful this should be the last remaining element of this crash and it should finally be consigned to history! :)

EDIT: Slight correction to the above, seems I jumped the gun a bit as I'm told that this build does not resolve all instances of the D3D crash. There are some further fixes that we've yet to test internally but will find their way out in due course, likely as soon as we've been able to test them. The new SilverLining library fixed one instance of the D3D error, notably when the game receives a "lost device" message followed by a "reset device". However, there are situations where the "lost device" doesn't trigger, and instead we just get a "reset device". So, this will not be the end of the D3D crash entirely as there are still some fixes we need to test but, we are on it.

We're hopeful you will find this altogether more stable but please let us know your findings.

Best, Steve"