Gamescope doesn't work with Final Fantasy XIV

[Sojiro84]

I am using it with Lutris. I tried both the official launcher and the third party launcher.

I used: gamescope -w 3200 -h 1800 -W 2432 -H 1368 -b -- gamescope -w 3200 -h 1800 -W 2432 -H 1368 -- gamescope -w 3200 -h 1800 --

But all I get is a small pop-up and then nothing.

Which is a shame since FFXIV has zero anti-aliasing so running it at 4K or higher and then downscaling would make the game look so much better.

These are the last lines from the console:

parsing config: /home/sojiro/.config/MangoHud/MangoHud.conf [ ok ]
warn:  D3D9: VK_FORMAT_D24_UNORM_S8_UINT -> VK_FORMAT_D32_SFLOAT_S8_UINT
info:  AMD RADV NAVI10 (ACO):
info:    Driver: 21.1.5
info:    Vulkan: 1.2.168
info:    Memory Heap[0]: 
info:      Size: 7936 MiB
info:      Flags: 0x1
info:      Memory Type[0]: Property Flags = 0x1
info:      Memory Type[4]: Property Flags = 0xc1
info:    Memory Heap[1]: 
info:      Size: 8176 MiB
info:      Flags: 0x0
info:      Memory Type[1]: Property Flags = 0x6
info:      Memory Type[3]: Property Flags = 0xe
info:      Memory Type[5]: Property Flags = 0xc6
info:      Memory Type[7]: Property Flags = 0xce
info:    Memory Heap[2]: 
info:      Size: 256 MiB
info:      Flags: 0x1
info:      Memory Type[2]: Property Flags = 0x7
info:      Memory Type[6]: Property Flags = 0xc7
info:  Process set as DPI aware
info:  Adapter LUID 0: 0:3f5
00:00:01.723 [DEBUG] [types/wlr_surface.c:723] New wlr_surface 0x55c97162fbe0 (res 0x55c97160cc40)
00:00:01.847 [DEBUG] [../gamescope-3.8.4/src/wlserver.cpp:76] Received kill signal. Terminating!
(EE) failed to read Wayland events: Broken pipe
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
X11 I/O error
terminate called without an active exception
Monitored process exited.
Initial process has exited (return code: 134)
All monitored processes have exited.
Exit with returncode 134
2021-07-23 10:27:24,827: Game still running (state: running)
2021-07-23 10:27:24,827: Stopping Final Fantasy XIV Online - XIVLauncher (wine)

[emersion]

Hm. Is gamescope crashing by any chance? Can you try coredumpctl gdb then bt full after a crash?

[Sojiro84]

Sure, here is the data: https://gist.github.com/Sojiro84/815e6481d1ef3f2180138b3909902411

[emersion]

Hmmmmm. It seems like something in MangoHUD is calling XCloseDisplay, which then fails, then tries to unwind the stack, then hard crashes...

[emersion]

Can you try without MangoHUD?

[Sojiro84]

I did it without mangohud, still crashed, then also removed vkbasalt, still a crash, here is the log off that: https://gist.github.com/Sojiro84/b9a94b7d3c18c14641110a4131c087e3

[emersion]

That crash still originates from libMangoHud.so. Are you sure it's properly disabled? Maybe it's still in LD_PRELOAD or something. (Note, I'm not familiar with mangoHUD,)

[Sojiro84]

Weird, I have it disabled, I wonder why it still pops-up.

[Sojiro84]

I also tried renaming the libMangoHud.so but that also didn't work, but maybe that needs a restart of the PC.

What is this LD_PRELOAD you mentioned? Tried googling the term but couldn't find anything useful to my use case.

[emersion]

It's an environment variable used to force the load of a dynamic library. If it's set, this could be one of the possible reasons why MangoHUD gets loaded.

[Sojiro84]

I am running Wayland, but I still do have a .profile with:

export ENABLE_VKBASALT=1
export MANGOHUD=1
export RADV_TEX_ANISO=16
export AMD_TEX_ANISO=16

But I have gathered Wayland doesn't read that file (but Lutris still might off course).

Edit: I have removed them and will report back after a reboot.

[Sojiro84]

Alas, still no luck with the .profile changed: https://gist.github.com/Sojiro84/c3d6c550ac1933e2356cc015d570ee99

[Sojiro84]

And here with mangohud removed: https://gist.github.com/Sojiro84/2e1fa78c3ae5d209bcd6adb5ed6e20e7

Somehow mangohud still keeps popping up.

[exeqtion]

Hi, I am using steam version of ffxiv and with gamescope -H 1080 -f -- gamemoderun mangohud %command% launch commands, and it works without any issue.

[Sojiro84]

Hi, I am using steam version of ffxiv and with gamescope -H 1080 -f -- gamemoderun mangohud %command% launch commands, and it works without any issue.

Probably because you haven't set MANGOHUD=1 in the steam launch parameter as well.

I just bought the Steam version as well since with the Proton-GE (https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.13-GE-1) that has a easy FFXIV standalone client fix, I can now use gamescope. I don't have Mangohud in the launch options.

[massatt212]

i have the same problem, i had to use LD_PRELOAD="" gamescope -U -- %command%

[yaomtc]

The latest gamescope (installed on Arch via gamescope-git in AUR) works great for me, aside from one thing: the game can't tell when its window is inactive, so disabling the "play sounds when window is not active" option does nothing. Is this just a consequence of "running in its own personal Xwayland sandbox desktop"?