Missionen

Missions (Scenarios) for P3D

Statistics | Notes | ManufacturingNewYorkBridges

To give you an idea of the effort involved in a mission, here are my notes on the CilipiTransport, which I made during its creation and test flights.

Explanation of my scribbles:
- A minus sign “-” means I need to check/improve this point.
- A plus sign “+” means that this point has been completed (after a successful test flight).
- Underlined text means that the word has a spelling error and the value must be changed.
- A “crossed-out” line means that this idea has been rejected, is unnecessary, or has been resolved because another solution has been found.
- Text passages framed in bold or bold minus signs (-) mean that something still did not work during testing or is important and must be checked during the next test.
- To balance out a bold “-”, I naturally turned it into a bold “+”.

Mind you, before I made my first notes, the flight was already quite far along. More specifically, the takeoff in Caselle, the flight route, and the POI to Cilipi were ready. So were the dive over Cilipi, including rocket attacks, and the landing on the correct runway.

During the first test flight, I flew to Cilipi at 16x flight acceleration to test the dive spiral, because that is the special feature of this mission. It was only then that I began my first error notes.

After the first attack, offer an alternative: shut down engines at 5000 ft, then start them all up again for landing. (In this case, suspend attacks unless engines are restarted.)
I later discarded this idea, which is why I crossed it out.

Speed and altitude monitoring was only added during the next test flight. The idea of having to make an emergency landing en route due to engine problems and evacuating tourists was also added later.

Sure, I could have published the mission as complete on page 6, because the “normal user” usually doesn't notice the latest improvements.
However, during testing, I repeatedly noticed things that I absolutely wanted to fix.
I also tried to intercept as many tricks or errors as possible that users could exploit.

For example, climbing (away from Cilipi): If the climb rate of 2000 ft/min cannot be maintained due to engine problems, a text message is displayed (depending on speed) to reduce the climb rate to 1500 and later even to 1000 ft/min.

What happens if a user reduces the climb rate to 500 ft/min or even switches to horizontal flight?
None of the following events will be triggered because the flight altitude of 20,000 feet will not be reached.

So I had to install a climb rate monitor that alerts the user when climbing at less than 1000 ft/min.

You can read the 10 pages of notes here: (Sorry, my notes are only available in German.)
Click on the images for a larger view.

Seite1	Seite2	Seite3	Seite4	Seite5
Seite6	Seite7	Seite8	Seite9	Seite10

Statistics | Notes | ManufacturingNewYorkBridges