windows 10

[Brett Ridel]

Hi all

I recently installed windows 10, but I don't succeed to execute the examples.

I followed the following steps : https://github.com/thp/psmoveapi/blob/master/README.win32

example.exe give me the this message : 

D:\softwares\psmoveapi\build>example.exe

Connected controllers: 1

Could not connect to default Move controller.

Please connect one via USB or Bluetooth.

I have no idea of what could be my problem.

Brett

[Chadwick Boulay]

Hi Brett,

Do you mind trying my fork? I've put a lot of work into Windows compatibility (well, mostly MSVC compatibility) and I'm curious if it will work with Window 10.

https://github.com/cboulay/psmoveapi

See README.win64_msvc if you're willing to use MSVC 2013.

[Alexander Nitsch]

> I have no idea of what could be my problem.

Same here without more information about your setup. ;)

Are you building the recent master branch from source or are you using
the 3.0.0 binary release?

What controllers are attached and how? Is it working via USB? Was
psmovepair.exe successful in setting up a working Bluetooth connection
(i.e. is the small red LED on)?

[Brett Ridel]

I'm compiling the last version from the git repository, with mingw64 32bit.

I used a psmove (with the colored ball ;-) )

When I plug the psmove via usb, the red LED twinkle.

psmovepair.exe and example.exe don't work (with the message I show above).

I will test with Chadwick's fork, and will let you know.

Brett

[Chadwick Boulay]

Hi Brett,

In Windows 8.1, it was necessary to do a 2-step pairing process. First psmovepair.exe, then Alex's psmove-pair-win (from here: https://github.com/nitsch/psmove-pair-win).

This is true both for the upstream repo and for my fork.

If you want to save yourself some time, you can try the binaries I've compiled from my fork here: https://github.com/cboulay/psmove-ue4/tree/master/Binaries/Win64

[Brett Ridel]

Thank you for the help

I test the binaries, here is the message error (psmove-pair-win.exe)

==== Looking for Bluetooth radios ====
  (0)  e8:2a:ea:59:ed:17  DESKTOP-BDDG545
Using the only available Bluetooth radio.
Making radio accept incoming connections.
Making radio discoverable.

==== Connecting new controllers ====
Device: (0)  00:06:f7:a7:a7:07
                          CoD: 0x00002508, CON: 1, REM: 0, AUTH: 0

Device: (0)  00:06:f7:a7:a7:07  Motion Controller
                          CoD: 0x00002508, CON: 1, REM: 0, AUTH: 0
device #0: Move Motion Controller detected
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707
[ERROR 0x00000002] Failed to open registry key: Le fichier spÚcifiÚ est introuvable.
- checking HID service
- enabling HID service
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707
[ERROR 0x000000ea] Failed to get registry value: Plus de donnÚes sont disponibles .
Set VirtuallyCabled: 1
- verifying successful connection RE
Device removed - retry
Device: (0)  00:06:f7:a7:a7:07  Motion Controller
                          CoD: 0x00002508, CON: 0, REM: 0, AUTH: 0
device #0: Move Motion Controller detected
Device removed - retry
Device: (0)  00:06:f7:a7:a7:07  Motion Controller
                          CoD: 0x00002508, CON: 0, REM: 0, AUTH: 0
device #0: Move Motion Controller detected
Device removed - retry
Device: (0)  00:06:f7:a7:a7:07  Motion Controller
                          CoD: 0x00002508, CON: 0, REM: 0, AUTH: 0
device #0: Move Motion Controller detected
Device removed - retry
No Bluetooth devices found.
No Bluetooth devices found.

I precise that the bluetooth of my computer seems to work (it detect my smarphone), and the bluetooth of my psmove works too (for example on my ps3)

Brett

[Brett Ridel]

Ok, I just finish to test with the fork, compiling with msvc.

I still have the same issues.

Just one point (maybe important ?), the compilation finished with errors (the opengl examples)

 

========== Build: 31 succeeded, 3 failed, 3 up-to-date, 0 skipped ==========

 

And, there is no "psmove-pair-win.exe" in the folder, just the "psmovepair.exe".

So, I can just use the "psmve-pair-win.exe" from there https://github.com/cboulay/psmove-ue4/tree/master/Binaries/Win64

This is strange, because my psmove seems to be connected (Connected controllers: 1) but not detected/used.

Brett

[Chadwick Boulay]

