"Chartered Freight" (Seebergbahn) - is this one broken?

[USRailFan]

Played the "Chartered Freight" scenario on the Seebergbahn route, picked up the freight cars per the work order, dropped them off at Seeberg as instructed, then picked up the second rake of cars and proceeded towards Almfeld, but just as the train enters Almfeld i get the popup that 'you did something wrong' and the scenario is listed as a failure, even though the work order was followed. Has anyone successfully completed this with the latest patch?

[martw]

No, I haven't been able to complete this one too. I completed all my orders and drove to Almsfeld, where I received the same message.

Martijn

[USRailFan]

OK, reported to RS.com

[firetrap1]

does the scenario editor say that there are duplicate rail numbers per chance?

chris

[USRailFan]

Haven't tried, but there are no duplicate numbers showing up in the coupler view. Alsom, if there were cars with duplicate numbers, shouldn't you still be able to actually stop in the correct track and do the drop-off as usual, and _then_ receive the 'sorry, you failed' pop-up? At least that's what was the case with the 'Cement Duty' scenario from the Class 66 pack before it was fixed

[USRailFan]

OK, the scenario editor does indeed report duplicate wagon numbers - in fact several instances of it even, although not within the same consist...

[firetrap1]

OK, the scenario editor does indeed report duplicate wagon numbers - in fact several instances of it even, although not within the same consist...

Bingo! even RSC misses things like this!

To make the scenario work you need to edit the scenario and locate the problem wagons. here you must delete the duplicate stock by first changing the wagon numbers to something else (double click to bring out the flyout window). Once you have changed the wagon numbers you can save the scenario then go back and delete the offending wagons from the scenario.

should be good to go after that. This is how I fixed "The Midland Scot " scenario for WCML North.


chris.

[USRailFan]

They really have to be deleted? You'd think it'd be enough just to renumber them?

(Also, given the large amount of wagon numbers to chose from in this case, one'd think it'd be possible to program the scenario editor to avoid assigning the same number twice?)

[FoggyMorning]

They really have to be deleted? You'd think it'd be enough just to renumber them?

(Also, given the large amount of wagon numbers to chose from in this case, one'd think it'd be possible to program the scenario editor to avoid assigning the same number twice?)

Renumbering should do the trick - make sure you renumber the ones that are not part of the player consist though. I don't know how it assigns numbers, sometimes it seems a bit bizarre; one scenario I've been trying to create keeps assigning the exact same numbers to every FGW HST I place

[USRailFan]

Renumbered the offending wagon in one of the AI consists. Saved, reloaded the scenario and checked that the renumber really had 'stuck'. Opens the editor again, and IT STILL REPORTS THAT THE BLASTED WAGON IS IN THE AI CONSIST WITH ITS ORIGINAL DUPLICATED NUMBER!!! What is wrong with this silly software????

[firetrap1]

Renumbered the offending wagon in one of the AI consists. Saved, reloaded the scenario and checked that the renumber really had 'stuck'. Opens the editor again, and IT STILL REPORTS THAT THE BLASTED WAGON IS IN THE AI CONSIST WITH ITS ORIGINAL DUPLICATED NUMBER!!! What is wrong with this silly software????

That's why you need to delete if as well.

[USRailFan]

That's where the logic fails me - why should it be necessary to _both_ renumber, _and_ delete/replace? One would think one of them would be enough?
(Please notice I am not drawing what firetrap1 says under doubt, I'm just trying to understand how things 'fit together')

[radu1972]

Hi, I have been able to finish this scenario by choosing a different track to pass through the station ( other than the one you are to finish on ) then backing up onto the one I was originally supposed to finish on. Although not a technically explicit description it worked as far as finishing the scenario with the green arrow.

[radu1972]

I meant with the green check mark ( and the "scenario complete" message )

[1S811985]

I've encountered this same issue with duplicate numers and can confirm that renumbering, saving then deleting is required. It's as if renumbering alone leaves a sort of "ghost in the machine" so to speak.

I'm beginning to think that some of the problems that can arise with signals and points during scenario creation may be the result of similar such hauntings.

For example. You route your driver train, test run the scenario and it works okay. You add an AI train and a conflict occurs that blocks your driver train. You re-time the AI to avoid the conflict and all seems well but when you run the scenario, although the re-timed AI is in the proper place at the proper time, the "ghost" of the original AI still conflicts.

I've taken to changing the start time (forward by one hour) and service type (anything but special) of any AI that I place before I give it any routing instructions. I then check the time I want the AI to be at a particular point and adjust the start time accordingly. I've also taken to cloning a WIP scenario at regular intervals, once satisfied that its working fine and before making any potentially conflicting additions/changes. If I encounter a problem then I go back to the clone and try again. It means a lot of cloning and deleting, and a lot of test running too, but I think it pays off.

It is of course allways possible that the better results I have experienced since adopting these practices may be due to a growing familiarity with the scenario editor but you never know.

Regards,

1S81