RIGHT THATS IT!!!!

[tonic110]

Hi Guys.
I did post this message earlier, but it seems to have got lost, so if it pops up later I apologise.

I suppose my original message WAS a bit of a rant, and I had no intentions of disparaging Rail Sim.com OR the team.

I was SO annoyed at having to delete the scenario AGAIN (not knowing any other way to fix things).
The creator manual is good at telling you what does what, but thats it. For a beginner, like myself, we are left completely in the dark as to HOW to do things.( Please see my post about drop off instructions in scenario creation)

Now I don`t expect to be taken by the hand and shown every little thing, but a few basic clues would be a good thing don`t you think?
I do not consider myself to be below average inteligence (Though at my age, the phrase "You can`t teach an old dog new tricks" springs to mind) and I spent MANY hours in the "Sheds" at Buxton, as well as "working" in the signal box on the Millers Dale line (Pre Dr Beeching).

I wanted to get back into the "Railway World" even if only graphically? (spelling) and becoming part of creating it. (Re-capture my youth if you will )
Alas it look like it is not to be, this thing has got me beaten hands down. Shame really,I was just starting to enjoy being driven daft by RailWorks.
Tony.

[Acorncomputer]

Hi

These videos and tutorials might help if you have not seen them already - http://railsimulator.blip.tv/

http://www.uktrainsim.com/filelib-info. ... leid=19227

http://www.uktrainsim.com/filelib-info. ... leid=19228

I think your original post has actually been very useful and may help us all to work out what might be going wrong.

[tonic110]

Thank you Geoff, much appreciated.
Tony.

[Wikkus]

I was SO annoyed at having to delete the scenario AGAIN (not knowing any other way to fix things).

Hi Tony, if you're not already using it, I can heartily endorse that nice Mr. Simpson's RWTools and see that he gets beer tokens in return.

With that in your arsenal, you can 'clone' scenarios very quickly and easily. That way, you can make incremental changes to your scenario and always keep the "last known working" copy as a backup. Then, when you discover that the change you just made makes York station explode in ball of flame or that Bath sinks, you can recover quite quickly and re-clone so that you don't have to start all over again.

Another top tip that someone round here gave me was to set up your player train first and make sure it does exactly what you want it to, before you go adding any AI trains or even static stock. Make sure you give it the service type that matches what you're doing and don't leave it as "special". This done, adding AI around to give the desired effect is relatively straightforward.

Hope this helps,

Cheers, Rik.

[lemberg]

Yeh! me too. always proc error after being in the editor, running XP, ati 4870 , 4gig of paired ram, amd 3gig dual core, also some times it comes up as could not write to memory, this always on exiting.

Keith

[miglietto]

I'd love to see some of the red lights turning to green someday .... http://www.railsimdownloads.com/wiki/ti ... us+Updates
This page was update on Tuesday 01 of September.
Could be very interesting to have a date for each defect transition. Some of them are getting too old
I apologize for the sarcasm but who can resist animore ?

Shot at 2009-09-08

[bab7000]

Before blaming RW for every fault, there has been some errors, made by other software/hardware.
One reported, that the new driver for a touchpad on a notebook, made RW go mad. Installing an older driver fixed the problem.
I had a problem, when making a scenario with a lot AI, the editor come with the procerror at a point, when just 1 too many AI was in the scenario. It's reported to RS and in the list of things to check. A fix for that, is to lower the graphics settings in RW.

The problem is, that RW shouldn't break down because of that. But again, they cant know every hardware setup, and take care of every software driver.
RW has some errors, that has to be fixed. And some errors can be fixed by checking your own computer.

And telling RS.com to stop making new content, makes no sense. Derek makes some great stuff (unfortunely most british ), but at some point, he stated, that he doesn't know anything about coding. He's an artist. Not a computer programmer.

Bab

[AndiS]

To be honest, decal object not always rendering on the surface certainly annoys some people, but I guess few will object if they postpone it until the major crashes are fixed.

The missing script for the BSNF signals, wasn't that fixed by the recent patch. Don't have the list at hand, but I vaguely remember something along these lines.

In the signals getting stuck department, they fixed one that was reported. It is correct to keep this item in the list, but it is not like they do absolutely nothing about it.

I believe that the amount of logfiles after crashes which get actually sent to RSC with detailed and not too angry explanation could still be increased.

[RailX]

hello

i think this has nothing to do with different hardware setups. when nearly 80% from the RW users got those "proc error", then it shows
that something works not correctly in the software structure. i have also some problems, but only when i exit the game.
of course derek is no programmer, but the real programmers from RW also seem to despair with this "proc error".
but for all that i look positive into the future.

greetz

Rail-X

[miglietto]

The T Key crash is around since the first release of RS. Many users experienced it and it's pretty easy to reproduce.
I think that with the source code and a decent debugger, shouldn't be a big deal to catch it.
I'm a SW engineer with 20+ year experience in almost every programmming language, so I guess that it should be a very difficult beast to find if in 2 years hasn't be fixed yet.

[CaptScarlet]

I'm a SW engineer with 20+ year experience in almost every programmming language, so I guess that it should be a very difficult beast to find if in 2 years hasn't be fixed yet.

Then as a software engineer you would also know that it is all a matter of priorities and where resources should be best focused ?

John

[Basherz]

What "T" crash. Never heard or seen this in the 3 years, with RS & RW, I've been plotting DEM??

[Acorncomputer]

What "T" crash. Never heard or seen this in the 3 years, with RS & RW, I've been plotting DEM??

Same here really. I have created terrain for 3 routes and not the slightest problem.

[Darpor]

Have to say I am the same here. Used DEM quite a lot and never had a "T" crash. Starting to feel like I am missing out.

[miglietto]

What "T" crash. Never heard or seen this in the 3 years, with RS & RW, I've been plotting DEM??

It happens when I use SRTM1 DEMs and I'm on a tile sitting over 2 dem files (eg. N45E009.hgt and N46E009.hgt)
With SRTM3 data the crash don't show up. So time ago I adopted the workaround to use SRTM1 and switch to SRTM3 in the "hot" places.

Then as a software engineer you would also know that it is all a matter of priorities and where resources should be best focused ??

I'm well aware of priority mechanism but I cannot know how are assigned to the various bugs.
In any case, even giving to this bug the lowest priority, even having only 1 guy working on the code, 2 year seem too much to fix it.