It seems that not all Bluetooth adapters work with all controllers. I've had success with the ASUS BT-400 but I've read many complaints about people not being able to connect with one dongle but they can connect with another.

Also, the psmove-pair-win process sometimes takes several tries before it can work and you should be pressing the PS button on your controller throughout the process. Sometimes it doesn't work for me, but I  usually get it within 3-4 tries. Maybe it's a timing issue.

[Chadwick Boulay]

And, there is no "psmove-pair-win.exe" in the folder, just the "psmovepair.exe".

So, I can just use the "psmve-pair-win.exe" from there https://github.com/cboulay/psmove-ue4/tree/master/Binaries/Win64

That's right. It's from a separate repository on Alex's github page. There have been a couple attempts to integrate it into psmoveapi but then it sometimes causes a 'blue screen of death'. So for now it's separate.

 

This is strange, because my psmove seems to be connected (Connected controllers: 1) but not detected/used.

The USB connection is 1 connection. If it were also paired & connected via bluetooth then you'd have 2 connections. These different connections can confuse psmoveapi so it's better to unplug the USB connection after it's been paired successfully (including both psmovepair.exe and psmove-pair-win.exe). 

[Brett Ridel]

It seems that not all Bluetooth adapters work with all controllers. I've had success with the ASUS BT-400 but I've read many complaints about people not being able to connect with one dongle but they can connect with another.

Also, the psmove-pair-win process sometimes takes several tries before it can work and you should be pressing the PS button on your controller throughout the process. Sometimes it doesn't work for me, but I  usually get it within 3-4 tries. Maybe it's a timing issue.

