From [email protected] on February 17, 2011 15:17:45

The idea is to propose a "calibration mode for dummies".

One key combination triggers a rectangular dead zone test.
Another key combination triggers a circular dead zone test.

The test generates mouse motion (1,0) for 1s, (1,1) for 1s, and (0,1) for 1s.

If the dead zone is correctly configured (shape+size), the test should not generate any movement.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=36

From [email protected] on May 07, 2010 21:10:48

What steps will reproduce the problem? 1. Compile/Run Program
2. Tested with Battlefield: Bad Company 2
3. For example move the mouse slowly in one direction, stop moving the
mouse, then press X (jump). The X command will not execute until all
movement commands have been sent to the PS3. What version of the product are you using? On what operating system? Ubuntu 10.04 LTS
diyps3controller revision 53 Please provide any additional information below. Although I can see the logic in what is happening, it doesn't make FPS
games very playable if I have to wait around for my mouse commands to clear
the buffer. Keyboard commands as far as I can tell so far have been
working well, as they only send one command to the system.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=7

From [email protected] on January 27, 2011 16:10:24

Sixaxis buttons are only supported as digital buttons, i.e. button value is 0=released or 1=pressed.

But most buttons are pressure-sensitive, and have an 'analog' state too, i.e. a value in the 0..255 range.

'Analog' values are not correctly detected because Linux maps 0..255 to -32767..32767, so that the released state corresponds to an off-center position.

Specific code could be developed for sixaxis, so as to remap -32767..32767 to 0..255.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=27

From [email protected] on February 26, 2011 14:38:39

Dongle that require a software reset (for ex. most of broadcom dongles) are not fully reset giving "-r" as argument to the bdaddr tool.

The command "hciconfig hci0 reset" does more than "bdaddr -r": the device is reset (HCI command) but it is also set the device down and up.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=43

From [email protected] on February 26, 2011 22:14:06

It's not possible to edit a mapping.

The only way to change a mapping is to delete it and add a new one.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=44

From [email protected] on May 06, 2010 23:38:03

What steps will reproduce the problem? 1. Compile and run the program as described on the home page. What is the expected output? What do you see instead? I followed the instructions and got the following MAC adresses :
Sixaxis : 00:21:4F:E5:0E:9D
PS3 : 00:0b:e4:41:d4:85

When running 'emu', the PS3 started up fine but the program says
'Connection refused'.

Compiled with debug output : this is my command-line results :
jm@chaperon-desktop:~/diyps3controller-read-only$ sudo ../bdaddr -r
00:21:4F:E5:0E:9D
Manufacturer: Broadcom Corporation (15)
Device address: 00:19:86:00:0A:A5
New BD address: 00:21:4F:E5:0E:9D

Address changed - Device reset successully

jm@chaperon-desktop:~/diyps3controller-read-only$ sudo ./emu 00:0b:e4:41:d4:85
connecting to 00:0b:e4:41:d4:85 psm 17
[PS3 starts up]
emu: can't connect to 00:0b:e4:41:d4:85 psm 17: Connection refused What version of the product are you using? On what operating system? Code from SVN rev 52, Ubuntu lucid up to date.
libbluetooth-dev version 4.60.0ubuntu8

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=5

From [email protected] on November 30, 2010 14:18:11

Button mapping is the following:
q = left stick left
d = left stick right

press q, press d, release q (but maintain d pressed)

=> left stick is set to center position, it should be set to right.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=15

From [email protected] on February 01, 2011 14:57:34

The calibration mode was removed when the configuration file capabilities were coded.

The reason for this code removal was that the sixaxis emulator is now able to support multiple mice (but the libSDL is still not ready for that).

It's not easy to design a generic calibration mode that would work for multiple mice, so that the calibration mode will be back only for mouse id 0 in a first step.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=31

From [email protected] on March 04, 2011 22:24:47

Ability to Have the mouse analog go to a set number without acceleration, similar to the keyboard press of an analog button. This may help with uniform mouse control.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=48

From [email protected] on May 12, 2010 13:59:37

