Launch is not found when scanning for devices, but I can pair my dongle to it!


#1

Hey guys,

I just upgraded to Windows 10, and I can verify that I am running on build 15063. I have buttplug installed, and I can run the websocket server. I then start ScriptPlayer, turn the Launch on (blue LED starts blinking) and I start scanning for devices, but nothing happens. I also tried this after I paired the BLE dongle to the Launch using Windows. Am I doing something wrong here!?

Here is the log:

2017-08-15 22:28:08.2843|INFO|Buttplug.Components.Controls.ButtplugTabControl|Can't load assembly file, no version info available!
2017-08-15 22:28:08.2843|INFO|Buttplug.Components.Controls.ButtplugTabControl|Windows Release ID: 1703
2017-08-15 22:28:25.5393|DEBUG|ButtplugServer|Setting up ButtplugServer
2017-08-15 22:28:25.5513|INFO|ButtplugJsonMessageParser|Setting up ButtplugJsonMessageParser
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|Message type count: 22
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- Ok
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- Ping
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- Test
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- Error
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- DeviceList
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- DeviceAdded
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- DeviceRemoved
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- RequestDeviceList
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- StartScanning
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- StopScanning
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- ScanningFinished
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- RequestLog
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- Log
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- RequestServerInfo
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- ServerInfo
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- FleshlightLaunchFW12Cmd
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- LovenseCmd
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- KiirooCmd
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- VorzeA10CycloneCmd
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- SingleMotorVibrateCmd
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- StopDeviceCmd
2017-08-15 22:28:25.5513|DEBUG|ButtplugJsonMessageParser|- StopAllDevices
2017-08-15 22:28:25.7471|INFO|DeviceManager|Setting up DeviceManager
2017-08-15 22:28:25.7471|INFO|ButtplugServer|Finished setting up ButtplugServer
2017-08-15 22:28:25.7471|INFO|Buttplug.Components.Controls.ButtplugTabControl|Windows Version: Microsoft Windows NT 6.2.9200.0
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Setting up Device Manager UWPBluetoothManager
2017-08-15 22:28:25.7566|INFO|UWPBluetoothManager|Loading UWP Bluetooth Manager
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Loading Bluetooth Device Factory: FleshlightLaunchBluetoothInfo
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Loading Bluetooth Device Factory: KiirooBluetoothInfo
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Loading Bluetooth Device Factory: LovenseRev1BluetoothInfo
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Loading Bluetooth Device Factory: LovenseRev2BluetoothInfo
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Loading Bluetooth Device Factory: LovenseRev3BluetoothInfo
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Loading Bluetooth Device Factory: MagicMotionBluetoothInfo
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Loading Bluetooth Device Factory: VibratissimoBluetoothInfo
2017-08-15 22:28:25.7566|DEBUG|UWPBluetoothManager|Loading Bluetooth Device Factory: VorzeA10CycloneInfo
2017-08-15 22:28:25.7659|DEBUG|XInputGamepadManager|Setting up Device Manager XInputGamepadManager
2017-08-15 22:28:25.7659|INFO|XInputGamepadManager|Loading XInput Gamepad Manager
2017-08-15 22:28:25.8037|DEBUG|ButtplugServer|Got RequestServerInfo Message
2017-08-15 22:28:25.8547|DEBUG|DeviceManager|Got RequestDeviceList Message
2017-08-15 22:28:30.3179|DEBUG|DeviceManager|Got StartScanning Message
2017-08-15 22:28:30.3179|INFO|UWPBluetoothManager|Starting BLE Scanning
2017-08-15 22:28:30.3179|INFO|UWPBluetoothManager|Stopped BLE Scanning
2017-08-15 22:28:30.3179|INFO|XInputGamepadManager|XInputGamepadManager start scanning

#2

Small update, I also started my Vorze Cyclone, and that is also not being scanned, so I think the problem lies with the connection between the software and the bluetooth dongle, perhaps someone knows what it is…


#3

Okay, I managed to find it! I think my HTC vive was interfering with it. I did not install steamVR yet, so I think it was trying to connect to the bluetooth of the HTC vive, but those drivers weren’t installed yet. I removed all my bluetooth drivers, disconnected the vive, and now it works! Do you guys know if the HTC vive can be used as a bluetooth connection to the Launch?


#4

Ok, the problem may have actually been that you paired it with Windows. The type of connection we used to the Launch requires that the device /not/ be paired with the OS.

As far as using it alongside the Vive, I… think you should be ok? I only have an Oculus at the moment but I’ve had no problems with the two interfering. I think it may have been the pairing step that was getting in your way. I’ll try to get a “don’t pair” section added to the tutorial. :slight_smile: