Can anyone out there load, run, or edit third party routes?

[_o_OOOO_oo-Kanawha]

What does -lua-debug-messages do?

Is that switch necessary for troubleshooting routes not loading? The fewer messages the better, so only the relevant errors surface?

[mrennie]

What does -lua-debug-messages do?

Is that switch necessary for troubleshooting routes not loading? The fewer messages the better, so only the relevant errors surface?

I like to have as much information as possible. You can filter by type of message directly in the LogMate window itself while it's running.

[_o_OOOO_oo-Kanawha]

Understood.

For debugging route loading errors I suggest running LogMate while pressing the "Edit Route" button.
So as not to get confused with rolling stock and/or scenario errors just yet.

If the route succesfully opens in the World Editor, close it without saving changes, and then proceed to a simple standard free roam scenario.

If that scenario loads OK, proceed to the next one, until you find the culprit.

I had to delete some leftover malformed .xml, .bin and .GeoPcDx files, plus a PONtracks.bin trackrule from Kuju/RailSimulator/RailNetworks to get my COARW, NSAND, P&LE working again.

[buzz456]

I get exactly the same error on all my third party routes:
[RunTimeError 8:18:51 AM] cBlueprintSet::loadFile Failed to load blueprint: RailNetwork\TrackRules\PONtrack.bin
[RunTimeError 8:18:51 AM]
[RunTimeError 8:18:51 AM] cBlueprintSet::loadFile()
[RunTimeError 8:18:51 AM]
[RunTimeError 8:18:51 AM] cBlueprintSet.cpp : 369

Can one of you help us dummies out here? And yes the PONtrack bin file is there is the Kuju RailNetwork\TrackRules folder.

[_o_OOOO_oo-Kanawha]

Buzz, that PONtracks.bin is an empty blueprint, i.e. it has no trackrule definitions apart from the correct section headers.
Perhaps with the stricter asset parsing because of Steam Workshop, these blueprints now cause errors.

All your routes are/were/ working OK I thought? nevertheless, try deleting that PONtrack.bin and see if it makes any difference.

One word still: patience! Loading a large route with thousands of different assets takes a whole lot longer with LogMate running. Let it run its course.

On opening COARW, P&LE with the world editor I got loads of "Blueprint set not found" errors. Does this relate to no .ap file present of said provider or no provider references in the route definition blueprint? Some older routes went through a long developing phase, and the creators sometimes got sloppy.
For comparison, I am opening Cajon Pass now to see the different LogMate reports, and it comes up clean!

[dick8299]

OK, I ran Logmate and got this run time error message:

[RunTimeError 9:47:42 AM] cBlueprintSet::loadFile Failed to load blueprint: RailNetwork\TrackRules\PONtrack.bin

My route does not reference this track rule at all. However I did look around my files and found I had a bad copy of PONtrack.bin in my Kuju>RailSimulator>RailNetwork>TrackRules folder. I replaced it with a good copy and still got the crash and error message.

Nothing that has been said up to now has worked, and nothing explains why my route opened OK the very first time I tried it after installing 2014, but was never able to open after that. I believe the program wrote something in my files the first time I opened it that will not allow it to open again.

[_o_OOOO_oo-Kanawha]

Buzz, use Explorer search by date with a date after you've upgraded to TS2014, the a second search the day later, one day later still, etc. and try to find a pattern in the route folder or any asset folder of which you are certain it is used in the route that now refuses to load. LogMate doesn't report the ProviderID unfortunately, so it still is a game of hit and miss unless you know your asset folders' content by heart.

I also have the impression TS2014 is updating references, caches, checksums or whatever to provide for asset base stability with respect to Steam Workshop.
All US DLC routes from RSC that I have (all RW3 and later, actually) load with very few LogMage errors in the editor.

Try removing the scenario folder from the offending route and try to edit the route. Because there is a default scenario present when saving after editing, and sometimes its rolling stock isn't in your install. Try then to create a new scenario.

Sorting out rolling stock and scenarios can better wait until you know for certain the route loads OK in the editor.

Ol'Pint, are you still with us?

[buzz456]

Buzz, that PONtracks.bin is an empty blueprint, i.e. it has no trackrule definitions apart from the correct section headers.
Perhaps with the sticter asset parsing because of Steam Workshop, these blueprints now cause errors.

All your routes are/were/ working OK I thought? nevertheless, try deleting that PONtrack.bin and see if it makes any difference.

One word still: patience! Loading a large route with thousands of different assets takes a whole lot longer with LogMate running. Let it run its course.

They were working just fine and then DISASTER!!

[buzz456]

It appears to all be because of that PON file. I did a search, it was in four places. I eliminated all of them and WHOLA everything works again!

[_o_OOOO_oo-Kanawha]

That's awful! Don't panic and start restorings backup, deleting at random.

Retrace your steps, do the obvious, clear .pak files and other junk, verify, etc. You know the works by now.
Have you been editing stuff in the meantime, look for malformed .xml, .bin and .GeoPcDx files.
We can be certain that RSC didn't find all possible causes of error, no matter how hard they've tried.
There are simply too many variables and differences between users'installs when freeware and self created assets are involved.

Edit: strike the above, PONtracks.bin once again proved to be the culprit. Buzz is buzzing happily again?

[buzz456]

This is all well and good but I must say that I would have spent the next ten years and never got this to run again if it wasn't for you guys talking about logmate (which I didn't know existed) and your suggestions. For that I thank you ten times over.
To RSC for the way this is being handled.

Let's face it they don't give a rats petewy about anything to do with the third party stuff. If I had one route that wouldn't load I could understand but this literally every third party plus Castle Rock wouldn't load.

[buzz456]

[Scheduler 9:38:54 AM] Trace cTelemetryManager.cpp : 1314 = cTelemetryManager::cSendThread::sendPacket
[Scenario Manager 9:38:54 AM] Trace cCareerModel.cpp : 283 = cCareerModel::GetIntStat ( experience )

What the he^# does that mean? Frozen there.

[_o_OOOO_oo-Kanawha]

It seems that the LogMate is our best bet/only option in resolving problems.

That looks like AI communications that happen inside a standard scenario, or communications with the Steam host service in career scenarios.

Running LogMate slows things down considerably, wait for the loading process to finish.

[dick8299]

Deleted all PONtrack.bin files and now most all works. Still getting weird missing content errors in one of my own routes, but will continue to work on it.

I don't understand why RailSimulator support (who tried very hard to help me) did not tell me about logmate.

[_o_OOOO_oo-Kanawha]

Deleted all PONtrack.bin files and now most all works. Still getting weird missing content errors in one of my own routes, but will continue to work on it.

I don't understand why RailSimulator support (who tried very hard to help me) did not tell me about logmate.

LogMate reports are not that clear, the ProviderID is missing and you have to guess often as to what the report actually implies.

Missing assets? As in milk bottles lying around in your -running- route? Reported by LogMate or RW_Tools?

RW_Tools doesn't yet look in those new .ap archives into which most TS2014 default Kuju and RSC content has been moved.
I don't know where LogMate looks for its verification until documentation is provided or some other more savvy user finds out.