• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

When to fail the player?

L

LivestockTony

Messages
7
Country
us-alaska
Philisophically, when's the right time to fail a player in a mission?

Let's say the 'story' leads up to a single engine ILS in solid IMC. You can build vectors, give the player a gentle (copilot reminding) and then a strong advisory (atc gives new vector) as he gets off course... but if the player- particularly one familiar with the airport- goes GPS direct to the runway (thus getting away from all my carefully placed dialog triggers! but also getting under the real world min vectoring altitude), and executes a circling approach from the other direction under the overcast, though he may have cheated himself out of experiencing what you've built, he probably feels he's solved the problem he was presented with (get this airplane on the ground in this weather) and deserves his reward. Or what if he shoots the back course ignoring the vectors (not a real world approach)....

Since the missions are not games in and of themselves, how much leeway are we expected to give the players?
-T
 
This ist totally up to you. I would advise you though to tell the user why he failed - if he did.
Cheating is easy in FSX missions, expecially in bad weather scenarios: simply delete the weather file and you won't need any skills to finish the mission.
The mission engine can't control this, you'd need simconnect to ensure bad weather.

If I create missions I try to figure what the user thinks and how he will act. If he leaves the flight corridor you can give him a warning or 2 and if he doesn't return you can fail him. Or you can still give him success if he kept at save altitudes all the way down. It's up to what you expect of him. ;)

Most important to me as a mission pilot is that I'm not lost with the question if I'm doing the right thing. There are some missions out there that let you do whatever you want - and when you touch down after 60mins of flying they give you a "mission failed" but don't tell you why. Those missions are no fun for me. :mad:
So, in any case include some triggers that remind the user what he's eypected to do and you should be fine. :)
 
Hi Folks

Tony -
As Thorsten says,
use off-route triggers to trap the user.



Thorsten -
To avoid the weather file deletion scenario.

You can use simconnect, (via simvar.exe)
to force the weather state.

In some situations it might not work fully,
unless you set it for other airports in the region,
or add fake weather stations.



HTH
ATB
Paul
 
You must log in or register to reply here.
Back
Top