Ok, I succeed to pair my psmove with my computer, here is the message (if you wan't to see it)

==== Looking for Bluetooth radios ====
  (0)  e8:2a:ea:59:ed:17  DESKTOP-BDDG545
Using the only available Bluetooth radio.

==== Connecting new controllers ====

No Bluetooth devices found.
No Bluetooth devices found.
No Bluetooth devices found.
No Bluetooth devices found.

Device: (0)  00:06:f7:a7:a7:07

                          CoD: 0x00002508, CON: 0, REM: 0, AUTH: 0

Device: (0)  00:06:f7:a7:a7:07
                          CoD: 0x00002508, CON: 1, REM: 0, AUTH: 0

Device: (0)  00:06:f7:a7:a7:07  Motion Controller
                          CoD: 0x00002508, CON: 1, REM: 0, AUTH: 0
device #0: Move Motion Controller detected
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707
[ERROR 0x00000002] Failed to open registry key: Le fichier spÚcifiÚ est introuvable.
- checking HID service
- enabling HID service
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707
[ERROR 0x000000ea] Failed to get registry value: Plus de donnÚes sont disponibles .
Set VirtuallyCabled: 1
- verifying successful connection RE
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707
[ERROR 0x000000ea] Failed to get registry value: Plus de donnÚes sont disponibles .
Set VirtuallyCabled: 1

- checking HID service
- verifying successful connection CRE.RE

radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707
[ERROR 0x000000ea] Failed to get registry value: Plus de donnÚes sont disponibles .
Set VirtuallyCabled: 1
- checking HID service
- enabling HID service
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707
[ERROR 0x000000ea] Failed to get registry value: Plus de donnÚes sont disponibles .
Set VirtuallyCabled: 1
- verifying successful connection RE
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707
[ERROR 0x000000ea] Failed to get registry value: Plus de donnÚes sont disponibles .
Set VirtuallyCabled: 1

- checking HID service
- verifying successful connection CRE.CRE.CRE.CRE.CRE.
- !!!! Successfully connected device 00:06:f7:a7:a7:07 !!!!

Device: (0)  00:06:f7:a7:a7:07  Motion Controller

                          CoD: 0x00002508, CON: 1, REM: 1, AUTH: 0

device #0: Move Motion Controller detected
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707

[ERROR 0x000000ea] Failed to get registry value: Plus de donnÚes sont disponibles .
Set VirtuallyCabled: 1

- checking HID service
- verifying successful connection CRE.CRE.CRE.CRE.CRE.
- !!!! Successfully connected device 00:06:f7:a7:a7:07 !!!!

Device: (0)  00:06:f7:a7:a7:07  Motion Controller

                          CoD: 0x00002508, CON: 1, REM: 1, AUTH: 0

device #0: Move Motion Controller detected
radioInfo.address: e82aea59ed17
deviceInfo.address: 0006f7a7a707
sSubkey: SYSTEM\CurrentControlSet\Services\HidBth\Parameters\Devices\e82aea59ed170006f7a7a707

[ERROR 0x000000ea] Failed to get registry value: Plus de donnÚes sont disponibles .
Set VirtuallyCabled: 1

- checking HID service
- verifying successful connection CRE.CRE.

Now, my psmove has a red LED completely turned on. But, I still can't execute "example.exe" :

D:\softwares\psmoveapi\build\Release>example.exe

Connected controllers: 1
Could not connect to default Move controller.
Please connect one via USB or Bluetooth.

I precise that I've copied the "psmove-pair-win.exe" in the same folder as all my binaries (example.exe, psmovepair.exe, etc...)

Brett 

[Chadwick Boulay]

D:\softwares\psmoveapi\build\Release>example.exe
Connected controllers: 1
Could not connect to default Move controller.
Please connect one via USB or Bluetooth.

I precise that I've copied the "psmove-pair-win.exe" in the same folder as all my binaries (example.exe, psmovepair.exe, etc...)

After you've paired the controller then you don't need psmove-pair-win.exe anymore. It's not a dll, it doesn't matter where you put it.

Did you also disconnect the USB cable?

Can you try test_calibration.exe?

Can you e-mail me or message me the errors you get when trying to build the opengl examples? I invited you to a google hangouts.

N.B. Je comprends francais si cela plus facile pour vous. But I may answer in English.

[Alexander Nitsch]

> Now, my psmove has a red LED completely turned on. But, I still can't
> execute "example.exe" :
>
> D:\softwares\psmoveapi\build\Release>example.exe
>> Connected controllers: 1
>> Could not connect to default Move controller.
>> Please connect one via USB or Bluetooth.

That probably means that Windows 10 changed some more Bluetooth-related
peculiarities. The current psmoveapi already contains some workaround
for Windows. If you can, try stepping through the library code and see
what happens, where it fails etc.

BTW, building with -DPSMOVE_USE_DEBUG might also output something helpful.

[Alexander Nitsch]

Did you eventually sort things out or do we indeed have a problem with
Windows 10?

There was no more info from the point on where Chadwick suggested
personal messages ...

[Chadwick Boulay]

Here's a message Brett sent me. I was waiting for him to post it here but I guess he is busy. I instructed him to post an issue on thp's psmoveapi repo but I guess he hasn't done that yet.

I didn't have lot of time today to debug the psmoveapi on windows 10.
The only thing I've found is that "hid_open_path" function return NULL at this step (in the "psmove_connect_internal" function)

move->handle = hid_open_path(move->device_path);

And, I found that the "hid_open_path" return NULL at this part :

/* Check validity of write_handle. */
if (dev->device_handle == INVALID_HANDLE_VALUE) {
     /* Unable to open the device. */
     register_error(dev, "CreateFile");
     goto err;
}

If this can help, here are the values of move->device_path and move->device_path_addr, used as parameters of "hid_open_path" in the "psmove_connect_internal" function.
(I precise that only the call with move->device_path return NULL.

via usb:

move->device_path_addr : \\?\hid#vid_054c&pid_03d5&col02#6&2c1fccc&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
move->device_path      : \\?\hid#vid_054c&pid_03d5&col01#6&2c1fccc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

via bluetooth:

move->device_path_addr : \\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d5&col02#9&31d8ad89&1&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
move->device_path      : \\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002054c_pid&03d5&col01#9&31d8ad89&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[Brett Ridel]

Hi all

Sorry for the delay.

My computer is dead, for the moment I have no other way to deepen my test.

Chadwick has said all I had found.

Brett

[Péter Balogh]

Hi,

We're using the codes with hidapi 0.7.0 without issues on Windows 10
Can you try replacing the hidapi lib with an updated one?

Peter

[Alexander Nitsch]

> We're using the codes with hidapi 0.7.0 without issues on Windows 10
> Can you try replacing the hidapi lib with an updated one?

Are you sure you meant version 0.7.0? By default, psmoveapi uses a much
more recent version. So switching to 0.7.0 would actually be a downgrade.

[Péter Balogh]

pretty sure, I've got it from here:
https://github.com/signal11/hidapi/downloads
but it does seem old, I'll try updating to the latest git version, and see, what happens