Skip to main content

Controller

src/controller/controller.hh — thin helpers on top of psyqo::AdvancedPad for analog stick handling.

static constexpr uint8_t ANALOG_STICK_DEADZONE = 16;
static constexpr uint8_t ANALOG_STICK_DEADZONE_X = 16;
static constexpr uint8_t ANALOG_STICK_DEADZONE_Y = 16;
static constexpr uint8_t ANALOG_STICK_MAX_INPUT = 127; // sticks range [-128, 127]

class ControllerHelper final {
public:
  enum AnalogStickIndex { RightStickX, RightStickY, LeftStickX, LeftStickY };

  void init(void);
  int GetNormalizedAnalogStickInput(psyqo::AdvancedPad::Pad pad, uint8_t index);
};

Non-static member of MadnightEngine (g_madnightEngine.m_controllerHelper).

GetNormalizedAnalogStickInput returns the raw stick value re-centered around zero (adc - 0x80, so roughly -128..127), with the Y axes sign-flipped so "up" on the stick reads positive. IsPadAnalog was removed as of v0.0.1 — GetNormalizedAnalogStickInput now checks pad connection and analog support internally (via psyqo's own AdvancedPad::hasAnalog) and safely returns 0 if the pad isn't connected or isn't analog, so there's no need to check first.

Usage​

Reading the right stick for camera control:

constexpr auto pad = psyqo::AdvancedPad::Pad::Pad1a;
int rx = g_madnightEngine.m_controllerHelper.GetNormalizedAnalogStickInput(pad, ControllerHelper::RightStickX);
int ry = g_madnightEngine.m_controllerHelper.GetNormalizedAnalogStickInput(pad, ControllerHelper::RightStickY);

if (ry != 0) camera.UpdateOrbitAngles(ry * ORBIT_SPEED, 0, deltaTime);
if (rx != 0) camera.UpdateOrbitAngles(0, rx * ORBIT_SPEED, deltaTime);

Internals​

  • GetNormalizedAnalogStickInput applies no deadzone. It returns the raw ADC reading re-centred on 0, so a resting stick gives you whatever it drifts to. ANALOG_STICK_DEADZONE, _X and _Y are provided as sane starting values for a game to apply itself, deliberately, so the threshold stays the game's decision rather than the engine's.
  • init() is a stub. It is where forcing the pad into analog mode would go, and nothing calls it yet, so pads report whatever mode they power up in.
  • Unlike ControllerHelper's explicit Pad parameter, the engine's AdvancedPad::Event-driven code (menu navigation, the debug menu, the pause-menu bind) never checks event.pad: on a multitap, any connected pad fires those handlers, not just the one you might expect.