Changing the resolution in fullscreen mode causes eduke32 to be turned into a background process on Windows

Doom64hunter

#1 Posted 19 September 2019 - 03:04 AM

When in fullscreen mode, switching resolution two times in a row turns the game into a background process.
Notably this also happens anytime someone attempts to switch viewmode from 2D to 3D in mapster32 while in fullscreen mode.

This only happens on Windows, I could not reproduce the same problem on Debian 10. Probably some kind of problem with SDL.

It appears that this was broken in commit r8063 "Support fullscreening to the correct display in multiple monitor configurations"

This post has been edited by Doom64hunter: 19 September 2019 - 03:07 AM

Doom64hunter

#2 Posted 29 September 2019 - 09:05 AM

It also happens when you press ALT+Enter, and furthermore it also happens in Ion Fury.

One person playing the AMC TC ended up being unable to launch the game in the foreground again after this occurrence, running on Windows 7.
It's as if it somehow remembered that it was a background process last time it was run, and it just restores it as that.

Paul B

#3 Posted 01 October 2019 - 10:46 PM

I will chime in because I use to have this exact same problem. The devs blamed my hardware as the problem or a bad driver. However, I knew it wasn't that. Eventually, someone figured out the problem and silently fixed it as I haven't had it happen in ages but now I haven't been updating Eduke either. It's like when IF came on the scene they forked the code re- introducing all these bugs they had fixed over a 7 year period. I don't know why, maybe for the sake of optimizations. But this has been a major set back. No idea how long it will take them to reach the point where they were a couple years back. I kinda think this change has been in the works for a while now and they just bit the bullet for IF performance, Eduke32 was kind of an after thought. I think they just need to revise their previous commits to adapt to their new way of doing things. If memory serves me correctly rather than play the game in full screen mode try playing it in window mode. That worked for me. Until they can revisit the fix. I use multiple monitors too. (Very interesting). I think you are onto something with dual display in full screen mode.

This post has been edited by Paul B: 01 October 2019 - 11:03 PM

Tea Monster

Polymancer

#4 Posted 02 October 2019 - 08:07 AM

Doom64hunter

#5 Posted 23 December 2019 - 10:18 AM

Still happens in r8494. Though I realize that this problem appears to be highly dependent on system configuration.

One other person on Civvie's server tested this for me a while back, and it didn't happen for them.
He had a multi-monitor configuration, while I have only a single monitor -- this may be the source of the problem, judging from the commit that introduced it. Not completely confident however.