Railworks America

When I do a quick drive on the Springfield route it loads and than crashes with this error

Saved log to...

C:\Program Files

(x86)|Steam|steamapps\common\Railworks\TempDump\

Exception Code 0xC0000005

Exception Info: ACCESS VIOLATION

Please contact our Customer SUpport Team at
https://dovetailgames.kayako.com/

RU trying to load it with the new 64bit? If you are it's a known problem and no fix yet.

buzz456 wrote:RU trying to load it with the new 64bit? If you are it's a known problem and no fix yet.

Yes I'm using 64bit also lets hope they fix it

Well you can still run it with 32bit.

I agree. WIth the 64 bit the box of problems opened up and I bet it will take a while to get all problems sorted out.

buzz456 wrote:Well you can still run it with 32bit.

true I just wanted to see if the frame rate got better

I finally found a fix. Delete the Global folder from Assets\VNHRR\Springfield\Scenery and it loads in 64-bit.



Bingo!

Well, if it was just the VNHRR then I’d be inclined to try this, but.....

If I edit the FRC in 64bit, I still get the Access Violation error.... 32bit is just fine. So it’s how the 64bit routines are using memory....

I bite what's the FRC?

Feather River Canyon. The 64-bit editor is a mess right now.

Just a FYI I got rid of the global in the scenery and it loaded like a champ. There are a few odd things going on however I have edited things in 64bit and haven't had any problems.

A further tale of strangeness (a word I just invented) is I couldn't get our MRL to load. Checked with Bob and he was not having any problems so I started poking around. In the Kuju RailSimulator Environment\Terrain\grass there was a file it didn't like. I didn't hunt down the exact one but there were some that got updated on 10/13. I took the folder from my backup and SHAZAM it loads just fine now. 'Splain that to me huh?

Thanks very much for sharing the results of the investigation. The global scenery is something we hadn't looked at yet.

Keep a backup of the "global" assets folder mentioned a few posts above if you decide to try this workaround on your PC. Deleting this folder will remove all the distant scenery objects from the route, which are mainly the distant forests and suburbs that are visible beyond the standard 2-mile scenery draw distance of the sim. The route will look a bit worse without them when you are travling the open countryside or crossing the river. Those assets located in the "global" folder are all flagged as "global scenery" in the editor, making the visible all the time (same like for example the skyscrapers in NYC on the NY-NH route). This of course means an increased RAM and VRAM footprint, but the old version of the sim could handle it okay so I never expected this to be the cause for the crashes in the 64-bit program.

+++ Update +++ Update +++ Update +++

We believe we have found a fix for the crash with the route in 64-bit TS. Wayne has tweaked the objects for the "global" (always visible) distant scenery items for a somewhat reduced resource footprint and that seems to have done the trick. (Don't ask us though why the original, more detailed objects work fine in 32-bit TS which theoretically should have less resources available for them).

Anway, here is a patch:
http://vnhrr.golden-age-rails.com/files ... -%20WC.zip
Just install it directly to your Railworks main folder and allow it to overwrite files. If you want to create a backup of the original files first, back up these:
- the entire folder Assets\VNHRR\Springfield\Scenery\Global
- the file Content\Routes\c427bd51-0f8f-4edb-948b-e9b5ceadd48f\Scenery\GlobalScenery.bin

Please note that this patch has so far only been tested by Wayne and me. We hope that it works for everybody, but we can't guarantee it. Please report back if it doesn't work for you and the crash persists even after installing the patch.

Cheers
Michael

I loaded into the first scenario for the S-2 that would constantly crash. This patch seems to have done the trick. All of the scenery is back and all is working well.



Hot TOFC also works.

I'll do a full run of the route later today and report back. Thanks for fixing this!

Has somebody tried something similar to Michael´s fix in FRC?