![]() Not many people even understand what it does under the hood in WinOS kernel level. Anyway, the existing version of HidG is the best thing we have.Įver wondered why there are no other similar solutions like HidGuardian? What it does is veeeeeeeeeery complex thing to do, because of kernel driver API, blocking access to a device handle, etc. Even the original author of HidG (Nefarious) doesn't recommend to use this existing (old) version of HidG unless user is ready to take the risk and understands how it works. The author of HidGuardian has a new version of HidGuardian in a lab, so hopefully it resolves some of those issues with the current HidGuardian version. because upgrading will now break a lot of my setups on multiple devices now. I'm going to have to stick to this version of DS4 and just not upgrade. So even HIDGuardian will not work for me. I'm using older controller mixed with a v2 controller. Why does Edge of GeForce need exclusive access to the controller? Not for any reason I can think of. That is being caused by other programs that are NOT functioning correctly. But again, that is not something caused by DS4W. I agree, that the "Hide DS4" option causes issues because it's not easy to tell what programs are stealing exclusive access for absolutely no reason. ![]() You cannot say the same about HIDGuardian. If set up properly, "Hide DS4" works 100% of the time, completely flawlessly, regardless of hardware, and with a simple click of a button. You can't control what programs other people are using. We don't all have the money to upgrade all of our controllers. Unless HIDGuardian can hide the actual DS4 without affecting the Virtual DS4, then it is not "Flawless in all situations". My resistance is that I use DS4 v1 controllers. I would much rather see the feature still included, but be made aware that the feature is depreciated, no longer supported, and it may or may not work. The hidguardian solution would be fine if it were able to distinguish the DS4v1 from virtual. It really does work well when it does work. ![]() It's unfortunate that it's such a troublesome feature. I'm sure there are a plethora of games that this will effect. Such as Diner Bros, which accepts ds4 input, but needs remapped buttons (X and O turn into and X without remapping.). Exclusive mode was the only thing making some of these games behave correctly. It would be fine if I only used my v2 controller, but I've got 3 kids and we all sit down and play some of these games together. so I'm going to have to stay on the highest version with exclusive mode. This isn't in the current build, 2.1.15, correct? I've got 4 controllers and only 1 of them is a v2 controller. If you have a unsupported copy-cat feel free to reach us and kindly ask for it to be added to DS4Windows code while providing the maximum amount of information on it.I just finally got exclusive mode working correctly every time! Nooooo! I literally just uninstalled geforce experience 2 days ago. ![]() DS4W detects controller by their Vendor and Product Identification (VID/PID), meaning that if a controller’s VID/PID is not already on DS4W code then it will just be ignored.Īdding support to new copy-cats may be as easy as just adding their VID/PID to the code or as hard as making major changes to the internal structures of DS4Windows. For example, 8bitdo controllers that are compatible with Nitendo’s Switch usually present themselves as a replica of the Pro Controller and can be used as normal with DS4Windows.įor cases where the gamepad presents itself differently than the official one to the system (most DS4 replicas) then DS4Windows will not recognize them. If a gamepad is made to be a complete replica of a official one, meaning that they act exactly as the original controller and appear to Windows as such, then chances are DS4Windows will just detect it as being the official controller and it may just work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |