Railworks America

Ok here goes, I have The Chessie Big Sandy Sub, in it's first beta, My beta tester can run the route with no problem, can edit and create in the world editor with no problem, But as soon as he tries to edit or create a scenario the dreaded SBHH crash. Of course on my end I have no error's or crashes. After 9 months of working on the route and being so close to a release I could really use a few suggestions as to what may be the cause. Both Myself and my beta guy have run the route thru RW tools reporting no errors or missing assets. I have went thru the Tut. on fixing third party routes and still no go.
Not sure what to do next.

I would suggest this, if your using just one other person other then yourself to test the route, add one or two more beta testers to your team, this way you can see if they have the same problem or if it's local to one machine.

Best,

Roger

That may be an option, But for now I was looking for some insight into the finer workings of the scenario editor, and it's file structure within the game.

Is there no one who can offer some insight into the inner workings of the scenario editor?

Can your friend edit or create scenarios in other routes?

harryadkins wrote:Can your friend edit or create scenarios in other routes?

Yes.

Coaltrain1 wrote:Is there no one who can offer some insight into the inner workings of the scenario editor?

Have you tried reading the manual? It's out of date, but the basics are all there.

Forgive me if this is way off in regards to your problem. Gotta catch a bus in five minutes so this might be alot of "rambling" but:

Does the sim crash as soon as your beta guy hit the "edit scenario" button from the main menu? Or does the "edit" scenario load only to crash as soon as he does something in the scenario editor.?

Can your beta guy untick the providers? If so, untick them all, save, exit completely, reload scenario and try now.
How big is the beta guys Kuju folder?
Did your beta guy clone a scenario lately? If yes, check the size ( in megabytes), thinking of "bloated" scenario files.
Has your beta guy removed everything, scenarios and all, reinstalled a "vanilla" / "default" TS2013 and started over?

Create a batch file, ( make a backup of your work first! )

Notepad file, insert following:

del/s *.pak
pause

Save file as clearblueprints.bat and place the file in TS2013 root folder. Run it, now try creating a scenario.

Thank You Sir,
It only crashes after he tries to save a new scenario.
He did completely re install TS13
Again thank you for providing an avenue to follow to start looking into. I am not a file guy so really was not sure where to start.

How did the bug hunt go ? Are you guys up and running on TS2014 ?

Yes, all is good and the bugs are gone, just needed the right kind of poison.