ppsspp/UI/TiltEventProcessor.cpp

#define _USE_MATH_DEFINES
#include <cmath>
#include "TiltEventProcessor.h"
#include "Core/HLE/sceCtrl.h"
#include "math.h"
#include "native/base/logging.h"


using namespace TiltEventProcessor;

//deadzone is normalized - 0 to 1
//sensitivity controls how fast the deadzone reaches max value
inline float tiltInputCurve (float x, float deadzone, float sensitivity) {

	const float factor = sensitivity * 1.0f / (1.0f - deadzone);

	if (x > deadzone) {
		return (x - deadzone) * factor * factor;
	} else if (x < -deadzone) {
		return (x + deadzone) * factor * factor;
	} else {
		return 0.0f;
	}
}

//dampen the tilt according to the given deadzone amount.
inline Tilt dampTilt(const Tilt &tilt, float deadzone, float xSensitivity, float ySensitivity) {
	//multiply sensitivity by 2 so that "overshoot" is possible. I personally prefer a
	//sensitivity >1 for kingdom hearts and < 1 for Gods Eater. so yes, overshoot is nice
	//to have. 
	return Tilt(tiltInputCurve(tilt.x_, deadzone, 2.0 * xSensitivity), tiltInputCurve(tilt.y_, deadzone, 2.0 * ySensitivity));
}

inline float clamp(float f) {
	if (f > 1.0f) return 1.0f;
	if (f < -1.0f) return -1.0f;
	return f;
} 


Tilt TiltEventProcessor::NormalizeTilt(const Tilt &tilt){
	// Normalise the accelerometer manually per-platform, to 'g'
	#if defined(ANDROID) || defined(BLACKBERRY) || defined(__SYMBIAN32__)
		// Values are in metres per second. Divide by 9.8 to get 'g' value
		float maxX = 9.8f, maxY = 9.8f;
	#else
		float maxX = 1.0, maxY = 1.0;
	#endif

	return Tilt(tilt.x_ / maxX, tilt.y_ / maxY);

};


Tilt TiltEventProcessor::GenTilt(const Tilt &baseTilt, const Tilt &currentTilt, bool invertX, bool invertY, float deadzone, float xSensitivity, float ySensitivity) {
	//first convert to the correct coordinate system
	Tilt transformedTilt(currentTilt.x_ - baseTilt.x_, currentTilt.y_ - baseTilt.y_);

	//invert x and y axes if needed
	if (invertX) {
		transformedTilt.x_ *= -1.0;
	}

	if (invertY) {
		transformedTilt.y_ *= -1.0;
	}

	//next, normalize the tilt values
	transformedTilt = NormalizeTilt(transformedTilt);
	
	//finally, dampen the tilt according to our curve.
	return dampTilt(transformedTilt, deadzone, xSensitivity, ySensitivity);
};

void TiltEventProcessor::GenerateAnalogStickEvent(const Tilt &tilt) {
	__CtrlSetAnalogX(clamp(tilt.x_), CTRL_STICK_LEFT);
	__CtrlSetAnalogY(clamp(tilt.y_), CTRL_STICK_LEFT);
};


void TiltEventProcessor::GenerateDPadEvent(const Tilt &tilt) {
	static const int dir[4] = {CTRL_RIGHT, CTRL_DOWN, CTRL_LEFT, CTRL_UP};

	if (tilt.x_ == 0) {
		__CtrlButtonUp(CTRL_RIGHT);
		__CtrlButtonUp(CTRL_LEFT);

	}

	if (tilt.y_ == 0) {
		__CtrlButtonUp(CTRL_UP);
		__CtrlButtonUp(CTRL_DOWN);

	}

	if (tilt.x_ == 0 && tilt.y_ == 0) {
		return;
	}

	int ctrlMask = 0;
	int direction = (int)(floorf((atan2f(tilt.y_, tilt.x_) / (2 * M_PI) * 8) + 0.5f)) & 7;
	switch (direction) {
	case 0: ctrlMask |= CTRL_RIGHT; break;
	case 1: ctrlMask |= CTRL_RIGHT | CTRL_DOWN; break;
	case 2: ctrlMask |= CTRL_DOWN; break;
	case 3: ctrlMask |= CTRL_DOWN | CTRL_LEFT; break;
	case 4: ctrlMask |= CTRL_LEFT; break;
	case 5: ctrlMask |= CTRL_UP | CTRL_LEFT; break;
	case 6: ctrlMask |= CTRL_UP; break;
	case 7: ctrlMask |= CTRL_UP | CTRL_RIGHT; break;
	}

	for (int i = 0; i < 4; i++) {
		if (ctrlMask & dir[i]) { 
			__CtrlButtonDown(dir[i]);
		}
	}
};


void TiltEventProcessor::GenerateActionButtonEvent(const Tilt &tilt) {
	static const int buttons[4] = {CTRL_CIRCLE, CTRL_CROSS, CTRL_SQUARE, CTRL_TRIANGLE};

	if (tilt.x_ == 0) {
		__CtrlButtonUp(CTRL_SQUARE);
		__CtrlButtonUp(CTRL_CIRCLE);	
	}

	if (tilt.y_ == 0) {
		__CtrlButtonUp(CTRL_TRIANGLE);
		__CtrlButtonUp(CTRL_CROSS);	
	}

	if (tilt.x_ == 0 && tilt.y_ == 0) {
		return;
	}

	int direction = (int)(floorf((atan2f(tilt.y_, tilt.x_) / (2 * M_PI) * 4) + 0.5f)) & 3;
	__CtrlButtonDown(buttons[direction]);
}; 

void TiltEventProcessor::ResetTiltEvents() {
	//this is ugly, but it's needed since the entire tilt system is
	//stateless. So, when a tilt option is changed, we have to reset 
	//the tilt. 
	//this scenario will take place without this:
	//1) tilt is Analog based. the device is tilted. Analog controller is being moved
	//2) user changes mode to D-Pad and goes back to game
	//3) the event handling loop sends all events to D-Pad now. 
	//	The analog controller doesn't know that the type of tilt input has changed.
	//	It keeps sending tilt events for the analog.

	//D-Pad
	__CtrlButtonUp(CTRL_RIGHT);
	__CtrlButtonUp(CTRL_LEFT);
	__CtrlButtonUp(CTRL_UP);
	__CtrlButtonUp(CTRL_DOWN);

	//action buttons
	__CtrlButtonUp(CTRL_SQUARE);
	__CtrlButtonUp(CTRL_CIRCLE);
	__CtrlButtonUp(CTRL_TRIANGLE);
	__CtrlButtonUp(CTRL_CROSS);		

	//analog
	__CtrlSetAnalogX(0.0f, CTRL_STICK_LEFT);
	__CtrlSetAnalogY(0.0f, CTRL_STICK_LEFT);
};