Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash Detection #12

Open
nabeelio opened this issue Aug 20, 2021 · 1 comment
Open

Crash Detection #12

nabeelio opened this issue Aug 20, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@nabeelio
Copy link
Member

nabeelio commented Aug 20, 2021

How to do crash detection...

  • New "Crashed" state in phpVMS
  • Send log, don't auto-delete/reject, just so admin has visibility

Sim Vars

FSUIPC

...

X-Plane

...

MSFS

...

@nabeelio nabeelio added the enhancement New feature or request label Aug 20, 2021
@FatihKoz
Copy link

Personal thoughts

  • Option 1;

Cancel the flight when a crash is detected, no need to send a "crashed" status or report back to phpvms. It is crashed and it is not a completed flight anyway.

Send a notification (either via discord or mail) , preferably at admin level (not public) about the crash. So if admins want to see how much/often their pilots crash they will have something in hand.

  • Option 2;

Send the pirep automatically with "Crashed" status/state and reject at phpvms level, do not let the pilot to interfere with it anymore after the crash detection.

Send a notification (either via discord or mail) , preferably at admin level (not public) about the crash.

So with this admins will have the ability to see where the crash happened (from pirep map) and check the details.

Also do not move the pilot/aircraft to the closes location, let them both stay at the departure. Giving a second chance to the pilot to fly again the same route.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants