Class-D Personnel

The trail has gone hot again

@eqagunn said in BthPS3 controller won't stay connected:

My main problem persists. Controller won't stay connected.

That's not in issue with BthPS3, but most likely with Shibari. Some controllers apparently expect periodic data sent to them which Shibari doesn't do. I'll keep a possible solution/test in mind but for now I call it a day.

Cheers

@eqagunn said in BthPS3 controller won't stay connected:

You might want to try https://github.com/extesy/hoverzoom/
Will feel like a nusance in the beginning, but after a week or so you won't want to live without it.

Tried it, doesn't work

@eqagunn said in BthPS3 controller won't stay connected:

Hey man. I saw in other support topics you had some issues with Imgur. Sorry for that.

No need to apologize, I just don't like that an image sharing site loads everything but the image of interest in under 3 to 5 seconds, but ads and useless bloat like 5 megabytes of scripts and whatnot get shoved to the browser I'd much rather have you occupy a bit of storage on the forums server and it loads fast in return

@eqagunn said in BthPS3 controller won't stay connected:

Maybe worth noting that after installation Nefarius Bluetooth PS Enumerator had exclamation mark next to it in Device Manger saying it required a restart. Upon restart, the exclamation was gone and all looked okay in there except my Bluetooth driver was disabled and had to be manually re-enabled.
My Bluetooth device is an integrated Intel Wireless Bluetooth 7265. It connects fine to my Bluetooth speaker still. This is on a week old installation of windows with no prior traces of ScpToolkit.

Could you share screenshots of how it looks now in Device Manager, that exclamation mark has to be gone or nothing will work.

Cheers

@eqagunn said in BthPS3 controller won't stay connected:

I saw you said the development of additional features will depend on user interest. This driver is largely unknown to most of the people. Had trouble finding it myself based on a memory of stumbling upon your research notes topic a year ago. Google SEO or linking to it through top Google results would change this.

I get your point but this is where I could need serious help. I have no personal interest in coding, running the infrastructure, giving support and do marketing/SEO stuff. I understand its value but my plate is quite full already and I have little drive to become a salesman if you catch my drift There's limits to the madness. Forums, E-Mail and Discord is already enough, I don't have the capacity to go on all sorts of social media sites to advertise. The public projects I do for fun and learning and they already helped in getting in touch with interesting people, everything else is an extra

Edit: It's only out for a few months as well and I have kept the noise about it down deliberately until I declared it stable enough to face the public. It's a bunch of kernel drivers after all that can crash the system

I took the liberty and removed that garbage site imgur, you can directly paste images into posts here

setupapi.dev.log relevant snippet:

     sto:           {Stage Driver Package: c:\program files\nefarius software solutions\vigem bus driver\drivers\win10\vigembus.inf} 20:34:15.333
     inf:                {Query Configurability: c:\program files\nefarius software solutions\vigem bus driver\drivers\win10\vigembus.inf} 20:34:15.339
     inf:                     Driver package uses WDF.
     inf:                     Driver package 'vigembus.inf' is configurable.
     inf:                {Query Configurability: exit(0x00000000)} 20:34:15.343
     flq:                Copying 'c:\program files\nefarius software solutions\vigem bus driver\drivers\win10\x64\ViGEmBus.sys' to 'C:\WINDOWS\System32\DriverStore\Temp\{7c7efb0d-ebe7-2542-919b-357966378c7c}\x64\ViGEmBus.sys'.
     flq:                Copying 'c:\program files\nefarius software solutions\vigem bus driver\drivers\win10\x64\WdfCoInstaller01009.dll' to 'C:\WINDOWS\System32\DriverStore\Temp\{7c7efb0d-ebe7-2542-919b-357966378c7c}\x64\WdfCoInstaller01009.dll'.
     flq:                Copying 'c:\program files\nefarius software solutions\vigem bus driver\drivers\win10\ViGEmBus.cat' to 'C:\WINDOWS\System32\DriverStore\Temp\{7c7efb0d-ebe7-2542-919b-357966378c7c}\ViGEmBus.cat'.
     flq:                Copying 'c:\program files\nefarius software solutions\vigem bus driver\drivers\win10\vigembus.inf' to 'C:\WINDOWS\System32\DriverStore\Temp\{7c7efb0d-ebe7-2542-919b-357966378c7c}\vigembus.inf'.
     sto:                {DRIVERSTORE IMPORT VALIDATE} 20:34:15.413
     sig:                     {_VERIFY_FILE_SIGNATURE} 20:34:15.497
     sig:                          Key      = vigembus.inf
     sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{7c7efb0d-ebe7-2542-919b-357966378c7c}\vigembus.inf
     sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{7c7efb0d-ebe7-2542-919b-357966378c7c}\ViGEmBus.cat
!    sig:                          Verifying file against specific (valid) catalog failed.
     sig:                     {_VERIFY_FILE_SIGNATURE exit(0x800b010c)} 20:34:15.509
     sig:                     {_VERIFY_FILE_SIGNATURE} 20:34:15.510
     sig:                          Key      = vigembus.inf
     sig:                          FilePath = C:\WINDOWS\System32\DriverStore\Temp\{7c7efb0d-ebe7-2542-919b-357966378c7c}\vigembus.inf
     sig:                          Catalog  = C:\WINDOWS\System32\DriverStore\Temp\{7c7efb0d-ebe7-2542-919b-357966378c7c}\ViGEmBus.cat
!    sig:                          Verifying file against specific Authenticode(tm) catalog failed.
     sig:                     {_VERIFY_FILE_SIGNATURE exit(0x800b010c)} 20:34:15.522
!!!  sig:                     An unexpected error occurred while validating driver package. Catalog = ViGEmBus.cat, Error = 0x800B010C
!!!  sig:                     Driver package is considered unsigned, and Code Integrity is enforced.
!!!  sig:                     Driver package failed signature validation. Error = 0xE0000247
     sto:                {DRIVERSTORE IMPORT VALIDATE: exit(0xe0000247)} 20:34:15.525
!!!  sig:                Driver package failed signature verification. Error = 0xE0000247
!!!  sto:                Failed to import driver package into Driver Store. Error = 0xE0000247
     sto:           {Stage Driver Package: exit(0xe0000247)} 20:34:15.529

In conclusion: no clue. Signature verification fails for whatever reason

install.log

Relevant section:

Calling custom action ViGEm.Setup.CustomAction!ViGEm.Setup.CustomAction.CustomActions.InstallViGEmBusDevice
Begin InstallViGEmBusDevice (1.16.115.0)
Attempting to install driver C:\Program Files\Nefarius Software Solutions\ViGEm Bus Driver\drivers\Win10\ViGEmBus.inf
Devcon.UpdateDeviceDriver failed: System.ComponentModel.Win32Exception (0x80004005): Unknown error (0xe0000247)
End InstallViGEmBusDevice
CustomAction InstallViGEmBusDevice_x64 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 21:30:11: InstallExecute. Return value 3.

Hello! AirBender being there hints that you might have mixed Shibari versions....? Have you tried the latest one in a clean, empty folder?

What device in particular fails, could you provide some screenshots, version details, etc., basically as much information as possible, thanks.

Cheers