![]() ![]() Also it's extremely important to realise that this isn't the fault of games but the inherent fault of the emulation software. It's not an optional thing, it's absolutely required for normal operations. ![]() However said feature effectively makes it impossible to use any emulated controller in them since you'll have double input all the time, thus a solution that provides "exclusive" access is required. So them picking up multiple inputs is not a bug, it's a very intended and necessary feature for said games to function properly. All of them are different devices and therefore require said games to support multiple inputs at the same time. In racing games when you use a wheel, you also have pedals then as an extra gear stick, maybe handbrake as well and quite a lot of extra small things are possible to add as well. So let's start with the fact that multi input device support is a feature found most commonly in car games with wheel support and games with local multiplayer, aka split screen or hot seat. I've seen some very alarming thoughts posted here about this and decided that it warranted a post because the direction you're taking with this would effectively force me to move to Steam controller support, which I would absolutely hate to do so. Maybe there should be a better warning/disclaimer msg in DS4Windows app when the exclusive access fails to fight this documentation issue. Instead they just send a private message or post yet-another issue ticket asking the same thing discussed several times already. "Hide DS4 Controller" (=exclusive access to device handle in user-space app level, not in kernel API level) works well when it works, but many people don't even bother to read the warning message and the linked "exclusive access" Wiki doc page when it doesn't work. 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. I just finally got exclusive mode working correctly every time! Nooooo! I literally just uninstalled geforce experience 2 days ago. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |