Missions (Scenarios) for P3DD

Introduction | Why | Missions | Tutorial | FIP

Introduction | FlightCreate | MissionCreate | MissionExpand | MissionComplete ||||| MissionExpand 1 | 2 | 3 | 4 | 5 | 6
Example flight expand (Part2)

So far, it is monitored whether RPM is above 2400, if so, the timer for the oil leak starts. In addition, it must be monitored whether the RPM is reduced after the start.

Open the group "TimerFailure" in the visualization and click on the trigger ">2400RPM". With the right mouse button select "Duplicates" in the menu.

Name the new trigger "<2400RPM" and click on EDIT LOGIC.
Right click on "Greater Than" and select "Less Than Or Equal" (red rectangle) in the menu under "Change Type".
All other settings in the trigger remain unchanged.

Now select the ObjectActivationAction named ">2400RPM on" in the visualization window and bring the trigger named "<2400RPM" into the field Referenced under ObjectReferenceList.

The trigger should stop the timer for the oil leak, so another ObjectActivationAction is needed. Find the action named "Timer OilLeak on", and duplicate it. Name the duplicate "Timer OilLeak off" and change the NewObjectState to DEACTIVATE.

Select the trigger "<2400RPM" and bring the ObjectActivationAction named "Timer OilLeak off" into the field Referenced under Actions.

Then select the ObjectActivationAction "Timer OilLeak off" in the Visualization window and bring the Time Trigger named "4,5min. to OilLeack" into the Referenced field under ObjectReferenceList in the right window.

What happens now when you test the flight?

As soon as you taxi off and into the "StartTimerFailure" area, it monitors if the propeller speed is above 2400 (better said above 2450) RPM. If so, the oil leak timer will start. Because you reduce the propeller RPM to 2400 RPM after takeoff, the "<2400RPM" trigger turns off the timer. The timer stops and continues to run when the RPM is increased above 2450. This repeats each time the RPM is reduced and increased until the timer runs out.

The plan is for the timer to stop and reset as soon as the propeller RPM is reduced. Finally, the Maule may well fly at full RPM for some time, once the RPM is reduced, the engine "recovers" and can later be operated at maximum RPM again for the full 4.5 minutes for the landing approach.

Therefore a "ResetTimerAction" is needed, which can be found in the Catalog under the category Actions.

Drag the action as usual into the visualization window and name it "ResetTimer OilLeak". Select the "4.5min. to OilLeack" trigger under Triggers and put it into the Referenced field.

The ObjectActivationAction named "Timer OilLeak off" could now trigger the "ResetTimer OilLeak" under OnCompleteAction, but it is unrealistic that the motor "recovers" immediately. I assume the engine needs 2 minutes recovery time.

That's why another TimerTrigger, a ResetTimerAction and an ObjectActivationActions are needed.

Conveniently, the three objects are already present and properly linked. So draw a frame around the objects shown in the image in the visualization window and select "Duplicate (3)" from the menu with the right mouse button.

Rename the objects appropriately:
- (ResetTimer OilLeak - Copy 1) "ResetTimer Recreation"
- (Timer OilLeak on - Copy 1) "Timer Recreation on"
- (4,5min. to OilLeak - Copy 1) "2min. to Recreation".

1) Then select the TimeTrigger with name "2min. to Recreation" and set in the right window under StartTime 120 (2x60 seconds).
2) At OnScreenTimer you have to switch to "NO". (Only one timer can be set to "visible" at the same time and currently this is the timer "4,5min. to OilLeack").
3) For OneShot switch to "NO". (The engine can recover several times).

When you save now, you will see 4 errors under Validation Output, because there are still some links to be made.

- First select the ObjectActivationAction named "Timer OilLeak off" and under OnCompleteAction bring the action named "Timer Recreation on" into the Referenced field.
(This will start the "recovery time" of the engine).

- Now select the ObjectActivationAction named "Timer OilLeak on" and under OnCompleteAction bring the ResetTimerAction named "ResetTimer Recreation" into the Referenced field.
(This will set the engine recovery time back to 2 minutes once the propeller speed is above 2450 RPM).

- Now select the TimeTrigger named "2min. to Recreation" and under Actions bring the ResetTimerAction named "ResetTimer OilLeak" into the Referenced field.
(This will cause the oil leak timer to be reset after the 2 minutes have elapsed).

Save the mission, no errors are listed in Validation Output.
Test the flight in SimDirector (Mode, Preview Scenario).

1st Test:
- For the test you don't have to fly off, it's enough to roll forward a few meters to get to the area that starts the RPM monitoring.
- Stop and apply the parking brake. Now give full thrust, the timer for the oil leak will appear and run down.
- Reduce the propeller RPM, the timer stops, increase the propeller RPM and the timer continues to run.
- If you reduce the propeller speed for 2 minutes, the timer resets to 4:30.
- You can increase the simulation rate to 4x, then at full propeller speed in one minute the oil leak will be triggered. (More than 4x simulation rate is not possible on the ground, or even at 16x the simulation will only run at 4x speed).

2nd test:
- Go back to the SimEditor (Mode, Sim Editor) and deactivate the OnScreenTimer at the timer "4.5min. to oil leak" and activate it at the timer "2min. to engine recovery".
- Test the flight again (Mode, Preview Scenario).
- Roll forward again a few meters, stop, apply the parking brake and give full thrust.
- As soon as you reduce the propeller speed, the timer will fade in and run down.

If both tests were successful, deactivate the OnScreenTimer and save the flight again.

If you don't want to rebuild this part of the tutorial yourself, you can download this zip and copy the files it contains into your save directory to see the result.
(Both timers are hidden).

ExampleFlightExpand2.zip

Continue with part3: Example flight expand (Part3)
I hope you enjoy these flights, if so, please give feedback to p3d@andi20.ch.
Also send error messages (spelling mistakes, wrong information, etc.) to me, I appreciate any feedback.
Introduction | FlightCreate | MissionCreate | MissionExpand | MissionComplete ||||| MissionExpand 1 | 2 | 3 | 4 | 5 | 6

Introduction | Why | Missions | Tutorial | FIP