AutoActions
AutoActions copied to clipboard
Codectory
UWP Apps that use Launchers do not work
Describe the bug There are quite a few apps that use launcher apps as an intermediary before launching the actual executable. For non-UWP apps, you can often get around this by finding the actual/specific executable that gets launched. However this poses a real problem for UWP applications, as you can't target the actual executable.
Some example apps:
To Reproduce
- Add one of the aforementioned apps
- Select the HDR profile
- Start the app
- HDR will be enabled when the launcher app starts, then disabled again when the true app starts
Expected behavior Honestly, this is kind of expected - as it's doing exactly as it should. Launching in HDR for that app (just the launcher) then turning HDR off. The desired behaviour is for HDR to work for the actual game executable, not the launcher.
Desktop (please complete the following information):
- OS: Windows 11 21H2
- Version: 22000.593
Hardware (please complete the following information):
- Monitors: Alienware AW3423DW
- Graphics card: Gigabyte 3080 Gaming OC
- Graphics card driver: 512.15
Additional context Potential suggested solution - add a third App selection option (aside from "Choose application"/"Choose UWP app...") called something like "Choose open process" that would allow the user to capture the window process name to allow AutoActions to execute for these troublesome processes.
