I only changed the one under as Im on a 64-bit OS, but I assume you'd need to change the block under on a 32-bit system. What I changed was the block under the line 'Oculus HMD as follows. There is a warning that these aren't signed drivers, but I just passed it as okay.
I was guessing somewhat, but when it was done, my Quest was now accessible via ADB. inf file and altered the hardware IDs to suit. What I did notice, though, was that the hardware IDs of the devices that wouldn't accept the drivers didnt actually match the hardware IDs listed in the. inf file, nor with installing devices 'separately' via Action>Add Legacy Hardware (this just added a new nonworking device). I didn't have any luck manually pointing the devices at the. Or at least I can now connect from ADB, and upload and delete packages on the Quest via ADB commands. Ive had the same problem, and appear to have a solution. inf file does not support this type of installation. inf on Install, the error message is displayed that the Named "Oculus adb Device" to appear in the hardware manager. Installing the drivers via "Add legacy hardware" only causes a non-bootable device Install the drivers by hand with Pnputil under dos: The tips and the dropbox adb auto install driver from this reddit: If I deactivate the developer mode, it says "quest" as unknown device, which Not find any drivers: ADB Interface and XRSP Interface In the device manager there are two devices for which Windows does Since the last update yesterday, these drivers can no longer be installed, notĮven by hand.
The original 2.0 drivers from Oculus could not be installed, but these here I already had problems installing the adb drivers for the Quest in June. Windows 10 installed, but it is a very clean system, which is only for gaming. Due to professional reasons I still work under Windows 7.
0 kommentar(er)
