Category: Package release

Warning: the configuration writer of the mouse calibration mode is not working (issue 82) 🙁

If you are upgrading from v0.15 or lower, read this post first: link.

New configuration example installed in the /etc/emuclient folder:

• CallOfDuty:BlackOpsG500i.xml (with stick intensity control)

Improvements:

• the calibration mode automatically saves the configuration
• stick intensity control for button-to-stick mapping
• macros are fixed
• emuclient is started automatically
• the last used config file is auto-selected
• a (big) memory leak is fixed

All corrected issues:

• issue 70
• issue 71
• issue 72
• issue 73
• issue 75
• issue 78

Download links:

• sixemu_0.21-1_i386.deb

New sixemuconf layout:

It’s now possible to have a better control over a stick with 4 keys or buttons (for ex WASD) and at least 1 modifier key or button (for ex a wheel, which is in fact 2 buttons).

The original idea was to enable to reach mid-positions. This was proposed by KillerBug (see issue 73).

The solution I coded enables to reach more positions of the 8 directions that can be generated with 4 buttons. Up to 127 positions for each direction = up to 1016 positions!

Example:

– dead zone = 31 (null-movement positions = black zone)
– shape = circle
– steps = 3 (number of positions for each direction)

The circle radiuses are 127, 95, 63.
Each red dot is a position we can reach with 4 direction buttons (ex WASD) + at least 1 modifier button (ex wheel).
With shape = rectangle, the red dots are aligned as squares.

Enjoy!!

WARNING: this release totally breaks the configuration compatibility.

EDIT 21 April: The macro fonctionnality is broken 🙁

New configuration examples are installed to the /etc/emuclient folder:

• CallOfDuty:BlackOps.xml (updated)
• CallOfDuty:BlackOpsG500+G5.xml (configuration for 2 controllers)

Following items in the edit menu of Sixemuconf will let you convert your old configuration quickly:

• Replace mouse: detect and replace mouse name&id in the current controller
• Replace keyboard: detect and replace keyboard name&id in the current controller

Due to the correction of issue 60, you also will have to change ALL your mouse multipliers depending on your mouse frequency:

• 125Hz : divide by 1.25
• 250Hz : divide by 2.5
• 500Hz : divide by 5

If you don’t know what frequency your mouse is running at, just try each value (or ask google for your mouse max frequency, and limit it to a maximum of 500Hz). High-end mice like the Logitech G5 or G500 are running at 500Hz (default frequency).

I know, this incompatibility sucks, but the new features in this version are worth the price. This probably won’t happen another time.

To prevent beginners to use this version until I’m sure its quality is good, I will not change the version in the tutorial, and the previous version will remain “featured” in the googlecode download page. About 500 people downloaded the previous version 🙂 I’m waiting everyone’s feedback! I’m just joking, but I really appreciate a few words and I accept both positive and negative feedbacks.

Main improvements:

• multiple mice & keyboard (new configuration examples in /etc/emuclient)
• synchronization improved
• mouse translation improved
• up to 8 configurations per controller
• new mouse calibration mode

All corrected issues:

• issue 54
• issue 56
• issue 57
• issue 59
• issue 60
• issue 62
• issue 63
• issue 64
• issue 65
• issue 67

Download links:

• sixemu_0.20-1_i386.deb
• sixemu_0.20-1_amd64.deb

New items in the edit menu of Sixemuconf:

The “Replace Mouse DPI” item lets you adjust your multipliers according to your old and new mouse dpi values (the higher the better). I recently bought a Logitech G500 (which is excellent by the way), and I run it at its max dpi (5700). My previous mouse is a Logitech G5 (max 2000 dpi). This means I had to multiply my multipliers by: 2000/5700.

New calibration mode, displayed in Sixstatus:

This calibration mode lets you calibrate each mouse independently. It reads values from the loaded configuration, but it still doesn’t save them (use Sixemuconf to apply changes to the configuration file). To change values, use rctrl+FX key combinations and use the mouse wheel.

Enjoy!!

Main improvements:

• multiple emu (but still single mouse & keyboard)
• configuration switch/switch back
• compatibility with QtSixA
• buttons to stick mapping improved

All corrected issues:

• issue 15
• issue 19
• issue 27
• issue 45
• issue 46
• issue 47
• issue 50
• issue 51
• issue 52

Download link: sixemu_0.15-1_i386.deb

Enjoy!!

Main improvements:

• Config file permission/ownership problems should be fixed.
• Software reset is improved (better compatibility with Broadcom dongles).
• It’s possible to choose a circle or rectangle dead zone shape.
• Sixemuconf allows to modify a mapping.
• Sixemugui doesn’t hang anymore if connection is not successful.

All corrected issues:

• issue 29
• issue 34
• issue 37
• issue 38
• issue 39
• issue 40
• issue 41
• issue 42
• issue 43
• issue 44

Download link: sixemu_0.14-1_i386.deb

Enjoy!!

I built a new all-in-one package 0.13 that includes everything needed to install, configure and launch the sixaxis emulator.

It features a new gui called “sixstatus” that is able to display the sixaxis status (issue 35), as shown in the following screenshot:

It’s now possible to save the configuration of sixemugui (Sixaxis and PS3 addresses) so that it is not required (except for the first launch) to have the sixaxis plugged anymore (issue 33).

Last but not least, the mouse calibration mode is improved (issue 36).

If you installed the 9.99 test package, uninstall it before installing this new package!

Package download: sixemu_0.13-1_i386.deb

I will update the tutorials latter.

New packages are available there: link.

It fixes issues 24, 25, 31, 19.

There is a new package (sixemugui_0.1-1_i386.deb) that contains the sixemugui tool.

Package installation now adds shortcuts for sixemuconf and sixemugui in the Application>Game menu.

Quick instructions:

1. Plug you sixaxis and bt dongle
2. Select the sixaxis
3. Select the bt dongle
4. Set the dongle address (don’t forget to write the old one down)
5. Re-select the sixaxis and the bt dongle
6. Start emu (a popup will tell you if connection is succesful)
7. Start emuclient
8. Enjoy!

As I won’t be available next week, I didn’t updated the tutorial.

So if you use them and find some issues, please report them, but don’t expect to have a quick answer or a quick fix.