Originally Posted by Stratman95

After the wii controller is connected, I select Menu-Controllers-Wii-Player1. In the configuration menu when I select up and press up on the controller it logs it as 37, right as 50, down as 50, and left as 37. It seems like they should each have their own unique number mapped to function correctly.

Yeah... that's not how you are supposed to use that... my bad though... not your fault. I should have explained it. I'm uploading version 0.7 right after I finish updating my instructions.

In the meantime, don't use the controller to set those values, use your SIP (virtual keypad). The driver already knows that when you press up on the controller that you are pressing up on the controller. This settings form is meant to configure which keyboard button you want "up" to simulate. So if you want the up button on your controller to simulate an "A" key, then you put 65 in that textbox or check the detect checkbox and press "A" on your sip. Does that make sense? I removed the detect option in v0.7. You'll just have to know the keycodes if you want to change anything. I hope it's not too confusing. I wrote it so I already understood how it should work before it wrote it and I sometimes lose sight of that fact that others wont know unless I explain it. I was hoping it would be self explanatory, but I was wrong. But I'll keep trying.

Ok, that makes more sense. Thanks for the replies and your work on this project, it is much appreciated!

v0.7

---

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)

Thx for new stuff...
bug fixes is already a good way...

LeSScro

@ DJaDjfreund...
Bro'... Wm6.5 is dead...
All users need to switch to WP7...
I know, shame on M$ but i keep all my device then i have a big Pocket to move with all this device...

Originally Posted by Stratman95

Ok, that makes more sense. Thanks for the replies and your work on this project, it is much appreciated!

If you, or anyone else, encountered any key mapping issues in previous versions of CobaltController, and the key mapping issues still exist in v0.7, run CobaltControler and go to Menu > Controllers > ...[which ever controller you are using] and then tap Return > Restore Defaults. That should take care of it.

Let me know if problems persist.

Note for those editing reg values: The reg values for the Wii: UP, RIGHT, DOWN, LEFT are set as if you are holding the controller vertically with the D-Pad at the top, whereas the LEFT, UP, RIGHT, DOWN in the CobaltController settings app are set as if you are holding the controller horizontally with the D-Pad on the left. It can get kind of confusing if you are editing in both places, but hopefully the need to edit the registry directly has been eliminated and you can return to just using the CobaltController UI.

Just a quick update. I tried the new version and it works perfectly. Thanks again!

Thanks for giving us the option to configure the key codes inside.

I must admit, I'm still confused on why after clicking the "Connect" button, you still prompt a second dialog you have to confirm. Surely the act of clicking the main button is an indication you're ready?



O/T Rant

Originally Posted by lesscro

Bro'... Wm6.5 is dead...

As long as I (or anybody else) own a WM6.5 device, it isn't dead

Originally Posted by lesscro

All users need to switch to WP7...

Why? None of the software I use on my WM6.5 device will work on a 7 device. That means purchasing a whole new range of software when my current stuff works fine.

Originally Posted by lesscro

I know, shame on M$ but i keep all my device then i have a big Pocket to move with all this device...

Maybe you could buy us all new 7 phones then

I'm at my wits end. I've paired up my ps3 controller in the past to my hd2. Yesterday I had to repair it to my ps3. Since, i can not get it to repair to my hd2. I've tried everything and it gets me no where.


Help me.

Update. I installed the newest cab and its for some reason picked it up like nothing. I guess the problem was in the 0.6 cab.

Originally Posted by pmprog

As long as I (or anybody else) own a WM6.5 device, it isn't dead

You right dude... always a user and a dev have this phone...
Wm6.5 is not dead but microsoft do not provide more support or rom dev...
Then it s a Dead UI...

Originally Posted by pmprog

Why? None of the software I use on my WM6.5 device will work on a 7 device. That means purchasing a whole new range of software when my current stuff works fine.

I agree, but lot of standard software are now updated and fingerfriendly on this phone... Like Locker, Player, UI and more... and if it s unlocked... i will hope the new way to XDA WP7 Thread...

Originally Posted by pmprog

Maybe you could buy us all new 7 phones then

If you want... i have a Xtra Buyer Price from HTC...
Then send me your money... and i send you a Phone with a low price...

Originally Posted by lesscro

If you want... i have a Xtra Buyer Price from HTC...
Then send me your money... and i send you a Phone with a low price...

How much would the new Desire HD cost?