Profile selection using auto profile rules
DS4Windows application supports several profiles with different mapping rules for keys and buttons, because not all games work the best using the same gamepad setup.
User can manually choose an active profile via DS4Windows settings screen, through command line interface or setting up an automatic linking between foreground processes and profiles.
Automatic profile switching is defined via Auto-Profile list in DS4Windows settings. The auto-profile setting can change a profile automatically when an active foreground process is changed (ie. a new application is launched). A match between a profile and process is defined using a process path and/or window title keywords (since V1.7.13 version).
Path = Process path (fex c:\apps\steam\eurotruck2.exe). Window title = The title of an active window (fex Calculator).
Search keyword supports wildchars:
ABC = Exact match of path or window title with a ABC keyword (path or window title name)
^ABC = Match ABC keyword at the beginning of path or title
ABC$ = Match ABC keyword at the end of the path or title
*ABC = Contains ABC keyword in a path or title
For example "notepad.exe$" path keyword would match with "C:\windows\notepad.exe" and "c:\windows\system32\notepad.exe" process names, but does not match with "c:\apps\notepad.exe.plusplus.exe".
Using both path and window title keywords at the same time allows to setup different profiles for Windows Store applications (before V1.7.13 version this was not possible). WinStore apps share the same c:\windows\system32\applicationFrameHost.exe process name, but have a different window title.
If this option is enabled in auto-profile settings screen then the "Logs" tab page of DS4Windows screens shows detailed debug messages about process and window title names and how those match an auto-profile rules. This is useful when a new process needs a special auto-profile rule, but the correct path or window title is not obvious. Enable this option only when you need to fine tune auto-profile rules, but keep it off in a normal usage of DS4Windows because it generates lots of debug messages.
By default the DS4Windows app reverts back to default profile when an unknown process is the active foreground process and none of the auto-profile rules match with the process or window title. Sometimes it may be useful to indicate DS4Windows that a profile should not be reverted back to default profile and just leave the currently active profile as is when certain process is running in foreground.
For example c:\windows\explorer.exe process is activated during task switching or when a desktop is an active. If the auto-profile rule doesn't choose any custom profiles and leaves all controllers in "(none)" profile option then this kind of auto-profile rule would not do anything (ie. the rule would not change a profile nor it would not revert back to default profile).
