Problems with Scenario Editor

[harryadkins]

Has anyone else been experiencing problems with the Scenario Editor? Whenever I try to edit a scenario, Railworks crashes and I get the Windows 8 message, "Railworks.exe has stopped working." This issue happens with both DTG and Third Party routes. I have restarted the computer and verifyed the game cache with no success.

Harry

[_o_OOOO_oo-Kanawha]

On what route exactly, or all of them?
You can play the scenario you want to edit?

Fire up LogMate.exe from the Railworks root folder and keep an eye on it while Railworks loads.

[harryadkins]

Thanks for the help. Logmate confirmed that the PONtrack.bin file was back on my computer and causing the problem. I deleted it and all is well. My question is how did it get back on my hard drive?

[mikesimpson]

Hi Harry,

After running the program 'Search Everything' (a freeware search engine for your hard-drives), I discovered 12 copies of PONtrack.bin on my PC, 8 of them in back ups of my Assets folder on USB drives which did not matter, but also 4 copies in my main Assets folder in various sub-folders.

You never know what is there until you have a really good look...

Mike

[chrisreb]

I remember having to remove it from a number of places to get rid of it.

[OldProf]

It seems that this problem has been resolved, so I hope that no one minds my bringing up something similar: our old enemy blueprints.pak.

On several occasions lately, I've searched the entire Steam folder for this beast, always finding 50 or more copies, which I dutifully delete. However, as soon as I run TS2015 again, no matter why or what I do, another search for blueprints.pak turns up another pile of files.

I don't remember anymore whether some copies of this creature are actually necessary to TS's operations or why multiple copies are generated or, for that matter, why they are considered undesirable. So, I'm hoping to encourage some discussion of these matters.

[Chacal]

Yes, they are recreated as needed.

Every time the game needs to load assets, it will do this:
- look for blueprints.pak in the provider/product folder;
- if it doesn't exist, create it and pack blueprints* inside it;
- load the needed blueprints* from blueprints.pak.

This is why, when you make changes to certain blueprints, you have to delete the corresponding .pak file, otherwise the game will never see your changes. Cached files (inside .pak files) have precedence over uncached ones. It is normal behavior for a caching system, which aims for greater performance.

This behavior is entirely different, it is even the inverse, from how the game uses .ap files, for which an extracted file has precedence over an archived file. This is normal behavior for an archiving system, which aims for easier maintenance.

* this concerns only certain blueprints. For example the engine blueprint is in there, but the camera blueprint is not.
I know this from experience, but I never actually looked in a .pak file so I'm not sure which ones are in there.

[frankenthal]

This is what I get when II open my editor, I honestly don't recall if it started after an update or not.

[RunTimeError 10:42:54 PM] Trace mdump.cpp : 422 = error handlers have been set
[Content 10:42:54 PM] Trace cBlueprintLibrary.cpp : 417 = Blueprint set not found : Kuju, RailSimulatorCore
[Content 10:42:54 PM] Trace cBlueprintLibrary.cpp : 448 = Blueprint set not found for: Cameras\EditCamera001.xml
[RunTimeError 10:43:13 PM] Duplicate Scenario GUID in SerializeDatabase
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] ASSERT(mScenarioMap.find( scenario->getScenarioID() ) == mScenarioMap.end());
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] cScenarioDatabase::SerializeDatabase()
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] cScenarioDatabase.cpp : 1236
[RunTimeError 10:43:13 PM] Duplicate Scenario GUID in SerializeDatabase
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] ASSERT(mScenarioMap.find( scenario->getScenarioID() ) == mScenarioMap.end());
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] cScenarioDatabase::SerializeDatabase()
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] cScenarioDatabase.cpp : 1236
[RunTimeError 10:45:27 PM] Trace mdump.cpp : 381 = Dump taken

[OldProf]

I know this isn't of much help, but I've used the 2016 scenario editor a fair amount already without encountering any such problem, although the crashes typical of every version of this tool do persist in its latest incarnation. I'm referring to inconsistent break downs, possibly in response to "too many edits" [without ever being able to predict how many], "too many saves" [ditto], etc. Let's face it, folks, our relationship with the editing tools remains strictly adversarial, so it's just something we have to grin and bear it between cache verifications. I'm willing to say that, in most cases, the end justifies the means.

[tomgiorgini]

This is what I get when II open my editor, I honestly don't recall if it started after an update or not.

[RunTimeError 10:42:54 PM] Trace mdump.cpp : 422 = error handlers have been set
[Content 10:42:54 PM] Trace cBlueprintLibrary.cpp : 417 = Blueprint set not found : Kuju, RailSimulatorCore
[Content 10:42:54 PM] Trace cBlueprintLibrary.cpp : 448 = Blueprint set not found for: Cameras\EditCamera001.xml
[RunTimeError 10:43:13 PM] Duplicate Scenario GUID in SerializeDatabase
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] ASSERT(mScenarioMap.find( scenario->getScenarioID() ) == mScenarioMap.end());
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] cScenarioDatabase::SerializeDatabase()
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] cScenarioDatabase.cpp : 1236
[RunTimeError 10:43:13 PM] Duplicate Scenario GUID in SerializeDatabase
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] ASSERT(mScenarioMap.find( scenario->getScenarioID() ) == mScenarioMap.end());
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] cScenarioDatabase::SerializeDatabase()
[RunTimeError 10:43:13 PM]
[RunTimeError 10:43:13 PM] cScenarioDatabase.cpp : 1236
[RunTimeError 10:45:27 PM] Trace mdump.cpp : 381 = Dump taken

there is a file in the learning center under trouble shooting railworks about removing duplicate scenarios from chacal run it it will show you your duplicates and then you can take the appropriate action

[frankenthal]

After going to the Command window and running: del /S PONtrack.bin I still get this.

[RunTimeError 6:32:38 PM] Trace mdump.cpp : 422 = error handlers have been set
[Content 6:32:39 PM] Trace cBlueprintLibrary.cpp : 417 = Blueprint set not found : Kuju, RailSimulatorCore
[Content 6:32:39 PM] Trace cBlueprintLibrary.cpp : 448 = Blueprint set not found for: Cameras\EditCamera001.xml
[RunTimeError 6:37:34 PM] Trace mdump.cpp : 381 = Dump taken

Still getting the v53.9b.dmp

[Chacal]

The log gives no clue about the crash.
The two trace messages are always there, and anyway the crash happens 5 minutes later.