Editor needs sensitivity training! (now a bit "off track")

[OldProf]

A couple of months ago, I was prepared to declare the Timetable Editor finally stabilized. Now, I'm glad I kept my mouth shut. Over the past week or so, it has become more and more sensitive, shutting down abruptly for no apparent reason without even passing through an SBHH message. One second I'm editing and the next I'm looking at a dump message, knowing that not even RSC can read the dump-files anymore.



Have any other scenario writers noticed this?

[mrennie]

A couple of months ago, I was prepared to declare the Timetable Editor finally stabilized. Now, I'm glad I kept my mouth shut. Over the past week or so, it has become more and more sensitive, shutting down abruptly for no apparent reason without even passing through an SBHH message. One second I'm editing and the next I'm looking at a dump message, knowing that not even RSC can read the dump-files anymore.



Have any other scenario writers noticed this?

I haven't had any SBHHs in the editor for a long time now, and I was using the Timetable Editor a lot recently.

Have you done all the usual things, like clearing the cache, checking the integrity of the game files, and doing a chkdsk /f from a DOS command window?

[Railfan49]

I'm disgusted with those messages already. I hope they put out a fix for those

[OldProf]

Have you done all the usual things, like clearing the cache, checking the integrity of the game files, and doing a chkdsk /f from a DOS command window?

You bet! Incidentally, in the "hand is quicker than the eye" department: lately, when I clear the cache from within RW, this pops up:



Need I say that opening Steam support is useless? There's not a word about this annoying little glitch. Thank you, Steam, for once again making my life a bit more frustrating.

[Bananarama]

I've had two in the past few hours while rotating signal objects - no crashes since last summer, however.

[buzz456]

If you just wait a minute you won't get that message. You're just too fast for the computer. I had the task manager open after that happened to me a couple of times and it just takes a few seconds for the game to disconnect. Apparently the cache clear tries a instant restart. I was trying to get a object to show up the other day so I kept shutting down and restarting and I got that message if I tried to restart too fast.

[OldProf]

If you just wait a minute you won't get that message. You're just too fast for the computer. I had the task manager open after that happened to me a couple of times and it just takes a few seconds for the game to disconnect. Apparently the cache clear tries a instant restart. I was trying to get a object to show up the other day so I kept shutting down and restarting and I got that message if I tried to restart too fast.

It's not a matter of my waiting or not ... that annoying little message just pops up on its own because Steam is suddenly too hyped. Humorous, isn't it, that Steam takes its own sweet time opening RW when a player double-clicks the game's icon, but then turns around and hits restart half an instant after the cache has been cleared. Or not! Yesterday, after asking for an in-game cache clean-up and receiving in return an overly hyped restart failure, I took a minute to open the Assets folder and run a blueprints.pak check: the search found more than a dozen of them! So perhaps this irritating message's appearance means that RW is not clearing the cache at all anymore?

[buzz456]

Interesting thought. Needs further investigation.

[Chacal]

I don't use this function in-game anymore.
I just use a script before I start the game.
It's basically a single DOS command:
DEL *.PAK /S

[PapaXpress]

I don't use this function in-game anymore.
I just use a script before I start the game.
It's basically a single DOS command:
DEL *.PAK /S

[OldProf]

I don't use this function in-game anymore.
I just use a script before I start the game.
It's basically a single DOS command:
DEL *.PAK /S

Interesting idea ... I haven't used DOS for a long time. I tried selecting "Run" from the Windows 7 start menu and pasted your command into the box, but all I got was a "cannot find DEL error message. Old dog here needs to be taught new trick?

[buzz456]

I think with win7 you have to go to accessories to get to the dos prompt. I put a shortcut on my desktop for it.

[artimrj]

Tom unzip this and put the nat file in your Railworks folder. Then all you have to do is browse to is with Win Explorer and double click it. You can also make a shortcut to your desktop for it and run it from there.

[OldProf]

Thanks, Bob.

[PapaXpress]

I think with win7 you have to go to accessories to get to the dos prompt. I put a shortcut on my desktop for it.

Correct. I have mine pinned to the task bar.

You can also make shortcuts to your batch files.