Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash at launch if display enumeration changes #144

Open
OopyDoopy opened this issue Mar 30, 2023 · 2 comments
Open

Crash at launch if display enumeration changes #144

OopyDoopy opened this issue Mar 30, 2023 · 2 comments

Comments

@OopyDoopy
Copy link

The application refuses to start until all configuration information is deleted if display enumeration changes. This is a common occurrence if a computer is plugged into new screens often, and in some cases can be caused just by unplugging multiple monitors and plugging them back in.

I suppose I don't know 100% that it's specifically display enumeration causing it, but that's what it seems like, because the numbers associated with the display are the only thing that changes once I wipe the configuration and boot up the application again.

I'd imagine the easiest solution would be to error handle it and give the user a popup that display enumeration has changed and that they need to reconfigure the displays on their profiles. I'd also imagine that trying to automatically correct it would be...difficult/impossible, particularly for users that have multiple of the same screen, unless you can pull unique identifying information. But I digress, you know your software and what will work better than I do, just figured I'd share some thoughts lol.

And just to cover bases, this is with the latest version of the software as of this bug report.
Windows 11 build 22621.1413
Monitors plugged into an RTX 3080 running driver version 531.41

@MikiM0t0
Copy link

MikiM0t0 commented Aug 20, 2023

Release_x64.zip

Not a real fix, problem isn't easily solved and like the author of this program, I don't have the time right now.
Anyways I still wanted to share this version, it's more or less just skipping the errors and not handling them in any way. So it will start, don't throw errors, but obiously it won't work till the displays come back for which the profile was made.
In my setup I play mostly on my TV which isn't on all the time, so like you stated, autoactions won't start with windows. With this version it will start together with windows, then I turn my TV on before I wanna play (thus the displays are all back for the used profile) and autoactions works as intended when I start the game. Also updated .net version to 4.8.1

@tarvcode
Copy link

Confirm same issue. Some games I play on a TV (3rd monitor). Once I created a profile to deal with the TV display the program will not launch until the TV is connected.

I removed the TV profile and it resolves the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants