-
Notifications
You must be signed in to change notification settings - Fork 159
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
Engine: Windows freezes on Alt+Tab for a specific player #2486
Comments
|
If it's the issue that I had (on a Ryzen + NVidia Pc) you can use Windows key + Tab to bring the Desktop Switcher and move the hanged AGS to a new workspace/desktop and use the existing one as if nothing happened (to be able to investigate what happened). It would be nice to know the specific Windows 10 version and Nvidia driver. Here's my comment, from when I had, I remember I didn't had in 3.6.1, even though I had in 3.6.0, but eventually I upgraded my NVidia drivers and the issue disappeared even on 3.6.0. |
I want to add that I had a similar issue that I only managed to escape by virtue of having two monitors so I could alt-tab in and out, as well as using the mouse to attempt to restore focus (the game remained on top of primary monitor, and I don't think I had a cursor on that display). I can't be sure it's the same issue, since I was able to recover, but in case it's related, I'll list information below. It's also worth noting I alt-tabbed dozens of times and encountered the issue once, and I recall fumbling the keyboard command somehow when it happened. Fullscreen, not as borderless window Since I have similar problems (but all the time) with games like New Vegas, I'm curious if it would happen when set to OpenGL, but since I can't replicate it on demand, I'm not sure how I'd even test. |
Been chatting with the player, here's some answers:
does it happen virtually every time, in any moment of the game?
Drivers?
We've tried a number of combinations with the graphics and audio drivers, and it seems that it's most likelyrelated to d3d9. Software renderer did not crash, although it showed some strange behavior (like the game was responding to clicks even when it was not focused if the player clicked on a window in front of it...) |
And also:
So maybe some audio complexity in Rosewater that is overloading the engine in some cases? |
I suggest using "fullscreen as borderless window" by default. Direct3D definitely had issues with exclusive fullscreen in 3.6.0 (#1287). @ericoporto said it's fixed in 3.6.1, but the problem is that I cannot remember if anything was fixed in that regard in 3.6.1, so either any seemingly unrelated changed fixed it, or it became harder to reproduce by coincidence. |
Can confirm I can replicate in Rosewater in the wagon. Will download the 3.6.1 executable. Is there any way to enable some kind of verbose logging? |
Logging config is explained here: Is there a save I could use to check the same location, or alternatively a walkthrough? |
Thank you. I downloaded 3.6.1P4, put ac.exe in the directory, and ran it. Issue occurred. Will supply a save shortly. Will set up logging presently. |
File should be for 3.6.0, loading then alt+tabbing between around 8 and 12 times should trigger crash. |
Log is extensive. I think I grabbed the pertinent section, but I don't think it tells us anything:
I am currently at the debug verbosity. Will see if verbose provides any new information. ~~As an aside, is polling the prefs.rsw constantly (~1,000 times per minute) AGS behavior or Rosewater behavior?~~ Rosewater specific behavior Edit: The Direct3d device being lost is the only real information I can gather here. I hope it's helpful for someone with better knowledge of AGS. |
Also, I cannot replicate the issue with OpenGL. Combined with the Direct3D device being lost error, it's likely within D3D specific routines. Again, not a surprise, but hopefully helpful. |
I can't reproduce it anymore since I upgraded the Nvidia drivers but when I had the conditions required were
I think the game resolution and the monitor resolution also can't match (but I wasn't able to test this before the problem went away). If you can reproduce this and this somehow solves it for you, we could make so that exclusive fullscreen uses the same resolution as the desktop was on Windows, and then resize the game through some other way. Since 3.6.1 there's an additional setting to remove the Fullscreen configuration so one can set and lock the game to use only borderless window Fullscreen. Also it would be better to get a log for 3.6.1 since the code has diverged from 3.6.0 a certain amount.
That's a very old driver. I think if you upgrade the problem will disappear. |
The opengl driver can only do borderless, regardless of settings. Anyway, yeah, always make borderless the default. |
Good to know, thanks! |
So, to summarize, this is likely a reiteration of #1287. Back then I was not able to find what causes the problem nor have any idea how to fix this in the program (or whether this may be fixed in program), nor I do now. If this may be fixed by updating NVidia driver, I'd propose user to try that, unless it's already the latest version. In the long term, implementing a new graphic renderer based on contemporary version of DirectX is going to be beneficial, and may solve existing issues with Direct3D renderer. |
Right, I haven't tried to reproduce this in the "wagon" scene in Rosewater yet. I will try, but not sure if that will improve my understanding of a problem. |
Describe the bug
A player reported an issue where when they alt+tab, the game completely freezes, including Windows:
AGS Version
AGS 3.6.0.57
Game
Rosewater beta (1280x720px, game speed 60)
To Reproduce
Expected behavior
Windows doesn't freeze up.
Screenshots
User's game setup:
Desktop (please complete the following information):
Additional context
Player is using a custom-built PC with the following specs. Player also reported that it has not happened with any other AGS game.
The text was updated successfully, but these errors were encountered: