Citra Nightly/Canary stuck as a fullscreen window when windowed


#1

Issue:
The problem here is that the Citra game select screen is stuck as a full screen window with no window controls when it’s supposed to be windowed. Pressing F11 to enter/exit full screen does nothing in the game select menu, but exiting full screen in game causes the window to resize to its normal, glitch out, then return to a full screened window with no access to the close, maximize, and minimize buttons.

System Information

  • Operating System: Windows 10
  • CPU: Intel i7-8750 @ 2.20 GHz
  • GPU: NVIDIA GeForce GTX 1050 Ti
  • Citra Version (found in title bar): Nightly #966, Canary #842
  • Game: Fire Emblem Fates Special Edition (w/ DLC,
  • Screenshot of Issue (title bar not applicable):

Main Menu:

“Windowed” mode:

Full screen mode:

Diagnostic Log
citra_log.txt (29.1 KB) (Nightly)

citra_log.txt (46.4 KB) (Canary)


#2

I did not find anything wrong in your log file. Please wait for a moderator to assist.


#3

I did not find anything wrong in your log file. Please wait for a moderator to assist.


#4

This is a very old bug. Are you on the latest Citra version? If so, try deleting your qt-config.ini file.


#5

Deleting the config file seems to have fixed the issue. Thanks!


#6

Double post, but it seems like if I press F5 to restart the game while the game is in fullscreen, this issue occurs.


#7

I’ll look into it if I can.


#8

Not to bump an old thread from nearly three months ago, but I’m just writing to confirm this also happened to me. I’m new to using Citra, so I was fumbling around looking for both the hot key for screen swapping AND full screen, so I ended up hitting F5 and I got stuck in this full screen mode.

Doing a diffcheck on qt-config.ini before and after the error, I believe these are the values that gets stuck:

UILayout\[email protected](\x1\xd9\xd0\xcb\0\x2\0\0\0\0\0\0\0\0\0\0\0\0\x6?\0\0\x3\x83\0\0\x1\v\0\0\0\xcb\0\0\x5\x34\0\0\x2\xdb\0\0\0\0\0\x4\0\0\[email protected])
UILayout\[email protected](\0\0\0\xff\0\0\0\0\xfd\0\0\0\x2\0\0\0\0\0\0\0\0\0\0\0\0\xfc\x2\0\0\0\x1\xfb\0\0\0\x1c\0W\0\x61\0i\0t\0T\0r\0\x65\0\x65\0W\0i\0\x64\0g\0\x65\0t\0\0\0\0\0\xff\xff\xff\xff\0\0\0]\0\xff\xff\xff\0\0\0\x1\0\0\0\0\0\0\0\0\xfc\x2\0\0\0\a\xfb\0\0\0\x18\0\x41\0R\0M\0R\0\x65\0g\0i\0s\0t\0\x65\0r\0s\0\0\0\0\0\xff\xff\xff\xff\0\0\0o\0\xff\xff\xff\xfb\0\0\0 \0G\0r\0\x61\0p\0h\0i\0\x63\0s\0\x44\0\x65\0\x62\0u\0g\0g\0\x65\0r\0\0\0\0\0\xff\xff\xff\xff\0\0\0_\0\xff\xff\xff\xfb\0\0\0"\0P\0i\0\x63\0\x61\0 \0\x43\0o\0m\0m\0\x61\0n\0\x64\0 \0L\0i\0s\0t\0\0\0\0\0\xff\xff\xff\xff\0\0\0\x8c\0\xff\xff\xff\xfb\0\0\0*\0P\0i\0\x63\0\x61\0\x42\0r\0\x65\0\x61\0k\0P\0o\0i\0n\0t\0s\0W\0i\0\x64\0g\0\x65\0t\0\0\0\0\0\xff\xff\xff\xff\0\0\0\x8c\0\xff\xff\xff\xfb\0\0\0 \0P\0i\0\x63\0\x61\0V\0\x65\0r\0t\0\x65\0x\0S\0h\0\x61\0\x64\0\x65\0r\0\0\0\0\0\xff\xff\xff\xff\0\0\x1\x98\0\xff\xff\xff\xfb\0\0\0\x12\0\x43\0i\0T\0r\0\x61\0\x63\0i\0n\0g\0\0\0\0\0\xff\xff\xff\xff\0\0\0?\0\xff\xff\xff\xfb\0\0\0.\0L\0L\0\x45\0S\0\x65\0r\0v\0i\0\x63\0\x65\0M\0o\0\x64\0u\0l\0\x65\0s\0W\0i\0\x64\0g\0\x65\0t\0\0\0\0\0\xff\xff\xff\xff\0\0\0]\0\xff\xff\xff\0\0\[email protected]\0\0\x3S\0\0\0\x4\0\0\0\x4\0\0\0\b\0\0\0\b\xfc\0\0\0\0)
UILayout\[email protected](\x1\xd9\xd0\xcb\0\x2\0\0\xff\xff\xff\xf0\xff\xff\xff\xe1\0\0\x1\x8f\0\0\x1\xe7\xff\xff\xff\xf8\0\0\0\0\0\0\x1\x87\0\0\x1\xdf\0\0\0\0\0\0\0\0\[email protected])
UILayout\[email protected](\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\x5\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x4\xa8\0\0\0\x5\x1\x1\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x5\0\0\x2~\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\xfe\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\0\0\0\x64)
UILayout\[email protected](\x1\xd9\xd0\xcb\0\x2\0\0\0\0\0\0\0\0\0\0\0\0\x3\xe7\0\0\x2W\0\0\0\0\0\0\0\0\0\0\x3\xe7\0\0\x2W\0\0\0\0\0\0\0\0\[email protected])

When you delete qt-config.ini and start a fresh one, all of that gets reset to:

UILayout\[email protected](\x1\xd9\xd0\xcb\0\x2\0\0\0\0\x1\x2\0\0\[email protected]\0\0\x5$\0\0\x2\xa3\0\0\x1\n\0\0\0_\0\0\x5\x1c\0\0\x2\x9b\0\0\0\0\0\0\0\0\[email protected])
UILayout\[email protected]()
UILayout\[email protected]()
UILayout\[email protected]()
UILayout\[email protected]()

I don’t know if this is relevant, but it does make it a little easier to fix on the user end if you don’t feel like deleting your entire config file – just delete those five variables and the junk data they generate from the ini.

If I had to guess, hitting F5 to reset the game grabs the fullscreen window size somewhere and uses that for everything, even when the application isn’t full screen. But I probably shouldn’t backseat code.


#9

Deleting the variables is a known workaround, but not recommended for the typical user as they can delete the wrong variables. Deleting the entire file resets all settings, so no harm done.

I haven’t yet found the time to look into this issue. I’ll try my best though.