Home

##Troubleshooting After installing drivers and connecting with MogaSerial, you can verify that it's working by checking the joystick control panel in Windows. The easiest way to bring this up is to press Win-R and type joy.cpl. With vJoy, the controller is called "vJoy Device" and with SCP the controller is "Controller (XBOX 360 For Windows)". Click properties for the relevant entry and you should be able to see the controller inputs reflected onscreen.

If something is missing in vJoy, make sure you've configured it properly inside the vJoyConfig program. It should look something like this picture.

If you're using x360ce, be sure to triple-check the configuration settings within that program. It can be difficult to set up properly. If you can see all the inputs from your Moga within the x360ce.exe config program, MogaSerial is working, and the issue is somewhere else.

I'm afraid I can't provide game support. Most likely I won't own what you're playing.

####Input Lag This seems to manifest in several different ways, many of which I don't have control over.

If you enable debug output, there is a new message now. Input queue: # will show how many controller inputs have yet to be processed by MogaSerial. This number should never be above 0. Anything higher means that MogaSerial isn't getting enough CPU time to process each message from the controller as it comes in.

If the number is 0 and you're still experiencing lag, it likely is coming from somewhere else. Bluetooth radio drivers are notorious for being buggy, and it's possible that controller messages are being delayed before MogaSerial can get them. If other Bluetooth devices are being used at the same time, it's possible the radio can't keep up with all the data being transmitted back and forth. Or there could be radio interference causing problems with the signal. Narrowing down the exact cause can unfortunately be very difficult. It might be worth trying to use a generic Bluetooth driver rather than the official one.

####Bluetooth issues Winsock error 10108 means one of two things. Either no Bluetooth device was found, or MogaSerial couldn't talk to the Bluetooth driver installed on your computer.

Windows 7 might have some issue with Bluetooth 4.0 adapters and third-party drivers. MogaSerial uses the Windows Bluetooth API, which requires that a Microsoft-supported Bluetooth driver be installed. If you see "Microsoft Bluetooth Enumerator" in the system Device Manager, you should be okay. If not, try installing a Microsoft-generic driver for your adapter.

####How to understand the Debug output in MogaSerial If your Moga connects but something still isn't working, you can enable the debug toggle within MogaSerial to verify that your controller hardware is functioning properly. This displays the raw serial messages the controller sends to the PC in hexadecimal, and everything done on the controller will cause a change in these messages.
A typical message looks like this: 7a 0e 66 01 04 20 00 7f 00 00 00 ff 10 a4
It means the following:

• 7a - Message header. Always this.
• 0e - Message length. Always this or 0c. (14 or 12)
• 66 - Message type. Can be a few different things.
• 01 - Controller id. (1-4)
• 04 20 00 7f 00 00 00 ff - The data we care about.
• 10 a4 - Identifier and checksum. Used for validation.

The data we care about contains 8 bytes, or 8 two-digit hex codes. (6 in vJoy button-trigger mode) Buttons add together to give a value. For example, 08 + 02 = 0a, as a means ten in hex.

• Byte 1
  • 10 - Start
  • 20 - Select
  • 40 - L1 / Left shoulder
  • 80 - R1 / Right shoulder
  • 01 - Y button
  • 02 - B button
  • 04 - A button
  • 08 - X button
• Byte 2
  • 10 - L2 / Left trigger (digital)
  • 20 - R2 / Right trigger (digital)
  • 40 - L3 / Left thumbstick
  • 80 - R3 / Right thumbstick
  • 01 - D-Pad Up
  • 02 - D-Pad Down
  • 04 - D-Pad Left
  • 08 - D-Pad Right
• Byte 3
  • Left stick X axis
• Byte 4
  • Left stick Y axis
• Byte 5
  • Right stick X axis
• Byte 6
  • Right stick Y axis
• Byte 7
  • Left trigger axis (analog)
• Byte 8
  • Right trigger axis (analog)

So in the example message, button A is pressed, the left thumbstick is fully up, and the right trigger is fully pressed.
If a control on the Moga causes nothing to happen, the device is very likely damaged, unfortunately.
If any of these are different, then your Moga behaves differently from mine, and I'd be grateful if you let me know which Moga you have, what region you bought it, and what codes have changed.