Main improvements:
- multiple emu (but still single mouse & keyboard)
- configuration switch/switch back
- compatibility with QtSixA
- buttons to stick mapping improved
All corrected issues:
Download link: sixemu_0.15-1_i386.deb
Enjoy!!
GIMX adapts your gaming devices!
Hi!
Dear Sir, can you help me please?
I try to build sixemu project in Eclipse/CDT using tips from WiKi.
But now I'm stuck on "multiple definition of `main`" error 🙁
Hi,
You have to tell eclipse not to generate a makefile automatically: right clic on the project, then properties, C/C++ Build, disable "Generate makefile automatically", and adjust "Build directory" so that it matches the makefile directory (the same directory as emu.c, emuclient.c, etc).
It works, thank you!
hey matlo. is there any way of reading a sixaxis adress under windows OS?
It's probably possible to compile sixaddr or sixpair for windows, since there are libusb ports.
only wish i had the knowledge to do that…well gues i have to do some googleling but i'm sure it's not that simple.
Why do you want to read the sixaxis address in windows? If there is a good reason, I can help you to do that.
well i have another friend that has a sixaxis so i could use his adress too for a second gamepad. the problem is that he is very far and has no knowledge of linux whatsoever.
Even if you get this address, you still have to pair it with your ps3. Don't forget the pairing is done by connecting the usb cable+pressing the ps3 button.
Any bt address (such as a dongle address) may be paired with the ps3 thanks to a teensy++ or another usb dev board.
ohhh…i get it now. thanks for the info .
Just letting you know that EVERYTHING works amazing! I was able to fix my profile to give me 100% perfect mouse feel.
Just maybe more configs per saved file?? I need two per class and I play snipe, sub machine, assault, shotgun.
Each one needs its own ADS profile.
Secondly, I was wondering if there was a USB to ps3 implementation, would we be able to get a latency improvement? Or perhaps something with the Bluetooth packets/frequency.
Just looking for any advantage possible.
You rock.
hi matlo. i have succesfully cloned another ps3 sixaxis. my question is how do i write a second config for the second sixaxis. the same situation as the first, i only paired it to my ps3 and extracted the adress, i don't own it.
sorry for that …stupid question. just added another line to the config and it shows up. unfortunately i have a bigger problem, can't use 2 bluetooth dongles in the same time in windows so can't use them in the VM eighter.
Hello Matlo,
I'm having the issue that i can 'play' for some seconds, but then the ps3 shows "please reconnect controller", i restart the emuclient and then again, after a few seconds "please reconnect controller". Any idea why this is happening?
@veronika
I created issue 59.
There is no usb implementation yet. The bt solution will remain to 10ms since it's the sixaxis report period (reducing it causes disturbance).
Hello Matlo,
I see you figured out how to have more than one emu/Sixaxis. What was it that was preventing a real controller and Emu from being connected at the same time?
Now that I know a little bit about programming, Im going to try to make my own, but Im doing it using python so Im using the Hidemulator code as a guide.
My dongle class is set to 0x0508, but when I connect the hidemulator, the real controller eventually shuts off after about 30 secs. What could it be?
Hello,
The class is not checked by the ps3 at startup. If you don't set the class and try to connect the emulator after the ps3 is started, it won't work.
About your problem: is your emulated sixaxis using the same bt address as the real one?
Hello,
The emulator is using a different bdaddr from a second controller. The BT dongle is set to gamepad class, I can disconnect and reconnect even after ps3 is on.
The real sixaxis will only connect if the emulator is off. Once I turn on the emulator, the real sixaxis turns off after about 15 seconds.
Then I try to reconnect real sixaxis while emulator is still on, but it wont connect until I turn of the emulator. Only the leds are flashing.
If I turn off the emulator while they are flashing, the real sixaxis will connect, else the connection attempt times out.
Before it turns off, I can control the ps3 w/ both the real sixaxis and the emu.
if I connect the real sixaxis w/ usb cable, it will work along side the emulator. When I disconnect the cable, the leds immediately start flashing trying to establish connection but ultimately fails.
Also I forgot to add, Im doing this on a 60gb fat ps3.I also have a slim ps3.
When I use the hidemulator on the slim, the input is laggy. If I press a key on the keyboard, input doesnt happen until 10 seconds later. On the fat ps3 everything works fine. Maybe a difference in bluetooth hardware?
When I use you sixemu (instead of hidemu) everything works fine on both fat ps3 and slim ps3. Thats why I thought maybe you found a solution.
Another question I have, currently sixemu doesnt work with PS2 games and backwards compatibility correct?
When I tried sixemu on the fat ps3, I think the emu connected but controls wouldnt work.
In order to connect multiple emu processes to the ps3 I also added some arguments to the emu process.
One of them is the sixaxis number, which is defined in sixaxis.c and is used to modify a buffer a few lines after.
I hope this helps!
Ok I managed to keep them both connected. I have to start the emulator first, then turn on the real sixaxis. When the leds start flashing, I wait about 5 seconds and then I turn off the emulator.Then the sixaxis connects and then I restart the emulator.
If I leave the emulator on the whole time, the sixaxis never connects…weird.
Hello,
How Do you make two connections with sixemugui? When I try to connect the second dongle I get an error message to try another dongle. Both dongles work if used by itself.
It works fine on my side. I managed to emulate 7 (the max) controllers at the same time.
I didn't tested connecting emulated + real sixaxis at the same time lately. And I can't tell if I already got it work. According to what I wrote some time ago in issue 14 I probably didn't.
Hello,
How can I tell if I have the latest version of Sixemu?
Here is a video of me trying to connect two dongles. Am I doing it right?
http://youtu.be/rvcJFtASFCs
If you can confirm that perhaps the problem is my dongles I will try to buy some compatible dongles. Thanks!
Maybe I should ask, Does the multiple emu apply to amd64? I see the download link above is only for i386 but I am using the 64 one. Could it be thats the problem?
Some remarks:
– it's not required to change the dongle class: Sixemugui sets the dongle class when you start emu.
– if your bdaddrs are modified permanently, there is no need to re-select the sixaxis (unless you are using several PS3s).
Could you please:
– start Sixemugui in a terminal
– try to connect 2 emus
– send me the trace that is displayed in the terminal
Not sure this trace will be enough to debug this. I may ask you some other actions after that 🙂
I tested version 0.20 with 2 bluecore2-external dongles, and it works fine on my side. I also tried to connect a real sixaxis before/after the emulator, I didn't see any issue. Changing the sixaxis id also seems to work fine.
Hello I dont think I have the latest version. I think I never upddated to sixemu_0.20-1_amd64 I kept the 0.15. because of the BIG RED WARNING lol.
Yea I changed the class thru terminal just to show it thru the video.
Im afraid I dont know how to do the trace Im still clueless to such things.
Ok I think i get what you mean let me try…..
I think there was no big change between 0.15 and 0.20 regarding to running multiple emu.
Running Sixemugui in a terminal is easy:
Applications → Accessories → Terminal
Type "sixemugui" without quotes and hit enter.
Whew. Thank you. I was trying to do it like this "./sixemugui " but it wasnt working lol
Here is the result:
tangoblast@tangoblast-linux:~$ sixemugui
No controller found on USB busses.
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:FB:68:84:FE ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:1473 acl:0 sco:0 events:40 errors:0
TX bytes:330 acl:0 sco:0 commands:40 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'ToshibaBt'
Class: 0x480000
Service Classes: Capturing, Telephony
Device Class: Miscellaneous,
HCI Version: 1.1 (0x1) Revision: 0x20d
LMP Version: 1.1 (0x1) Subversion: 0x20d
Manufacturer: Cambridge Silicon Radio (10)
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:FB:68:84:FE ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02-External
Max key size: 56 bit
SCO mapping: HCI
hci1: Type: BR/EDR Bus: USB
BD Address: 00:21:4F:14:D1:09 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:1498 acl:0 sco:0 events:41 errors:0
TX bytes:330 acl:0 sco:0 commands:40 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: '1234-29094DA86A'
Class: 0x480000
Service Classes: Capturing, Telephony
Device Class: Miscellaneous,
HCI Version: 1.1 (0x1) Revision: 0x33c
LMP Version: 1.1 (0x1) Subversion: 0x33c
Manufacturer: Cambridge Silicon Radio (10)
hci1: Type: BR/EDR Bus: USB
BD Address: 00:21:4F:14:D1:09 ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.14
Chip version: BlueCore02-External
Max key size: 56 bit
SCO mapping: HCI
Can't get device info: No such device
run as root user to set device class
connecting with hci0 = 00:1B:FB:68:84:FE to 00:13:A9:6B:77:95 psm 17
connecting with hci0 = 00:1B:FB:68:84:FE to 00:13:A9:6B:77:95 psm 19
connected
emu_thread: end
run as root user to set device class
connecting with hci1 = 00:21:4F:14:D1:09 to 00:13:A9:6B:77:95 psm 17
emu: can't connect to control psm: Host is down
can't connect to control psm
emu_thread: end
no more cin: exiting
emu: error on ctrl psm
cleaning up
Does it give the same error with both the slim and fat ps3s?
Hmmmn it works on the slim.
from terminal:
tangoblast@tangoblast-linux:~$ sixemugui
No controller found on USB busses.
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:FB:68:84:FE ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:4353 acl:21 sco:0 events:170 errors:0
TX bytes:5185 acl:86 sco:0 commands:73 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'ToshibaBt'
Class: 0x000508
Service Classes: Unspecified
Device Class: Peripheral, Gamepad
HCI Version: 1.1 (0x1) Revision: 0x20d
LMP Version: 1.1 (0x1) Subversion: 0x20d
Manufacturer: Cambridge Silicon Radio (10)
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:FB:68:84:FE ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02-External
Max key size: 56 bit
SCO mapping: HCI
hci1: Type: BR/EDR Bus: USB
BD Address: 00:21:4F:14:D1:09 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:2723 acl:0 sco:0 events:72 errors:0
TX bytes:721 acl:0 sco:0 commands:70 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: '1234-29094DA86A'
Class: 0x000508
Service Classes: Unspecified
Device Class: Peripheral, Gamepad
HCI Version: 1.1 (0x1) Revision: 0x33c
LMP Version: 1.1 (0x1) Subversion: 0x33c
Manufacturer: Cambridge Silicon Radio (10)
hci1: Type: BR/EDR Bus: USB
BD Address: 00:21:4F:14:D1:09 ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.14
Chip version: BlueCore02-External
Max key size: 56 bit
SCO mapping: HCI
Can't get device info: No such device
run as root user to set device class
connecting with hci0 = 00:1B:FB:68:84:FE to 00:26:5c:f2:0e:22 psm 17
connecting with hci0 = 00:1B:FB:68:84:FE to 00:26:5c:f2:0e:22 psm 19
connected
emu_thread: end
run as root user to set device class
connecting with hci1 = 00:21:4F:14:D1:09 to 00:26:5c:f2:0e:22 psm 17
connecting with hci1 = 00:21:4F:14:D1:09 to 00:26:5c:f2:0e:22 psm 19
connected
emu_thread: end
connected to emu 0
connected to emu 1
Exiting
no more cin: exiting
emu: error on ctrl psm
cleaning upemu: error on ctrl psm
cleaning upno more cin: exiting
emu: no process found
tangoblast@tangoblast-linux:~$
————————–
On the fat ps3 it still has 3.15 firmware that could be why. :-/ I didnt think it would make a difference…oops
Right, this could explain why multiple emulators don't work with your fat ps3. The fat 60 ps3 is also a very specific version of the ps3.
I don't see any reason why it doesn't work. But there is probably something not compatible in the sixaxis emulator.
Why are you keeping the 3.15 firmware? OtherOS?
If you want me to work on this, please open an issue. I will then ask you a few traces. But I can't promise I will work on this as I have many other tasks with a higher priority.
Yes sir because of OtherOS. I just bought a slim and never updated the fat. I didnt think the firmware would make a difference. I would'nt have thought that they change the way bluetooth connects between models.
I'll open an issue soon, I understand that it'll be low priority as it should be.