Game Input MultipleXer

.

If it works with usbspoof, it should also work through the GUI, as the GUI does execute usbspoof...
Maybe you are running usbspoof from the GIMX/core source directory, and did not run 'sudo make install'?

Adding a specific protocol to have more control on the adapter is a good idea. This will allow the spoof to be automatically performed, without any specific user action.
In the end I think the spoof button will be removed, and there will be an error message in case no 360 controller is connected and the spoof was not already done.

FYI, I'm currently refactoring the firmware source code:
- the serial interrupt will be restored as some bytes are lost otherwise (it breaks the controller state)
- the LUFA stack will be upgraded and factorized between the 3 firmwares (the source tree will have one more level which will be called 'firmwares')

.

I made the 360 spoof work in Windows

It requires to replace the stock 360 controller driver with the libusbk driver (winusb and libusb-win32 do not work).
This can easily be done using Zadig.

I built beta versions of the software and firmwares:

• GIMX setup
• firmwares

Please test it!

.

peshkohacka wrote: - The adapter works fine, but when you have a genuine pad already connected to the console (360), the avr controller can't register and returns connector_init() failed.

Are you using the same controller that you use on the PC for the spoof?

peshkohacka wrote: - I couldn't find a mouse frequency option in gimx-serial. My mouse is a really modest 800 dpi / 125Hz and when forced 225Hz, you can't move around as the mouse gets stuck in the center (125Hz would be a perfect match).

I removed the controller frequency from the GUI
It's still available in the command line: In the above example, 8 is the refresh period, thus 1000/8=125 is the refresh frequency.

.