The WinUSB installation link in Noble Wiki is dead, but a web search pointed to this link as the modern replacement.
I searched for the hardware on that list, and thought the Asus USB-BT400 (*) was cheap enough to order and give it a try.įor the BT400 to function under Noble, I also needed to circumvent the normal driver installation process and instead install WinUSB so Noble can directly access the hardware to bypass Windows’ Bluetooth stack. Not surprisingly, the chip on board my experimental laptop was not on the list. Searching on that error message, I found more information in this GitHub issue filed against Noble, which pointed to a Noble document explaining that support is limited to a fixed list of hardware. Quite unlike the typical recoverable JavaScript exception I’ve become spoiled by.
There are some native code components that were built for Noble support, and if things go sour in native code, it fails like native code, hence the jarring failure. Looking at the crash stack, the culprit appears to be Noble, the Node.js BLE module upon which the Node-RED extension was built. No compatible USB Bluetooth 4.0 device found! Getting node-red-contrib-noble-bluetooth set up and launching a flow was easy, but attempting to discover nearby BLE devices caused Node-RED itself to crash. So I wanted to see if BLE can be just as easy.
I’ve had success so far with Node-RED making hard things easy, most recently in reading battery power state in an old Windows 10 laptop. if I disable controller support again, the crashing behaviour reappears), so it seems very specific to this mouse and the controller support options.I’ve known Bluetooth Low Energy (BLE) to be a new technology that can still be challenging to interface with. Rocksmith should then load, even with the wireless dongle attached. Change the drop-down box option to 'Forced On' Navigate to Library and click on Rocksmith 2014 Open STEAM Big Picture mode (upper right of steam window has option) In any case, to fix the issue, here's what I did: I have no idea why, but this only happens when the mouse is connected via the RF dongle! The controller support settings have no effect when connected via BT or USB. For some reason, this is causing conflicts with Rocksmith when Controller Support is disabled (as it is by default on PC), which causes an instantaneous crash on load. I managed to solve the problem! The ROG Chakram mouse is unique in that it has a thumb-operated Joystick that can act as a classic analog joystick or a programmable digital joystick. Note that this occurred with a fresh install of Rocksmith and after several attempts to reinstall. Rocksmith did not crash if I used either a Razer Basilisk Ultimate w/ wireless USB dongle or a cheap Amazon Wireless MouseĤ.) Plugging in the ASUS Wireless RF dongle after Rocksmith starts does not appear to cause any further problemsĥ.) Plugging in a ASUS BT400 Bluetooth dongle did not trigger a crash.Ħ.) This crash did not occur on at least two other systems I tried That is, Rocksmith will crash even if the mouse is off or connected by USB)ģ.) it seems specific to ASUS Wireless RF Dongle. No loading screen or any assets will appear/ġ.) No minidump file is generated- it appears the crash happens immediatelyĢ.) it does not matter if you are actually connected via the Wireless RF Dongle, only that it is plugged in. However, if the wireless dongle is connected, Rocksmith 2014 will instantly crash from the white screen. The mouse works fine when connected via USB Cable or using Bluetooth. The mouse can connect in three ways: (1) USB cable, (2) Bluetooth, (3) Proprietery 2.4 Ghz Wireless RF USB Dongle. I recently purchased an ASUS ROG Chakram mouse. This is a partial follow up to a previous topic FYI: Rocksmith 2014 Remastered Crashes when (ASUS) Bluetooth USB Stick plugged, information for the Dev team to diagnose and maybe fix the problem (either for 2014 or in anticipation of Rocksmith+)