Railworks America

Now that we're getting engines with complex and supposedly realistic start-up and shut-down procedures, I'm wondering how to build them in to scenarios. The start-up sequence is just a matter of allowing "enough" time for all of the various steps, although with each potential driver taking a different amount of time to go through them AI timing will be even more difficult. How about allowing for shut-down sequence at the end of the scenario, fully or partially? In order to run successfully, a standard scenario must have an end marker and when that marker is reached, the scenario ends and vanishes, without allowing for any shut-down procedures. Ideas, fellow scenario writers?

just add a message trigger at the end and change the time after the last action for 30 seconds or however much time you need it to hold the scenario open for

In the case of the GP40 the shutdown is done by switching mandatory breaker off, or by pressing the shutdown button, but under the hood we are hooking into the standard RW control 'Startup'. The GP20 and SD45 do the same thing (though the buttons maybe different). If you script your LUA to wait for the engine to have its Startup value set at -1 (1 is started) then you should be able to do what you want.

The scenario lua script?

Yes. You can script scenarios. You can start, stop, and do any number of things against an engine. I am sure you can do even more than that.

Yeah the cinemtaic deal stops you from doing anything with the controls while you are flying around. It has a command for that and a command for giving control back to you. If we only had a list of all the things it could do.

Another way to do it is to put a call like this in your engine script, a certain time after the shutdown:

SysCall(“ScenarioManager:TriggerScenarioComplete”, "Engine shutdown complete")

You can also end a scenario when there's an engine failure:

SysCall(“ScenarioManager:TriggerScenarioFailure”, "You blew up the engine")

Try this:
https://docs.google.com/document/d/19gn ... edit?pli=1

PapaXpress wrote:Try this:
https://docs.google.com/document/d/19gn ... edit?pli=1

Yep, that's the one I've got

robbit wrote:just add a message trigger at the end and change the time after the last action for 30 seconds or however much time you need it to hold the scenario open for

That sounds like what I'm after . . . thanks!

As to the scripting suggestions, well, I just don't LUA. Maybe someday, but not yet.

Honestly from what I have seen from our scenarios for the GP40 its not as complex as one you would write for a model.

You're welcome!

mrennie wrote:

PapaXpress wrote:Try this:
https://docs.google.com/document/d/19gn ... edit?pli=1

Yep, that's the one I've got

NICE! That's a helpful link.