..:: PCSX2 Forums ::..

Is there a way to further tweak the settings for mapping the mouse to an analog stick? I'm noticing a dead zone that is not affected by the dead zone setting for the analog. Also it doesn't feel like I have full 360 degree movement. Thanks.

When running with certain games and programs (JoystickCursorTool in particular), it seems to recognise my only controller input as joystick #2. There seems to be no way for me to influence the input of the 'first controller'. Any idea on why this might be? It's only a minor inconvenience that doesn't mess with any functionality, but it would be helpful to figure out!

see post #930

Unfortunately, all settings from 1-11 don't seem to fix this issue at all; my input is still read as controller #2 at all settings. To clarify, I'm only using one controller, and it's the only controller that's been connected, if that was unclear.

Okay, it was working a while ago, but now it's suddenly stopped working.
DS4 Windows appears to be functioning normally, the problem is rather the Driver. For some reason, The SCP Driver is simply not installing no matter what I do.
The Controller connects, i can change the lightbar colors, etc, but the fake "Xbox 360 Wireless Controller" does not appear in Input Devices, and the "Wireless Controller" that is there makes no inputs while DS4Windows is Turned on. It functions normally when Turned off.
Also, I am able to use Pinnacle Game Profiler to make the controller work as a 360 controller, without a fancy driver. (not at the same time of course though)

EDIT: Sorry, Windows 10 Forgot to Mention. Also the same when Bluetooth and wired

I'm not sure where else to ask this but when I installed DS4Windows, I dont remember getting a choice as to where to save profiles. It saved them to the %AppData% folder, but I would like to save them, along with all other files, to the folder with the .exe. Is that possible now? If so, what would I do- just move them? Would the program find them? I would like a complely portable setup. Thanks.

Windows 10 Anniversary Update (version 1607 build 14393) breaks exclusive mode again. Old workarounds don't work anymore. So there might be something new that's messing things up. Thanks Microsoft! Happy Anniversary!

ScpToolkit still works though. If you updated Windows 10 and need exclusive mode to work then use that for now.
https://github.com/nefarius/ScpToolkit
http://forums.pcsx2.net/Thread-ScpToolki...r-Reloaded

InputMapper dev has posted the issue to microsoft https://inputmapper.com/forum/inputmappe...issues#497.

Go here http://answers.microsoft.com/en-us/windo...0187583342. Click "Me Too". Let it be known!

Final Edit: Don't even bother Reading my wall of text. Just use the tool by jhebbel(inputmapper dev) below this post.

Okay, here's the workaround that works so far. It involves temporarily disabling and re-enabling "HID-compliant game controller" in the Device Manager.
-DELETED because too long.-

Update:
Semi-permanent fix for bluetooth only. Source of fix by user ZAMHome from InputMapper forums:
Video: https://inputmapper.com/20-windows-10-16...e-mode-fix
Original post in russian: https://inputmapper.com/forum/russian/10...0-redstone

1. Ensure that InputMapper / DS4Windows / SCP / DS4Tool are closed and not running at all.
2. Ensure the DS4 is OFF.
3. Open the device manager and look for Bluetooth HID Device.
4. Right click the device and select Disable.
5. After the list refreshes and the device is disabled, re-enable it.
6. Launch the application and connect DS4.

Wireless Bluetooth should work with exclusive mode and should keep working until next reboot.

Update2:
This is for wired USB. This needs to be done every time you plug-in.

1. Ensure that InputMapper / DS4Windows / SCP / DS4Tool are closed and not running at all.
2. Connect Controller with USB cable.
3. Open the device manager and look for "HID-compliant game controller" with this Hardware ID "HID\VID_054C&PID_05C4". This is the DS4.
4. Right click the device and select Disable
5. After the list refreshes and the device is disabled, re-enable it.
6. Launch the application.

I also found a quicker way to disable/enable devices with a batch file and devcon.exe which you can get from WDK https://developer.microsoft.com/en-us/wi...driver-kit. Alternatively easier to get is DevManView.exe http://www.nirsoft.net/utils/device_manager_view.html.

Disabling each specific device by finding the Hardware ID or Device Instance ID. Find it in the Details tab and Device Instance Path or Hardware IDs in the dropdown list.

Example:
Devcon

DevManView

Hardware ID should be the same for wired USB connection but Bluetooth might be different, not sure.

I have created a small EXE that automates this for you.
https://inputmapper.com/downloads/downlo...-mode-tool

Must be executed after each restart.
Requires elevation (automatically prompts for it).

A good way to make this hands off for now is to create it to be executed from a task (this allows for elevation without prompt so completely hands off), then create a batch file to execute the task then launch IM/DS4Windows/SCP. Then add that batch to windows startup if desired or just make a desktop shortcut and use it instead of your normal application shortcut.

This tool is generic so IM/DS4Windows/SCP users can all feel free to use it. Just be sure if you distribute it or do a writeup/video that you give credit where credit is due.

(08-03-2016, 04:45 PM)jhebbel Wrote: [ -> ]I have created a small EXE that automates this for you.
https://inputmapper.com/downloads/downlo...-mode-tool

Hey jhebbel, I just tested it. It doesn't seem to work with USB connection even though it says "Cycling USB Dualshock 4 Controllers". Bluetooth works fine.

Scratch that. I just rebooted and neither works using that tool. To test, I started with Bluetooth HID Device already disabled. Ran ExclusiveModeTool.exe and it didn't even re-enable the device. Seemed to be doing nothing.