I tried to add scripting support to emucontroller and have almost
succeeded. Currently I have gotten emucontroller to properly read the
script and act upon it, the problem is adding a fake keystroke to the SDL
queue. This was my first time working with SDL so please pardon any
mistakes. The way I have it written now is to create an event, give it the
same attributes as a button press, then push it on the stack, but this is
not working.

Basically the way Its currently working (I documented fairly well) is if F2
is pressed try to load the macro file, and then parse it line by line and
character by character. If a # is found ignore the rest of the line, if U
is found push the keystroke for SDLK_UP onto the queue, if a number is
found sleep for a predetermined amount of time, and so on for most
controller buttons.

Any help or insight would be greatly appreciated, and if you want you may
incorporate any part of what I wrote into future versions.

Attachment: emuclient.c sixaxis-macro.txt

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=9

From [email protected] on February 17, 2011 00:51:44

The idea is to allow to choose a circular or rectangular dead zone.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=34

From [email protected] on January 19, 2011 11:43:20

Connect to the PS3 and wait 20-30 min.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=26

From [email protected] on February 17, 2011 11:51:00

The idea is to display the sixaxis state in a user-friendly way.

The idea is not to encapsulate emuclient in a GUI.
The GUI and emuclient will be different processes.
The GUI will only read and parse the emuclient output.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=35

From [email protected] on February 23, 2011 11:05:26

In the config files for emuclient, only the id is used to identify the joystick, which is a big issue because the id only depends on the connection order.

Consider we have two different joysticks (not the same model) 'A' and 'B', and a PC with no currently plugged joystick. If 'A' is plugged first and 'B' is plugged second, then 'A' will have 0 as id, and 'B' will have '1' as id. If 'B' is plugged first and 'A' is plugged second, then 'A' will have 1 as id, and 'B' will have '0' as id.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=38

From [email protected] on May 08, 2010 14:31:43

Dead zone has to be calibrated for each game.

Keypad '*' will increase the dead zone, and keypad '/' will decrease it.

To make it easier to find the right dead zone value, a key press (keypad
'.') will enable a calibration mode.

The calibration mode applies an horizontal move movement that corresponds
to the current dead zone value.

If the position is not stable, decrease the dead zone until the position is
stable.

If the position is stable, increase the dead zone until last position that
is stable.

Current value for dead zone will be displayed in the emuclient terminal.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=8

From [email protected] on February 03, 2011 00:09:28

What steps will reproduce the problem? Its not easibly recreateable. emu might run for hours before exiting, it also might exit after a few minutes.
It seems to be unrelated to emuclient. emu even exits after a while when emuclient was not even started.

The light on my bluetooth-adapter continues flashing after emu exited. What version of the product are you using? On what operating system? Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux

I tried the german manual thus the "older software" where you had to compile emu etc. on your own.
And today I tried the new english tutorial and the .deb packages. But there is no diference - emu exits with "error on ctrl psm" after a while.

Note that I cannot change the address of my bluetooth adapter permanently, only temporariliy.

ubuntu@ubuntu:~$ sudo hciconfig hci0 revision
hci0: Type: BR/EDR Bus: USB
BD Address: 04:76:6E:97:96:BE ACL MTU: 1021:8 SCO MTU: 64:1
Firmware 35.66 / 14

ubuntu@ubuntu:~$ hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 04:76:6E:97:96:BE ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:332011 acl:5685 sco:0 events:193 errors:0
TX bytes:9517 acl:139 sco:0 commands:78 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'ubuntu-0'
Class: 0x000508
Service Classes: Unspecified
Device Class: Peripheral, Gamepad
HCI Version: 2.1 (0x4) Revision: 0x5123
LMP Version: 2.1 (0x4) Subversion: 0x420e
Manufacturer: Broadcom Corporation (15)

I have a new slim 320gb PS3. My notebook is a compaq 6910p.
There are other people on the web with that problem.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=32

From [email protected] on December 22, 2010 17:56:31

The following line:

{"LEFTPAREN", SDLK_AMPERSAND },

has to be:

{"LEFTPAREN", SDLK_LEFTPAREN },

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=16

From [email protected] on February 28, 2011 09:41:38

For a joystick axis to stick axis mapping, default multiplier should be 0.004.

This maps -32768..+32767 (joystick axis are normalized in linux) to -128..+127.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=45

