[linux] [wayland] launching games in fullscreen causes black screen (have to go out and back into fullscreen for image to appear) #130

New Issue

Open

opened 2024-04-10 14:40:05 +02:00 by fx · 3 comments

fx commented

2024-04-10 14:40:05 +02:00

Is there an existing issue for this?

I have searched the existing issues

Affected Commit or Release

All current releases AFAIK.

Description of Issue

Within a wayland session, launch a game with these commandline flags: QT_QPA_PLATFORM=xcb ./suyu.AppImage -f -g "<pathToGame>" This will launch the desired game in fullscreen successfully, however using xwayland.

Instead, try the same thing with QT_QPA_PLATFORM=wayland ./suyu.AppImage -f -g "<pathToGame>". You'll notice the shader compilation goes fine, and once the game loads it will be on a black screen. This isn't a freeze however, and the game can be restored just by changing fullscreen state. So you can go out of fullscreen and back into fullscreen and the game will work fine.

This is an issue because when using a couch gamestream setup, I want to launch my game flawlessly without getting stuck on a black screen.

Expected Behavior

The game should launch fine in wayland mode without any need to go out and back into fullscreen.

Reproduction Steps

QT_QPA_PLATFORM=wayland ./suyu.AppImage -f -g "<pathToGame>". You'll notice the shader compilation goes fine, and once the game loads it will be on a black screen.

Log File

attached

System Configuration

CPU: Ryzen 5 5600x
GPU/Driver: Nvidia Geforce RTX 3070 - 550.67
RAM: 2x16gb 3800c18
OS: Arch Linux rolling

### Is there an existing issue for this? - [ ] I have searched the existing issues ### Affected Commit or Release All current releases AFAIK. ### Description of Issue Within a wayland session, launch a game with these commandline flags: `QT_QPA_PLATFORM=xcb ./suyu.AppImage -f -g "<pathToGame>"` This will launch the desired game in fullscreen successfully, however using xwayland. Instead, try the same thing with `QT_QPA_PLATFORM=wayland ./suyu.AppImage -f -g "<pathToGame>"`. You'll notice the shader compilation goes fine, and once the game loads it will be on a black screen. This isn't a freeze however, and the game can be restored just by changing fullscreen state. So you can go out of fullscreen and back into fullscreen and the game will work fine. This is an issue because when using a couch gamestream setup, I want to launch my game flawlessly without getting stuck on a black screen. ### Expected Behavior The game should launch fine in wayland mode without any need to go out and back into fullscreen. ### Reproduction Steps `QT_QPA_PLATFORM=wayland ./suyu.AppImage -f -g "<pathToGame>"`. You'll notice the shader compilation goes fine, and once the game loads it will be on a black screen. ### Log File attached ### System Configuration CPU: Ryzen 5 5600x GPU/Driver: Nvidia Geforce RTX 3070 - 550.67 RAM: 2x16gb 3800c18 OS: Arch Linux rolling

suyu_log.txt

337 KiB

fx added the

bug

label 2024-04-10 14:40:05 +02:00

Exverge self-assigned this 2024-04-10 21:06:41 +02:00

Exverge added this to the (deleted) project 2024-04-10 21:18:24 +02:00

Ryzendew commented

2024-04-10 23:47:25 +02:00

can confirm on both amd gpu's and nvidia

fx commented

2024-04-11 11:51:10 +02:00

Author

From what I can tell, building with qt6 instead of qt5 seems to solve this issue. For reference, I used this AUR package to do that. Anything stopping us from using qt6 by default in CI and release builds? I'd rather not have to compile the emulator for every commit.

From what I can tell, building with qt6 instead of qt5 seems to solve this issue. For reference, I used [this AUR package](https://aur.archlinux.org/packages/suyu-dev-qt6-git) to do that. Anything stopping us from using qt6 by default in CI and release builds? I'd rather not have to compile the emulator for every commit.

Exverge removed their assignment 2024-04-11 23:41:26 +02:00