RailWorksProc error

[Wikkus]

So far the only error s i get are a proc.exe crash every time i close the program...

To avoid this being a "me too" post, er, me too, with the qualification that it's only if I use the editor. The 96.9a patch appears not to have helped in this respect.

I take it this is the known issue on the wiki as I do probably use the editor every time ..

I just did a quick test of the theory and in every case, only got a Proc error on exit when I'd used the editor.

Rik.

[ka959]

So far the only error s i get are a proc.exe crash every time i close the program...

To avoid this being a "me too" post, er, me too, with the qualification that it's only if I use the editor. The 96.9a patch appears not to have helped in this respect.

I take it this is the known issue on the wiki as I do probably use the editor every time ..

I just did a quick test of the theory and in every case, only got a Proc error on exit when I'd used the editor.

Rik.

And I use the editor a lot every RW session I play or work on, so it's therefore unavoidable I guess, for now, at least. Cheers.

Regards...

Jim McDermott

[Wikkus]

I remember back in the Windows 95 days, about Swapfiles, but haven't a clue where it is, nor how to do this with Windows XP ! Care to explain how this is done, as it might help me somewhat ? Please, and thanks heaps. Cheers.

Hi Jim,

It's pretty straightforward to make the changes to the size of the file(s), but as I said in my post, changing just the file size(s) by themselves are not the complete answer, the defragging is just as if not actually more important.

Also, one of the reasons I failed to mention for doing this is because in 32-bit versions of Windows, there's a 4GB limit to swapfile size, therefore, if you calculated that a 6GB file is what you need, you'd want to split the file up into chunks, either across drives (which I tend to do) or, if you have only the one drive, then across multiple files.

All you need to know is in this article here at Microsoft, but to get to where you need to be, r/click "My Computer", left-click "Properties", click the "Advanced" tab, click the "Settings" button in "Performance", click the "Advanced" tab, click the "Change" button and do what needs to be done on the resulting screen.

A heads-up on a potential "gotcha" at this point: You must make changes and click "Set" on each drive for the changes to take effect.

I'm happy to go into more detail if any of this is unclear.

Rgds, Rik.

[bigvern]

Proc error still present on exit even after latest update...

[ightenhill]

Proc error still present on exit even after latest update...

According to the wiki its still being investigated.. Then again according to the wiki the Advanced options still dont work and the BNSF signals should have been fixed..

[ka959]

Proc error still present on exit even after latest update...

According to the wiki its still being investigated.. Then again according to the wiki the Advanced options still dont work and the BNSF signals should have been fixed..

The Advanced Options definately do show up for me now, and were greyed previously. I can adjust the screen brightness now, unlike previously. That's better ! Haven't tried the BNSF signals yet at all, though, but hope to soon. The Proc. error still comes up at exit of RailWorks, though, if I've used the Editor even once. Not a serious problem, but it would be good to see the back of it sometime soon, though. RailWorks just seems to take a while switching back & forth between Route Building & Loco & Wagon mode, even on a medium-sized route I create myself, though, and the wait is a bit tedious to say the least.

Regards...

Jim McDermott

[CaptScarlet]

Haven't tried the BNSF signals yet at all, though, but hope to soon.

Regards...

Jim McDermott

You will have too wait until the next bigger update I suspect as they weren't included in the latest one.

John

[Hyuril]

Hello
I wish to thank all the people contributing positively as the RailProc error bug does not affect now my game. I can enjoy the RailWorks right now.
Thanks to all
@@++

[bab7000]

Well i thought this important enough to bump this thread up as i seem to have eliminated the dreaded proc error in the editor or playing my scenario! I have reduced the settings in the options screen down a notch to medium density on some of the settings, like particle density/passenger density/low detail shadows off/terrain texture and object texture/scenery detail 9, all other settings are on high. so far so good.

Mart

I tried it, and it works Now I can continue working on my scenarios.
But then it seems to be a hardware problem, and not that much of a RW problem ? I know, that RW shouldn't break down, but knowing the problem helps a lot until RS.com makes a patch for it.

Bab

[smarty2]

Hi Bab, i have both a liquid cooled 8800gtx and quad core phenom, you would have thought it would handle it o.k? But don't forget Bab the DK2000 route ran flawlessly without any traffic? Maybe the dispatcher put's too much load on the cpu?
Glad it's working for you now
I am getting the dreaded nvlkmm error now! Just can't win

Mart

[Wikkus]

Peeps,

this may be unrelated but it'd be useful if Someone Who Knows (tm) could explain... I just ran a quick edit session with logmate enabled and on exit (with accompanying Proc error), I noticed this in the log:
Blueprint being deleted with non-zero ref count

ASSERT(mRefCount == 0);

cBlueprint::~cBlueprint()

c:\dev\railsim\code\publicinterfaces\../Libs/Blueprints/cBlueprint.d.h : 65

Now, there is no c:\dev on my machine, the C: drive is a big, empty hole used for swapfile and some backing-up. Is this significant?

Rik.

[CaptScarlet]

Peeps,

this may be unrelated but it'd be useful if Someone Who Knows (tm) could explain... I just ran a quick edit session with logmate enabled and on exit (with accompanying Proc error), I noticed this in the log:
Blueprint being deleted with non-zero ref count

ASSERT(mRefCount == 0);

cBlueprint::~cBlueprint()

c:\dev\railsim\code\publicinterfaces\../Libs/Blueprints/cBlueprint.d.h : 65

Now, there is no c:\dev on my machine, the C: drive is a big, empty hole used for swapfile and some backing-up. Is this significant?

Rik.

No it isn't. just ignore that part of any error

John

[Wikkus]

Is this significant?

No it isn't. just ignore that part of any error

John

Fairy nerf. Thanks for clearing that up -- one less thing to be bothered about

Cheers, Rik.

[jkxx74]

Blueprint being deleted with non-zero ref count

ASSERT(mRefCount == 0);

cBlueprint::~cBlueprint()

c:\dev\railsim\code\publicinterfaces\../Libs/Blueprints/cBlueprint.d.h : 65

Actually that might be a part of the problem given what I've found out. It simply says the blueprint object could not be destroyed - could cause problems later on. Anyway, quick fix for a number of the random "railworks has stopped working" errors - only if you are getting the errors while driving.

Before getting close to an area which causes the error, disable the driver aid (F3) so that it disappears. You should now be able to drive through the affected area without any problems. The drawback is that as soon as I try to reenable the driver aid, railworks crashes with a BEX/APPCRASH error signature. Definitely something for the RW devs to look at.

-jkxx

[RSAdam]

Hiya,

As per our Wiki status page request.

Can you package up and mail these problems to support. While we cannot offer a repair service, it will help us immensely in understanding what users are doing to cause RailWorks to crash. This in turn helps us to better cater for potential issues in the future by knowing how users operate

Incidentally, if we do find trends in these such occurances (2Dmap and Driver guide initiated crashes while driving) does anyone have any preference as to how we should feedback our findings?

Cheers