From [email protected] on February 24, 2011 14:54:11

If no ~/.emuclient exists, then /etc/emuclient has to be copied to ~/.emuclient.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=40

From [email protected] on January 14, 2011 08:46:57

This stuff enables to release the mouse from the "Sixaxis control" window of the emuclient process, so that other stuffs can be done on the pc without having to quit the emuclient.

The key combination will probably be the ALT+ALTGR.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=23

From [email protected] on July 24, 2010 20:00:32

Add support for windows for both emu and emuclient processes.

Tasks for emuclient:

• port bsd sockets (emuclient.c)
• port threads (macro.c)

Tasks for emu:

• port bsd sockets (emu.c)
• port bt l2cap sockets (emu.c)

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=12

From [email protected] on January 17, 2011 14:00:05

There already is a way to make the emuclient release the mouse pointer ( Issue 23 ), but an argument would be nice to tell the emuclient not to capture it from startup.

This may allow some third-party programs such as speech recognition ones to interact with the emuclient.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=25

From [email protected] on January 13, 2011 09:46:01

Most buttons are analog (0-255) and digital buttons (0/1).

The idea is to make possible to map a joystick axis (such as a gas pedal) to a "digital" button ( r2 button is the gas pedal in many racing games).

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=21

From [email protected] on January 27, 2011 16:16:38

The idea is to control motion sensing axis with axis or buttons.

Both the configuration GUI and the emuclient have to be modified.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=28

From [email protected] on May 07, 2010 17:52:09

Sometimes the mouse movements stop to be reported.

Mouse buttons work.

As a work around, press escape, wait half a second, press up and enter.

That will restart the emuclient.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=6

From [email protected] on March 30, 2010 09:31:23

Instead of hard-coding button and axis mapping, a mapping table could be
defined in a header file for each game.

It would make the process of changing the button mapping easier.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=1

From [email protected] on September 30, 2010 22:28:29

For ex:

"
MACRO F1
KEY s
DELAY 450

KEY d
"

is read as:

"
MACRO F1
KEY s
DELAY 450
DELAY 450
DELAY 450
KEY d
"

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=13

From [email protected] on January 13, 2011 13:32:12

The user name returned by cuserid function is truncated to 8 chars

A solution has to be found to handle user names with more than 8 chars.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=22

From [email protected] on May 06, 2010 19:09:51

I followed the installation instructions line for line with no errors.
All I did was modify the key mappings.

"emu: send_report: Cannot allocate memory" floods the emu term shortly
after emuclient is launched.

The result on the PS3 is about a 10 second lag from the time a key is
pressed, to the time the PS3 responds.

Computer is a IBM Thinkpad T42 2379-DXU
OS is a brand new install of Ubuntu 10.04 LTS
PS3 is an unmodified US Slim

Attached are the outputs of the client/server with static int debug
turned on. Gathered using the syntax 'emu 00:25:56:83:cb:b2

emutrace.txt 2>&1' & 'emuclient >>emuclienttrace.txt 2>&1'

Attachment: emutraces.tar.gz emucode.tar.gz

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=4

From [email protected] on January 12, 2011 09:43:37

The idea is to make a simple GUI (1 panel) that:

1- detects all sixaxis connected to the PC, and gets sixaxis & PS3 bdaddrs
2- detects all bt adapters available, and display/change their bdaddr according to the selected sixaxis
3- launches a emu process according to the selected sixaxis
4- launches a emuclient process

Multiple emu processes for a single PS3.
Multiple PS3s.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=19

From [email protected] on March 30, 2010 09:38:08

Reproduction steps to be determined.

Sometimes x and/or y do not get the idle state.

Work around: press a key again.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=2

From [email protected] on January 16, 2011 23:24:31

The idea is to wrap joystick hat buttons to standard joystick buttons.

For ex, the d-pad of the XBox360 gamepad is defined as a hat.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=24

From [email protected] on April 28, 2010 19:20:47

I don't know how this problem can affect the keyboard driver, but I saw the
following problem reading the code:

// 9. Release the data line.
[...]
loop_until_bit_is_set( MS_CLOCK_PIN, MS_CLOCK_BIT );

should be:

