You pass the controller object to your scope. That has little to do with the actual SDK but is more like a beginners question for C# in general. Nothing about the SDK is ViGEm-specific, if you're familiar with C# it should be fairly self-explanatory.

Cheers

Update 2:
After a lot of unsinstall, reinstall, registry cleaning and so on not it looks like it's working again 🙂

C.

@darkhyperlink said in So lost with getting this to work:

I installed the dshidmini and it does recognize my ds3 in the dshmc settings window

Send a screenshot here of the DSHMC window.

Also, send a screenshot of DS4Windows.

Nope, Nav Support partially works but since it's incomplete and I don't like getting support requests for clearly unfinished components I left it disabled in the INF until I find time to finish it. There's also an issue in the issue tracker regarding Nav progress.

Cheers

@nefarius Yes, I've already tried to help myself by going through your old clean up docs, and I think my system is clean, but please, see below, I might have missed something.

Note: I've also tried to remove the high and low filters for the CSR device PID, but nothing was in Regedit, and also something within the classes, https://doublerock.blogspot.com/2016/08/windows-7-cambridge-silicon-radio.html
, but, it didn't change the base issue.

RDP

New1.PNG

new2.PNG

.

As I said, sounds like a networking issue you need to diagnose and address since I can not possibly know your network architecture. Maybe you need a VPN into your home network, how else would the packets get from your PC/Console to your phone and vice versa?

Cheers

I'm assuming you are talking about ViGEmBus. It's mentioned big and fat that ARM (which is the processor architecture of M1) is not supported.

Everything you need to know and do is in the same article in the troubleshooting section. Read, don't scream help, works better 😉

It means that you don't have working Bluetooth. Check in Device Manager if your Bluetooth radio shows up there and is healthy.

Cheers

Shibari is no more, use DsHidMini.

Can confirm it also happens with DS4Windows Mode.

@kirian
i uninstaled bthps3/fireshock/vigembus and shibari

then install bthds3 and dshidmini v2 and my fake gamepad is not working via usb and bluetooth.

dshihmini.jpg

i want to connect via bluetooth

@engineer25 Shibari is obsolete, so we don't give support to it anymore.

If you are on Windows 10 or above then move over to DsHidMini. It's not as straight-forward to setup but if you managed to install shibari you'll be able to install DsHidMini.

Remember that:

You'll need to fully remove Shibari and its drivers so it doesn't conflict with DsHidMini Make sure you are using both DsHidMini v2 and BthPs3 v2 if using DsHidMini v1 and BthPs3 v2 it won't work. Same if the opposite is true To achieve Xbox emulation, you'll either need to: Use DsHidMini's XInput Mode + Steam Use DsHidMini's DS4Windows mode + Ryochan7's DS4Windows

Links:

Installing DsHidMini + Uninstalling Shibari and related drivers DsHidMini Frequently Asked Questions Might be slightly wrong since it was created before XInput Mode was implemented DsHidMini's XInput mode guide Under construction DsHidMini's DS4Windows Mode Guide

What are we supposed to see?

Follow this.

Cheers

Nice, no information provided whatsoever, my psychic powers tell me it's... ducks.

That unfortunately tells nothing. I can't really tell you what's going wrong here.

Okay, I have sorted it out. I followed the steps described here:

https://windowsreport.com/ps4-controller-exclusive-mode/

Also I have added DS4Windows to the exceptions-list in the Windows-Firewall under Firewall and Network-Protection.

This has made the "Hide DS4 Controller" Option viable.
The HidHide Configuration Client still gives me the error mentioning "Something unforseen..." but since it's working now I don't really mind.

I don't know that game. Have you tried DS4Windows mode, which basically emulates a perfect X360 controller?

You already posted the same thing on GitHub and I responded, no need for spam.