MODE

Indicates which AirSig function are going to use when player triggered the controller input:

  • None:

    • Do nothing
  • TrainPlayerSignature:

    • Use the input data to set player signature (multiple input data are required to complete the training)
  • IdentifyPlayerSignature:

    • Use the input data to identify player signature.
  • DeveloperDefined:

    • Use the input data to identify against Developer-defined Gestures. The gestures are calculated by AirSig Developer Portal with developers collecting their own gesture samples. Using this API, developer will be able to provide infinite amount of gestures for improving experience of their products.
  • AddPlayerGesture:

    • Use the input data to collect Player-defined Gesture at runtime. Notice that data is only collected into a cache, until SetPlayerGesture(index) method is called which insert data into the engine.
  • IdentifyPlayerGesture:

    • use the input data to identify Player-defined Gesture that set into the engine. This function identifies whether a gesture is one of given targerts rather than telling is or is not a gesture.
    • For example, using this function to identify a gesture against one target - index 1, will almost always return match of index 1. If two targets - index 1 and 2 are set, will return match of either one.
  • SmartTrainDeveloperDefined:

    • Use the input data to identify against the Developer-defined Gesture and learn Player-defined Gesture at the same time. A excellent place to apply is like tutorial or practice session.
  • SmartIdentifyDeveloperDefined:

    • Use the input data to verify against both the Developer-defined Gesture and learnt Player-defined Gesture. The result is more accurate than just using one.