(10-09-2016, 10:51 PM)Nefarius Wrote: That's not possible without some hacks ATM. How is that a problem? What do you mean "makes it not work". Do you experience doubled input or what exactly is the issue?
The Audio device is a side-effect from emulating an Xbox 360 Controller which doesn't work. It's an "issue" caused by Microsofts drivers so I'm not sure I can fix this somehow. I'm always open to suggestions though.
Dark Souls simply won't detect the controller so there's absolutely no inputs being received. It's been a Dark Souls 1-3 issue with Xinput wrappers for a long time. Wont detect inputs in the main menu. In game camera will keep spinning, only movement and camera control will work and other inputs don't register. Other games that support both Dinput and Xinput might just have double inputs of course.
So basically right now, DS4 support in these drivers (with Vigem) will make it not work properly in games that do have native support for DS4 Dinput like Far Cry 4, GTAV, and Rocket League. Screwed up bad ports like Dark Souls will not work at all. It makes it work for Xinput-Only games though.
For the audio, is it possible so that it doesn't make itself the default audio device? Some user's might wonder why their PC stopped playing any audio.
So whats the point of Fireshock drivers for DS4 when it already has native Dinput support in windows? For custom button mappings? I'm guessing you plan using hacks to make it a bit more usable with Vigem?
Looking at Vigem, it seems to have have a feature to use x360ce. From what I understand, it makes it so you don't have to drop XInput.dll in the game directory. So maybe if you bundled x360ce and have it pre-configured for each controller with standard xbox360 layout so it works out of the box. That would be a neat workaround I guess. (I just realized each controller has a unique GUID so this probably won't work)