[Aug-20] CobaltController - PS3/Wii Controller Driver for Windows Mobile
- Thread starter Cobaltikus
- Start date
-
- Tags
- dualshock 3 wiimote
Hey Cobaltikus,
Just wondering how it went with the Mighty Rom? Working good? I tried both my sixaxis and dual shock 3 and neither one worked. I'm going to flash a new rom tonight and try it out again, not sure if I'll try stock,,, too lazy. Thanks and keep up the great work!
Fantastic!
Yeah! Works perfectly with HD2!
I'm using a PS3 SixAxis and the ROM is Artemis v17 ITA.
Playing with FPSECE is now absolutely perfect!
Much better than the Bluetooth gamepad from MSI I brought some week ago!
Yeah! Works perfectly with HD2!
I'm using a PS3 SixAxis and the ROM is Artemis v17 ITA.
Playing with FPSECE is now absolutely perfect!
Much better than the Bluetooth gamepad from MSI I brought some week ago!
I still can't seem to get it working for me, I flashed a few different roms last night, bhars, mighty full force, mr. x. I have a cdma telus tp2. Anyone have any luck with this running something similar?
EDIT:
Got it working after reading through the whole thread. I had to set my bluetooth to discoverable. I thought it was. Some other members mentioned it should be added to the front page, credit should go to them. Thanks everyone, Cobalikus, this rocks!!!!
Currently running bhars v12 cht, should work good on Mighty as well.
EDIT:
Got it working after reading through the whole thread. I had to set my bluetooth to discoverable. I thought it was. Some other members mentioned it should be added to the front page, credit should go to them. Thanks everyone, Cobalikus, this rocks!!!!
Currently running bhars v12 cht, should work good on Mighty as well.
Last edited:
Schtruck had to do one or two little changes in fpsece to get L1/2 R1/2 buttons working on fpsece (your drivers were not responsible for this)
The changes he made were made on fpsece itself, something to prevent the "71" code to remain each time you tried to press L or L buttons (now an already used code can't be used again)
I've just realuzed that fpsece doesn't seem to support the "g" letter from a keyboard (why?? I don't know!) so just R1 doesn't want to answer when wanting to map it in fpsece.
Schtruck now just has to see why this last code is not supported by fpsece, fix it, and all the buttons will be working.
And yes, you can set keys in FpseCE exactly the way you sayd: push the X icon on the phone, then press X on the gamepad or whatever keyboard
So your drivers work perfectly, that's fpsece that was a little adapted to support them better
BTW: I'm amazed by the speed of the sixaxis connecting process, almost immediate, even if the bluetooth on the phone was off before starting your application. The MSI takes at least 4 or 5 seconds before being connected!
Just a small quickly-made video to show Coblatikus drivers + fpsece on my HD2, you can see the buttons mapping then wipeout playing with my DualShock3
http://www.youtube.com/watch?v=mH_NBKtj0R8
Last edited:
This project sounds great! Coupled with FpseCE and a TV Out capable phone, this can turn our phones into extremely portable Playstation consoles WITHOUT controller cords!
I have a Touch Pro though, how is the bluetooth M$ stack development going?
It works on the Verizon Touch Pro now and most likely all windows phones
slide to settings tab, select "about phone", select "hardware information", scroll to last item: bluetooth address.
Help
I cannot get this to work with morphgear, the PS3 controller is linked to my phone and when I press the buttons the letters come up on the keyboard.
I have disabled the virtual pad in morphgear but it wont work, if I try and set anything in morphgear it just sets it as 229? Up down left and right set find but the games still do not respond to any button presses.
Anyone else got it working on morphgear?
I have turned off T9 as well, im on 6.5.3 Dutty rom.
I cannot get this to work with morphgear, the PS3 controller is linked to my phone and when I press the buttons the letters come up on the keyboard.
I have disabled the virtual pad in morphgear but it wont work, if I try and set anything in morphgear it just sets it as 229? Up down left and right set find but the games still do not respond to any button presses.
Anyone else got it working on morphgear?
I have turned off T9 as well, im on 6.5.3 Dutty rom.
Last edited:
It gets wierder, on the snes it works fine in landscape mode (expect you need to set right for up, left for down and so on.) for the megadrive it will only work in portrait... wierd...
Just make sure you enable polling input and disable fullscreen and vitual pad.
Just make sure you enable polling input and disable fullscreen and vitual pad.
no more 071 problem just take out btpad=2 from your ini file in fpsce and it also saves ya config everytime now why didnt i try that b4 lol
Download CobaltController.WS.0.1.zip from the first post, unzip it and run the exe on your phone. It will tell you the mac address. Write it down and then put it in a text file on your computer in the same directory as sixpair.exe. then continue with the steps provided.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4Good News!
GOOD NEWS EVERYONE!!!
My divorce is final, and my girlfriend dumped me.
Therefore, I am taking advantage of this massive influx of extra time to work on the Android port of CobaltController.
I'm getting the HTC Arrive on March 20th so expect a Windows Phone 7 port eventually as well. Unless of course another hottie snatches me up and drains the rest of my life out of me.
Going to Poe's Pub for some drinks and bar food alone with my laptop and free wi-fi. Side note: It's Open Mic night, just fyi, in case anyone cares to stop by and play a tune.1CobaltController
Use your Sony Playstation 3 Controller (Sixaxis/Dual Shock 3) or Nintendo Wii Remote (Wiimote) as a Bluetooth Game Controller on your Windows Phone.
It's perfect for game system emulators.
Play PlaystationOne games with FpseCE, Super Nintendo games (and more) with MorphGear (HD2 version), Nintendo, Genesis, GameBoy, GameGear games (and more) with SmartGear - There are many other emulators out there and this program/driver will work for anything that accepts keyboard input.
Compatibility
Post your results and I will update this list
You Tube VideosCode:DEVICE PS3 Wii Confirmed By ------------------------- --- --- ------------- Acer beTouch E200 ? Yes pmprog Acer Neotouch S200 Yes Yes Fenrir84 (PS3) / Snowball2010 (Wii) HTC HD2 Yes Yes Cobaltikus HTC Touch Diamond Yes No koert17 (PS3) / nightly_shadow (Wii) HTC Touch HD (Blackstone) Yes Yes RDilus HTC Touch Pro Yes No Cobaltikus HTC Touch Pro2 Yes Yes Cobaltikus HTC Touch2 Mega Yes ? RipNWO HTC Vogue No No Mycle78 HTC Wizard No ? shorty66 LG Expo Yes Yes dalb3 (PS3) / trueg (Wii) Samsung SCH-i730 No No Cobaltikus Samsung i780 Yes ? ShadowswordPL Samsung SCH-i830 No No Cobaltikus Samsung Omnia I900 Yes No Manny-77 Samsung Omnia II i8000 Yes No cyber-junkie Sony Xperia Yes No sashapont (PS3) / stratis10 (Wii) Toshiba TG01 No No Cobaltikus ... ... ... ... Your Device ? ? You
http://www.youtube.com/watch?v=mH_NBKtj0R8 (Thanks i900frenchaddict)
http://www.youtube.com/watch?v=3dH9J1y0G-8 (Thanks ahmedsaid)
http://www.youtube.com/watch?v=Qo-_nMmYq1Y (Thanks dijay_94)
http://www.youtube.com/watch?v=HauZQWYZxmQ (Thanks ShadowswordPL)
Prerequisites:
- PS3 Controller
- A compatible Windows Mobile device. Check the Compatibility list. Is your device not listed? Try out CobaltController and post your results; I'll update this post.
- A PS3 Controller (I don't know if non-Sony 3rd party controllers work - maybe they do, maybe they don't).
- A desktop or laptop computer with a USB port to set the controller's master address.
- Linux - Use sixpair - directions in this thread somewhere, search for "Ubuntu"
- Windows - Use Motion in Joy, but please note that Motion in Joy uses a different MAC format (little endian vs big endian) so for example, when I run CobaltController on my Touch Pro2 it displays "BT ADDR: 00:23:76:70:6B:4D" so I enter it into Motion in Joy as 4d.6b.70.76.23.00
- Wii Controller
- A compatible Windows Mobile device. Check the Compatibility list. Is your device not listed? Try out CobaltController and post your results; I'll update this post. Devices with the Microsoft Bluetooth Stack can't use the Wiimote yet.
- A Wii Controller.
- XBOX 360 Controller
Not Going To Happen
In order to get the XBOX 360 controller to work in windows you need to purchase a wireless receiver - it doesn't use bluetooth. It needs additional hardware. So if a full desktop Windows PC can't even do it without additional hardware, I seriously doubt it will ever work for our phones. Some company could come up with an xbox 360 wireless receiver for Windows Mobile, but again, very doubtful. And since I don't even have an XBOX of any kind, I know I'm not going to be motivated enough to even try.
Initial One Time Setup for PS3 Controllers:
Setting the PS3 controller's master address to your phone's bluetooth mac address via Windows:
- Download and install Motion in Joy.
- Run DS3 Tool, installed in the previous step.
- Click the "About" tab in DS3 Tool to see the version. If DS3 Tool is less than 0.5.0003 you will need to update.
- Connect your PS3 Controller to your computer via the USB cable and wait while Windows recognizes the new device.
- Click on the "BluetoothPair" tab.
- In the DUALSHOCK 3 drop down list select your controller. If it says "Can't find connected(USB) Playstat":
- Click "Driver Manager" directly above the drop down list
- Click "Load" and wait for it to finish
- Return to the "BluetoothPair" tab
- Run CobaltController on your Windows Mobile device to get its BT address.
- Enter that BT address into the text box directly above the DUALSHOCK 3 drop down list. Note that Motion in Joy uses a different MAC format (little endian vs big endian) so for example, a bluetooth address of "00:23:76:70:6B:4D" is entered it into Motion in Joy as "4d.6b.70.76.23.00"
- Click the radio button next to this textbox to make sure that it uses the one you entered and not the one above it which is to connect your controller to your PC
- Click "Pair Now"
- If all went well your controller is now configured to talk to your Windows Mobile device. Go to the "Quick Start" tab and click "Disconnect".
- Unplug your PS3 Controller.
- As long as you don't pair your controller with any other device (like your PS3) then you never have to do this again. If you do pair the controller with a another device and wish to re-pair it with your phone again, repeat the above steps.
Widcomm Stack Specifics:
- Turn on bluetooth and set it to discoverable. Thanks to ryotgz, skilty, and gorelshv for this information. I believe it is only required the first time you use CobaltController. Once you have successfully connected, BT does not have to be in discoverable mode any longer so you can change it back to invisible to save battery life.
- Make sure that the checkbox is not checked where it says "Allow only devices listed in 'My Devices' to connect".
- If you have never tried to connect the PS3 controller to your phone before (or at least not since the last hard reset or rom flash) it will fail to connect at first and you'll get a bunch of pop ups with PLAYSTATION(R)3 Controller shown in bold asking for the pin. Keep tapping cancel as it pops up and wait for everything to stop trying to connect. After all that, try again and it should connect just fine and should always connect right away in the future without the pin prompts. There is no pin (that I know of at least) I'm bypassing security on both the PS3 and Wii connections (even though we do know the pin for the Wiimote is the host's mac backwards.)
Microsoft Stack Specifics:
- TURN OFF BLUETOOTH The MS stack does not like the PS3 controller and will NOT pair with it. I ended up writing a modified version of this stack to get around this problem, but it will conflict with the real MS stack so they can't both be on at the same time.
- Your phone will reboot when you disconnect the controller.
PS3 Controller Specifics:
- Press the PS button to connect and then later to disconnect
Wii Controller Specifics:
- Press the red Sync button to connect. Hold down the Power button to disconnect.
Common:
- All 4 LEDs should flash a few times and then only the player one LED should remain lit showing it connected.
- The driver stops running after you disconnect to save battery life. Run it again to reconnect. It's in Start Menu\Programs\Games
- Registry Values are stored in HKEY_CURRENT_USER\Software\Cobaltikus\CobaltController
- Currently only 1 controller can be active at a time but I am exploring the ability to add more.
- Once you are connected you can tap Menu > Exit to close the configuration program and your controller will remain connected, and the driver will continue to run until your controller is disconnected.
To Do: (not necessarily in this order)
- Get Wiimote working on devices with the Microsoft Bluetooth stack
- Figure out why this doesn't work on the TG01 and HTC Vogue and fix it
- 2 player support
- Battery meter
- Integrate LeSScro graphics
- Clean up Microsoft stack code to eliminate the need to reboot
- Add support for non-touch-screen devices
Attachments
- CobaltController.vX.X.cab = Installs to \Program Files\CobaltController\ and a shortcut goes to \Windows\Start Menu\Programs\Games
- NETCFv35.wm.armv4i.cab = Although the CobaltController driver is written in native C++, the UI is written in .Net 3.5, therefore you will need to have .NetCF 3.5 installed on your device to run the UI. You might already have this by default so try without this first, and come back if you get an error message about needing it.
- NETCFv35.Messages.EN.wm.cab = Provides more details when .Net errors occur with any program written in .Net 3.5. This is optional and only needed if a .Net error occurs and you wish to see more details about that error.
Change Log
- v0.7
- Sorry - no actual driver enhancements yet - just bug fixes
- IMPORTANT - Different Default Buttons - you may need to remap in your emulator settings
- Updated instructions (Menu > Instructions)
- Menu reorganized, some new menu items exist
- More Bluetooth "stuff" working in the UI
- UI Settings Bug Fixes (values not sticking etc)
- v0.6
- ANALOG STICKS WORKING!
- Menu reorganized, some new menu items exist
- More Bluetooth "stuff" in the UI - Mainly for devices with the M$ stack
- Some other tweaks and changes but these are all the important ones.
- v0.5
- New Icon
- UI Uses .Net 3.5, (driver is still c++)
- Option to restore default keycodes
- Bluetooth Address shown on screen so you don't have to search for it
- 229 fix - it could cause you to not like how the SIP works in other programs but you can always restore, so no worries.
- I might have forgotten about another change or two but these are all the important ones.
- v0.4
- Updated Instructions (Menu > Help > Instructions > [PS3|Wii])
- Added Menu > Help > About to verify version
1Great App. Flawless Victory!
I've been using this on my HD2, and must say, you've outdone yourself Kobaltikus.
I <3 you!!!
Just donated $5 - I think everyone here who uses your app should follow suit. It takes work to code, and guts to release working programs for free. Cobaltikus deserves it
I now have a PS3 controller to play my NES, SNES, Sega Genesis, PSOne, and GameBoy color games. I'm getting virtually flawless emulation out of all these systems after some good research.
Using Cobalt Controller for Emulators
The following is how I got my new PS3 Cobalt Controller working on my HD2 alongside virtually flawless emulation of my games. I was dreadfully frustrated in finding the best emulators, AND getting them working with my new PS3 controller, but I now have it all figured out to a 'T'. I'm posting this because I was hoping someone would do the same for me. Enjoy!
NES: I use PocketNester. The only problem with PocketNester, is it doesn't support soft-keys, and thus no Cobalt Controller.
Fix: Install PocketNesterPlus (soft-key support), then go back to using PocketNester. The mappings now work flawlessly, and the emulation is near perfect.
SNES: Morphgear is a really decent SNES emulator. Problem: when mapping keys, the mappings only show up as '229' in the settings.
Fix: Find and install KforTP, made by ShinRa. Switch to M$.
Also, mappings still won't work in-game.
Fix: Go to 'Global Settings', enable 'Polling Method'.
Sega Genesis: SmartGear is nearly perfect for this. Go to the main page, and look under the Latest News for " ... new fixes/features and give it a try here." - click 'here'. Scroll down to the download link for the beta version. Might need KforTP - I forget if I needed it for this one.
PSOne: Use FPSECE. Select the controller icon, and press on the buttons you want to map on your screen (yes, press on the buttons that are on the controller image on your screen), then press the respective button on the controller.
Bug: I noticed that if R1 is pressed while FPSECE is open, FPSECE thinks it's stuck down and when you go to map any other buttons, it sets those buttons to the R1 key. Have to reset to get rid of this. Use an analogue stick button for this instead.
Edit: This is an old bug - it has been fixed with the newer version of Cobalt Controller. *where have I been?! - gasps*
Thanks Cobalt!
Gameboy Color: I use MorphGear for this - it works great. No issues so far.1Ya, I discuss the sad state of Emulators for Windows Mobile on my site (http://www.computerabuser.com/?p=876). Anyway, from there you can link to a roundup I did for WVGA compatible emulators on a different forum. It's not all bad, especially if you are willing to shell out $10 for SmartGear which is pretty awesome.1 - PS3 Controller
