Railworks proc2.exe

[The trainman]

Help needed.
I am having problems with railworks 3, and it's more to do with westcoast mainline north.
I downloaded from the steam site 360 addon and I can get it ti start playing the it crashes, saying that Railworks proc2.exe stopped working and need to close, I get this everytime I play this westcoast mainline addon.
Can someone out there help with this rather annoying problem.
I have windows 7 opperating system, with a 2 Gig memory, and a 1gig Radeon HD 5450 graphics card with 2gig max hyper memory.
:cry: :cry: :cry:

 

[mbonwick]

Sounds like you may need to drop your settings a little, WCML is a very demanding route.

 

[The trainman]

Thanks for you reply.
Which setting would you advise me to reduse, as most of the setting are on their lowest now.

 

[Crossover]

I highly suspect your 2GB of system RAM may be playing a part in this potentially.

I currently run on a laptop with 2GB RAM, the majority of routes play fine on lowest settings whilst pretty much maxxing out the remainder of my RAM.

The WCML route however either just crashes on completion of loading or is very very slow to respond before also crashing, maxxing out usually at 1.3GB RAM.

Having played the route on a friends PC who has 8GB RAM (OK, we had it on max settings and with TSX on), I had a glance at the usage in Task Manager and proc2.exe alone was using 2.5GB - 3GB IIRC (and I don't think this would include the graphics memory)

 

[The trainman]

Thanks for you reply Crossover.
I will be installing a 4gig of ram within the next few weeks and will let you know how I get on.
I have had a look at some other forums site's and the steam site, and they all say that WCML take a lot of ram.

 

[Johnny_w]

Hi trainman a little more details about your Railworks pc would help. For example I use an Intel Core Duo 2.8Ghz with 4Gb Ram and a 2gb ATI HD5450 graphics card.

WCML I get an average of around 18FPS with very little stuttering or micro lags. Around Glasgow is more painful, but I can live with it

Railworks appears to be very processor intensive.

I hope I can be of some help.

Best Regards,

JW