New packages released

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.

9 Replies to “New packages released”

  1. While not directly related to the GUI, I do have a feature request in the configuration, a Diagonal filter or dampener.

    What I'm observing is good x and y axis sensitivity separately, but when moving the crosshair diagonally in Modern Warfare 2, the sensitivity is much higher, so the crosshair rockets towards the corners.

    I'm not quite sure why it does this, but it's the only thing holding me back from a PC-like experience.

  2. I am aware of this problem.

    I think it's possible to see it with the lctrl+p key combination that generates a circular mouse move: the movement is slower each time x=0 or y=0 (i.e. for 0°, 90°, 180°, 270°).

    I have to see how different games behave so as to find a proper solution.

  3. That's exactly what I'm experiencing.

    I have an idea as to what may be causing (or partially causing) the accelerated diagonal movement. If the game treats dead zone as a circle instead of a rectangle, diagonal movement will appear more sensitive because emuclient is compensating more deadzone than truly needed.

    For example, let's say a game uses a circular dead zone with radius of 1. If you move the mouse 1 unit to the right (x axis), emuclient as it is now tells the PS3 to move right 1+1= 2 units. If you move the mouse 1 unit up (y axis), emuclient tells the PS3 to move up 1+1=2 units. If you move the mouse diagonally up-right 1 unit, emuclient tells the PS3 to move 2 units right and 2 units up (2,2). It should actually move right and up 1 + 1/2*sqrt(2) = 1.71 units (1.71,1.71).

    In other words, DZ should be a function of the angle of the mouse movement:
    ToPS3_X = x + dz*cos(tan-1(y/x))
    ToPS3_Y = y + dz*sin(tan-1(y/x)),

    where x and y are the x and y results of the existing power function Multiplier*(mouse movement)^Exponent

    Note: This assumes that the x and y dead zone values in the configuration are the same. If we treat the dead zone as an ellipse, the equation gets more complicated.

    In terms of programming, offer a choice between dead zone shapes in the configuration. If circle is chosen, either use the larger of the two dead zone values as the circle's dead zone radius or calculate the radius of an ellipse.

    Does this make sense?

  4. Well, I ordered what I thought were CSR plus EDR bluecore4 – ROM Bluetooth dongles, but what I received was old bluecore01a models. I bought them off of and they basically falsely labeled them as CSR + EDR Bluetooth dongles. I sent them an e-mail and ripped into them for mislabeling their product. I'll see if they give me a refund. They were only six dollars but still…

    I'm so tempted to buy a dongle that is being sold at my local Best Buy that has a Broadcomm– ROM chipset inside and test it out. Has anyone tested a dongle that has a Broadcomm – ROM chipset inside?

  5. It also happened to me… this seems to be a common practice 🙁

    Some broadcomm chipsets work, but their bdaddr cannot be changed permanently.

    If you don't find a working dongle, you can buy an at90usb dev board (a teensy for ex.) that can fake a sixaxis and pair any bdaddr with the ps3.


Leave a Reply

Your email address will not be published. Required fields are marked *