wacampbell wrote:...In a scenario you could easily simulate this interaction with some dialog boxes etc. Maybe even script and randomize the response so you have to drop the car at a different location each time you run the scenario.
That is a great idea, Wayne! I can imagine the following setup might work for this so that there's also corresponding data on the F1 task list:
1) let's assume the siding has three markers or stopping points (one for each spot / loading bay)
2) the scenario gets three "drop off" instructions, one for each of the three markers
3) each of the drop-off instruction includes the same rail vehicle number(s) and all are set to hidden
4) the script rolls a random number and makes one of the three hidden instructions visible via
SysCall( "ScenarioManager:UnhideDriverInstruction", [# of instruction] )This won't lead to a "successful" outcome of the scenario (no green check mark at the end) because there would still be two incomplete instructions (the two remaining hidden ones). So it definitely won't work with a Career type scenario, but in a standard type scenario it ought to be fine -- if the player is willing to overlook the "unsuccessful" outcome.