AutoActions
AutoActions copied to clipboard
Codectory
Won't Launch
Previously I had encountered the issue of it not starting at mentioned in #101 but now I can't get the exe to launch at all AutoActions.log .
I have a HDR TV and a monitor and I get the same error if the TV is not being used (powered on but no signal). If TV is set to either primary or secondary display, then the app launch fine.
I solved it by setting [Display] to [all displays] instead of [\.\DISPLAY2], which is my TV. Luckily my monitor isn't HDR capable so it works for my setup.
This is pretty much exactly my setup except my second monitor is fake HDR and looks awful so specifying the display is important.
Going to try a simple script to delay the launch of autoactions and see if that fixes it.
On 19 June 2022 10:32:55 pm LorKha @.***> wrote:
I have a HDR TV and a monitor and I get the same error if the TV is not being used (powered on but no signal). If TV is set to either primary or secondary display, then the app launch fine. I solved it by setting [Display] to [all displays] instead of [.\DISPLAY2], which is my TV. Luckily my monitor isn't HDR capable so it works for my setup. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Could you please send me the settings file?
xsilas43 @.***> schrieb am Mo. 20. Juni 2022 um 06:42:
This is pretty much exactly my setup except my second monitor is fake HDR and looks awful so specifying the display is important.
Going to try a simple script to delay the launch of autoactions and see if that fixes it.
On 19 June 2022 10:32:55 pm LorKha @.***> wrote:
I have a HDR TV and a monitor and I get the same error if the TV is not being used (powered on but no signal). If TV is set to either primary or secondary display, then the app launch fine. I solved it by setting [Display] to [all displays] instead of [.\DISPLAY2], which is my TV. Luckily my monitor isn't HDR capable so it works for my setup. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Codectory/AutoActions/issues/121#issuecomment-1159965195, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOWXFIOE75EWE7NSOVFDXC3VP7ZD5ANCNFSM5YZXF5KQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Good day gentlemen. I believe I have the same issue.
Scenario: Booting with 1 Display Active (PC Monitor). Later I switch to 2nd Display (HDR TV in another room) for gaming. I have profiles which set the 2nd Display to HDR depending on the game.
Behaviour: On boot with display 1 active, I see the splash screen, but the application immediately exits. If launched manually with only display 1 after boot, application also immediately exits. For testing purposes I booted with both displays active, then everything works as expected.
I was not able to find any log files of the failed startups, but if there are any that would help I would be happy to provide them.
