Atomic Systems

As already discussed in two previous threads, some people are reporting problems specifically related to route creation and switching to the scenario creator. This doesn't really give us an idea of what the balance is, is it happening to most of us or very few? Please answer in the poll if whether you are having problems or not and feel free to add anything by way of reply regarding certain situations that have caused it. This may help those that are not having the problem to avoid any potential issue. I have set the poll at just 2 days so hopefully by Sunday night we can have some sort of figure as to what percentages are involved.

No problems at all.

gav12 wrote:No problems at all.

Ditto.

I have backed up just in case, but nothing seems a problem.

Saying this, I have had a problem on one of my Newcastle to York Scenarios, just crashes when I get to the start of it.

I had to vote yes, but it only happens on one route which isn't mine and is a work in progress ( it is also not the latest version of it ).

I have tried editing ( by moving the length of a marker or portal link postion or signal link ) on the two default routes plus the IOW, and Crouch Valley and then saving and it did not crash.

John

No problems to report (so far).

No problem with editing, 3rd party or my own.

Clive

Had an initial problem, but since that - none, touch wood, but not used it a great deal yet.

Touchwood none,regular backups required...

Can I go home yet?

RSderek wrote:Can I go home yet?

Well, a quick trip to pick up some more digestives might be allowed .

Seriously, I've had a couple of RailworksProc errors in the sim itself but no editor problems as yet...

Paul

I think we ALL have a problem. Before more and more people come here happily saying they have no problem at all, and RS.com thinks it's not worth looking into it, why not doing a test?

- Make a backup of route Hedborough North (it's the folder 00000007-0000-0000-0000-000000000000)
- Startup RW, load Hedborough North - free play
- Go to tile -000003+000001
- Place something on that tile, like a tree.
- Save it
- Sit back and enjoy

If you prefer, try on the route Newcastle to York, same procedure except for the tile (-000002-000011), the route folder to backup is 00000003-0000-0000-0000-000000000000
This can happen in any route you edit, if you hit the problematic tile(s)
If nothing abnormal has happened, then you're lucky, sorry for wasting your time.

I shall follow that in the morning raildumper, do a backup for the two routes and test the tiles suggested although I reckon it is probably unfair to say that RS.com are not looking into it.

I got no problems, im finally happy that RW don't break when I close the program.

Did the test raildumper
And it failed.

Alex

Working on zipping the default routes now, a guy over in the US is reporting similar symptoms when trying to move into the San Bernardino area on the Cajon Pass route. I tested separately, first made a new scenario in my route, saved and tested, exited, no crash. Restarted railworks, opened the world editor and added half a dozen new signals, saved and tested, exited, no crash. Restarted railworks, opened the world editor again, spent 20 minutes to half an hour or so placing and linking new signals, hit F2 to save and got the "memory can't be written" proc error. "Something bad happened" whenever I tried to move into that tile again, further investigation showed that the \scenery\+000000-000002.bin file was zero bytes. Deleting that or replacing with the 71KB file from the backup fixes it, altho one other guy in the US is reporting a zero byte tracks.bin file instead of a corrupted scenery file.

EDIT: Just tried the Hedborough test, only instead of adding anything I deleted one of the tree clumps, same result - crash on save, the \00000007-0000-0000-0000-000000000000\Scenery\-000003+000001.bin is zero bytes.

EDIT again: Confirmed same thing on Cajon Pass ("Barstow - San Bernardino") route;



Add one truck, save and crash, zero bytes for that scenery file. I suspect the best idea is not to edit routes until they get this one sorted out, I've shifted development back to railsim until I get these signals finished or I'm never gonna get version 2 out.