Atomic Systems

Now normally I don`t complain BUT this is taking the Biscuit !!!!
As some of you know, I am very new to simming. Being a "newbie" I am finding it difficult enough to master the art of creating scenarios as it is.
In the last 2 days I have been Kicked back to the start screen around 20 times, usually in the middle of editing. No other programme does this, ONLY this one, so I aint blaming the pc. I have lost both sound and activation of the A.W.S. system (which took a time for me to fix ) my loco keeps disappearing , leaving only the Icons showing.
Passengers are left sitting in the air, numerous "not connected to destination" failures either that or "can`t find destination".

Then of course there is the famous "Railworks Proc" message. Sorry I am going on but it has got me .
WHY did Rail Simulator.com even THINK about releasing this programme WITHOUT sorting these Bugs?

It would seem that they are very quick at releasing new content and improving the scenery (No offence meant Derek).
WHY can`t they be even half as fast at fixing these DAMN bugs (`scuse me).

Tony.

Thinking a litlle bit of the same here. Why cant a reported bug even be recognised on the Wiki site, so the users can se "We are doing something". This bug I´m talking about has been reported more than one time, including screenshots which shows the bug. This is a litlle frustating.

No offence ment to the Team

The thing is Erich, when people like yourself take the time and trouble to create such good routes, other people WANT to create scenarios for them.
The problems and bugs kind of knock the stuffing out of (especially) new users,like myself, and make them feel like ditching the whole thing.
Tony.

Ah! I thought everything had gone a bit quiet on this forum this last month or so. I had begun to think that the AI traffic and single line working had all been fixed and everything was chickaty-boo with RW now after all the Steam updates. I was nearly going to buy it!
Close shave! Phew!
Ted.

Forgetting the proc errors etc, for the problems with the actual scenario creation have you sent a copy of the scenario to the team explaining what is wrong or is this just a rant?

Obviously, content is easier to fix or to produce than the game core.

Also, this "ProcError" is not one bug. It is the equivalent of crash to desktop or "phoning home". So what you really see is a set of bugs, and no one even knows the number. It might well be that they fixed one or the other but it went unnoticed. I vaguely remember one or the other post of someone who stated that the ProcError was gone for some of the occasions on which it happened. But naturally, people post rather when they have bugs than when they don't because then they are happily enjoying the game.

This is not to say that I don't understand your frustration.

Hi
i have just posted a simular comment on another thread,imho rs.com should forget loco building fix the program FIRST!
i am 4 months into my second route project,and the darn proc.exe error is driving me bonkers,the steam updates seem to be making things worse,the updates seem to be being put out with minimal testing,so much so that i have deleted all moving road traffic from my route,if i see another bus doing a wheelie ,i,ll do my nut!instead of model making gimicks please! please! put the effort into correcting the issues that really matter.
Signaling,Ai,disappearing assets,the rural wire fence disapearing fence post bug has been with us since RS,all we seem to get is "were working on it"it seems to me that most of RS.coms efforts are put into producing locos at £12 a time,now i know that ,the revenue from the locos funds developments,the fact is we have paid our money for the product,future development should be about improvements, not fixing the original product .
I am not given to rants ,and i know RS.COMS oppinion of the the community is not very high,but can you please listen to us at least sometimes,you will find us a friendly bunch(well most of us anyway)who share your passion for Railworks to succeed.
Regards
Kevin

The problem is with the proc error, it must be very hard to locate and fix due to the multitude of different systems people use,the way they use them and the way they use RW for that matter. Is everyone who gets the error sending a report to RS.com? On a personal note, I have had the proc error only once since the very first update and that was my fault. I am permanently in the route/scenario editor so it begs the question, why am I not seeing it constantly like everyone else seems to be?

Darpor wrote:The problem is with the proc error, it must be very hard to locate and fix due to the multitude of different systems people use,the way they use them and the way they use RW for that matter. Is everyone who gets the error sending a report to RS.com? On a personal note, I have had the proc error only once since the very first update and that was my fault. I am permanently in the route/scenario editor so it begs the question, why am I not seeing it constantly like everyone else seems to be?

This is indeed a good question. Another clue must be that it was not a fault in Rail Simulator. I am sure that it will eventually be fixed but I think patience is required.

I am still using XP ... is this perhaps a Vista problem?

Hi
Geoff you could be right about Vista,i am on Vista,the error when in the route editor is very frustrating,although i save frequently,inevitably i loose some of my work,route building in RS/RW is hard enough and time consuming as it is without loosing work through this error.
To me it is a question of priorities ,build loco,s or fix the core program,or if RS.COM has not the expertise inhouse to fix the errors, then hire in troubleshooter who can.
If your cars engine does not work its no point fitting fancy wheels and doing a paintjob.
Regards
Kevin

Hi Kevin

I have never really had a problem in RS with crashing, although it does happen and when you do something predicable mainly. I do not have Vista on any of my computers and I am having another one built at the moment that will be dual booted with XP and Windows 7. This could be just a poor operating system that RS/RW cannot really cope with.

I am Vista and receiving none of these problems. Maybe the problem needs to be approached from why it does work on some systems as opposed to why it doesn't which seems to be the logical way to look at it.

Acorncomputer wrote: I am still using XP ... is this perhaps a Vista problem?

Unfortunately not Geoff, as I use XP and get this on exit only, but then I have a similar error in RS also!!

Perhaps someone who knows a bit about computers could draw up a survey sheet that we could all complete giving details of our systems, anti virus software, hardware, etc, and this may help to identify exactly what circumstances cause what errors. The solution may be simpler than we think.

Basherz wrote:

Acorncomputer wrote: I am still using XP ... is this perhaps a Vista problem?

Unfortunately not Geoff, as I use XP and get this on exit only, but then I have a similar error in RS also!!

Me too!

I have had it since day one and i run XP.
I also have had a similar problem with RS, also from day one and that was never rectified.