Problems With Update 97.8a - Yes or No

[thackalane]

No problems with route editing, just the very poor frame rate in the Delivery Day scenario.

Mike

[dipper6]

I tried the Hedborough test and got a crash.

[Railworks7053]

Did the Hedborough North test, placed 6x different trees and a few houses and saved.

No crash, so i have voted appropriately.

cheers,
Chris.

[Darpor]

Same here, tried both the Hedborough and Newcastle - York "tests" without issue.

[choccy]

I did the Hedborough Test and it crashed when I planted a tree on the tile mentioned earlier.The route loaded again but crashed when I attempted to access the damaged tile. I examined the tile in the scenery folder and found it was, as reported by many, 0kb. Once replaced with a backup we were back to square one, but planting a tree again caused another crash etc.

Mark

[CaptScarlet]

I did the Hedborough Test and it crashed when I planted a tree on the tile mentioned earlier.The route loaded again but crashed when I attempted to access the damaged tile. I examined the tile in the scenery folder and found it was, as reported by many, 0kb. Once replaced with a backup we were back to square one, but planting a tree again caused another crash etc.

Mark

Pretty much the same result that I just got. Crash on saving after placing a tree in the same spot mentioned previously.

John

[RSderek]

Thank you for all responding and confirming.
I can confirm the crash is valid and repro'd here.

We will look into this asap.

regards

Derek

[CaptScarlet]

Thank you for all responding and confirming.
I can confirm the crash is valid and repro'd here.

We will look into this asap.

regards

Derek

Hi Derek, that is good news, it is always difficult to fix these type of things if you cant reproduce it in house.

Hopefully a fix can be found quickly and everyone can get back to normal activities.

John

[stuart666]

Can I go home yet?

LOL.

[TractorBasher]

I have a scenario in production which involves shunting in Didcot yard. I just tried to run it and initial loading took the usual amount of time, but when the scenario briefing box appeared I just had a black screen. After 10 or 15 seconds all the scenery and rail vehicles appeared in the default state they should be in at the beginning, but the screen was frozen. There was no sound and nothing was moving, like exhausts from locos. I couldn't close the scenario briefing, or move my view with the arrows or mouse. Ctrl + Q didn't work to quit so all I could do was switch to the task manager and close RailWorks.

[CaptScarlet]

I have a scenario in production which involves shunting in Didcot yard. I just tried to run it and initial loading took the usual amount of time, but when the scenario briefing box appeared I just had a black screen. After 10 or 15 seconds all the scenery and rail vehicles appeared in the default state they should be in at the beginning, but the screen was frozen. There was no sound and nothing was moving, like exhausts from locos. I couldn't close the scenario briefing, or move my view with the arrows or mouse. Ctrl + Q didn't work to quit so all I could do was switch to the task manager and close RailWorks.

If you can send it off to RSC support as it may be a similar issue to the default delivery day scenario.

John

[TractorBasher]

Decided to try running a different scenario so loaded my "Deluxe Cornish Pasty". When it loaded one of the services failed because it couldn't find its destination. I went into the editor and found the service and the destination box was empty. So I added a destination and saved but it still says can't find the destination when I reload.

[msdejesus]

Thank goodness I run RW in offline mode, so I haven't been affected by this update, that scenario you mention is one of my favourites. I think I will wait until all the dust settles before updating RW again.

For now, methinks I will stick to my out-dated version.

Manuel (old-fashioned )

[Neptune50006]

Thank you for all responding and confirming.
I can confirm the crash is valid and repro'd here.

We will look into this asap.

regards

Derek

No more biccies until it's fixed!

[Wikkus]

Hmm... I haven't voted in this one 'cause I don't think the issue is quite so black and white as this. One immediate thing I've noticed post-update is that I am no longer getting the ProcError on exit following an editing session.

Sure, I can force a crash as per the 'instructions' regarding Hedborough North earlier in the thread, however, curiously, it is not corrupting the route (and writing a zero-length file entry) and the route remains entirely usable.

Given that I don't normally do any route creation, this is not an issue currently relevant to myself

So far, this has been a very positive patch for me; I am getting more into the creation of scenarios and certainly not having the thing crash every time I exit an edit session is very nice to have.

Will be watching this with interest.

Rgds, Rik.