So after getting in a crashloop I manged to nuke my settings and now when I try to select DualSense to add my controller back I get the following message:
I already rebooted a few times.
#Unable to create virtual controller
32 messages · Page 1 of 1 (latest)
ah. My friend gave me his old DualSense, I googled up a bit, found DSX, bought it because the idea of wireless haptics sounded so sweet compared to my 10$ Game Sir Nova Lite xbox-pattern controller. Then I bought the Ugreen CM748(yes I installed the special drivers) because cough Gemini told me to and tried to set things up... It even worked before I managed to get my settings into a crashloop. Tho the sound was really quiet, came from a dozen games I was running at a same time, and the gamepad was just rumbling incoherently... Tried to initiate it in wired mode(ugh), and while the DualSense is now recognized as an audio device, the app still crashes with the same message I think.
i am kinda confused on what you mean 
Nothing works now, but it kinda semi-worked before.
And by before I mean like an hour before it stopped.
mm the rumbling incoherently sounds probably like you were in System Audio Capture mode, which will turn all of your computer's sounds into vibrations
the real golden egg will be haptics passthrough, but that's in closed beta for now. so you have to use the Virtual Dualsense - No Sound Device option. pretty soon it'll be available though!
But is it available in tethered mode, aka no BT, just cable?
only in Native Mode for now, which has limitations in terms of rebinding. there's a few things left to fix before haptics passthrough becomes part of the public beta. it's pretty close though
so yes if you're using dualsnse emulation, still has to be on No Sound Device
Ok, I'll wait then.

Also Gemini was telling me that w10 is more anal-retentive over audio stack compared to w11, any truth to that?
i'm not really sure. i bet reddit would know though! they know everything
Honestly I'd rather ask an AI. Reddit is a silly place.
Again it's not the same error, what apparently worked for that other user in #💬┃general is likely just a coincidence cause this one is a whole vPad error
Idk maybe but it seems like it is related to the audio device cuz switching off it seems to make it stop
It doesn't though
In #general it was some pebkac thing tbh
Here it's likely needing a proper reinstall but barely anything makes sense in what I'm reading
Okay ya
@mortal heron could you let us know if the error keeps happening? Might be there's something else going on and it would be helpful to know if so and what can be done about it
It was still happening last night, as of now I've reverted to stable branch and don't feel like experimenting. I just saw FH4 and 5 support and because I bought FH5 recently(and haven't touched FH4 in over a year) wanted to give it a try. The xbox rumble is... not entirely there for me
Is there still something to investigate here?
Please don't anal anything Windows at all 
mm i think nataniel doesn't wanna experiment with it to figure it out so ig for now there isn't, unless the initial screenshots are enough to learn anything
Well those are not making sense in this context so it is very confusing without a deeper investigation
I tried to get wireless haptics going, so I bought a dongle and switched to beta. It sorta worked, but then I got the app in bootloop, after which I reset my profile and now trying wireless haptics instead of it sorta working(just vibrating all the time and making choppy noises) it just throws that error. I guess you can close the support request because I don't feel like tinkering rn so I reverted to stable and not using the app for now.
OK so we can just assume it would be fixed anyway would you be on latest Beta and latest vpad driver so until then it is probably fine 
So better stay on stable before ruining your gaming evening 😛
Yeah I'm just using my xbox-like controller now, at least that one is plug and play :'D