Problem with loading the new activity "CN Q18961" for CN Blackfoot V3

[uli2]

Hi,

the recently released activity "CN Q18961" for the CN Blackfoot V3 route does not load on my system. Before the loading is completed I get an error message about a "keynotfoundexception" and the loading process does not proceed any further. I have attached the OpenRailsLog.txt but I can't make sense of it. The other two activities released in the same pack (File ID 90941) load without a problem on my computer. I also tried different OR versions but they all refuse to load the activity.

I would appreciate any help.

Uli

OpenRailsLog.txt

[OmenRotcod]

Same here,
David

[kapitaen]

Hallo Uli,
scheint ein Problem mit den Passing Paths zu geben. There seems to be a problem with the passing paths.

Warning: Multiple passing paths at the same location, without common branch out, or return switch. Check the passing paths for Train name: [CN Q18961] CN G86851 (Edmonton - North Battleford Grain Empties) (number: 64), and other train's paths, which have passing paths at the same locations

Entferne mal den Haken bei Ortsgebundene Ausweichfahrstraßen verwenden, möglich, dass der Fehler dann unterdrückt wird. Set UseLocationPassingPaths = False

Jan

[crimsonfloyd]

I had the same problem, it`s the eastbound grain train that causes the issue. In the path editor remove the reverse points in the siding and replace it with a waiting point.

Mark

[uli2]

Entferne mal den Haken bei Ortsgebundene Ausweichfahrstraßen verwenden, möglich, dass der Fehler dann unterdrückt wird. Set UseLocationPassingPaths = False

Jan

Did that and now the activity loads. Will try running it with that setting. Danke, Jan!

Uli

[OmenRotcod]

Same here - Thanks for the tips.
David

[Timbit]

Hi,
For some of us who don't understand how to fix this, can someone please explain how to fix this activity?
Thanks in Advance
Tim

[OmenRotcod]

As I understand it, there are two ways. 1) under Options on the OR startup, click on the simulation Tab, then uncheck the box that says "Location-linked passing path processing". 2) this 2nd solution requires re-doing the AI path using TrackViewer.

The first is more straightforward, so try that first. It will get the Activity running.

Hope that helps,
David

[Timbit]

Thanks David will give it a try.
Tim

[derekmorton]

>"Location-linked passing path processing"

There is a bug is this module when a "Y" is around a passing loop, the Y presents a path that does not come directly back.
The person who coded the module has not come back.

[cntrainguy12]

Hi all! Apologies for chiming in a bit late on this one. Putting these together presented a bit of a challenge since unlike most others, this route is completely unsignalled. Pathing for meets was unconventional and was accomplished with the method outlined in the guide included with the route in the docs folder, hence the double reverse points. Thanks to OmenRotcod for pointing out the "Location-linked passing path processing" setting. After checking out the settings on my install of OR, that box was unticked for me which should explain the difference that other users have had when trying to run the activity.

[geepster775]

It is best to remind everyone that there have been two (2) different versions of Blackfoot 3, so results may vary depending upon version you may have. I cringe to believe this may be why there have been no major efforts to create third-party activities for the route in the last 10 years - the fear of TDB sanctity being second to the top notch scenery efforts. Even today with 1.5.1 or 1.6.1, many on the mile markers that ARE placed simply show only intermittently on the track monitor.

https://trainsim.com/forums/forum/open-rails/open-rails-discussion/154387-cn-blackfoot-vegreville-subs-v2-can99v2?p=2113177#post2113177

[geepster775]

Took the AI's path, changed metadata to make it player driveable, and then ran a train using it while on 100% autopilot to see how AI traffic would behave. Path had both a wait point and double reverse arrows defined within it and both features never appeared in track monitor. That was after snaking through that 10mph switch at close to 50. What a scenic route designed for explore mode it seems. Noticed at the end a bit of wheel slip under autopilot... This route really could use some TDB analysis and perhaps a hidden signal system with signal heads buried underground and out of sight like they did it on parts of the Monon route.