// 9. Release the data line.
[...]
loop_until_bit_is_set( KB_CLOCK_PIN, KB_CLOCK_BIT );

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=3

From [email protected] on January 04, 2011 21:26:52

Some new code allows to trigger a circular mouse movement, that shows if there vertical moves and horizontal moves are 1:1.

Press Keypad 0 to enable calibration mode, then press 'p' to trigger a circular mouse movement.

Press Keypad 0 again to disable calibration mode.

There is now a different multiplier for vertical and horizontal moves.

define DEFAULT_MULTIPLIER_X 4

define DEFAULT_MULTIPLIER_Y 9

These values allow to make 1:1 movements in call of duty: black ops, and have to be adapted depending on the game.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=18

From [email protected] on February 24, 2011 22:39:00

Launch sixemuconf, clic File>Open.

Default directory is wrong.

This occurs if sixemuconf is launched with the menu shortcut.
No problem if sixemuconf is launched from a terminal.

This is due to the use of getlogin instead of getpwuid.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=41

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=193

From [email protected] on February 26, 2011 13:21:43

If sixemugui/emuclient/sixemuconf are launched by root first, file permission/ownership of ~/.emuclient is wrong.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=42

From [email protected] on June 08, 2010 17:22:09

Joystick events will be caught and mapped to sixaxis actions.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=11

From [email protected] on January 27, 2011 23:22:31

This is not so serious since it only occurs at emuclient startup.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=29

From [email protected] on February 15, 2011 09:22:23

Sixemugui requires the sixaxis to be attached.

It would be great to save the sixaxis parameters (device bdaddr and ps3 bdaddr) in a config file so that no sixaxis would be required (except for the initial pairing with the ps3).

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=33

From [email protected] on February 23, 2011 23:09:39

Try to connect with a non paired bdaddr.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=39

From [email protected] on October 22, 2010 23:13:21

The idea is to launch several emu processes, each of them using a different bluetooth adapter.

A single emuclient process gets all events from input devices and dispatches the commands to the emu processes.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=14

From [email protected] on February 22, 2011 13:25:55

The idea is to allow the user to detect new sixaxis.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=37

From [email protected] on February 28, 2011 22:00:49

Only "down" events (rising edge) can trigger a configuration change.

The idea is to be able to switch back to the previous configuration for an "up" event (falling edge) corresponding to a configuration trigger.

This is especially useful for FPS games, with the aiming button as a trigger, so as to change the mouse translation while aiming.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=47

From [email protected] on December 22, 2010 23:00:26

The idea is to be able to change the button/axis mapping performed by the emuclient process without having to modify its source code.

At startup, the emuclient process will ask the user which configuration file has to be loaded, amongst all conf files located into a specific directory.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=17

From [email protected] on June 08, 2010 17:18:51

The idea is to switch the keymap when predefined keys are pressed.

For ex: press F9 and the keymap is changed.

A key press can trigger a macro and a keymap switch at the same time.

The triggering keys and the keymaps will be defined in configuration files that will be read at the emuclient start.

As for macros, a table of keymaps will be used, with the key code as index.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=10

From [email protected] on January 12, 2011 10:10:00

Although it's easy to write macros with a text-editor, a configuration GUI could be done to avoid the user from making typos.

Ideas:

• 1 game = 1 macros file
• keep previous format (concatenate macros into a file)

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=20

Skipping this issue number to maintain synchronization with Google Code issue IDs.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=214

From [email protected] on February 01, 2011 10:24:59

The goal of this issue is not to report a bug, but to warn people about a xorg problem that impacts left and right mouse buttons.

This problem is related to a xorg functionality called "3rd button emulation" that is useful with a 2 button mouse. Xorg waits 50ms to see if both left and right buttons are pressed, and in case it is, it generates a middle button press.

Following bug reports were filled by people complaining about that behavior:

* https://bugs.freedesktop.org//show_bug.cgi?id=1752 * https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/291694 Although a real middle button press is enough to disable the functionality, it's possible to disable it by default. Details about how to do that are given in the two bug reports.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=30

From [email protected] on February 28, 2011 21:19:26

Define a configuration trigger with a mouse button.

Original issue: http://code.google.com/p/diyps3controller/issues/detail?id=46