Does 0 A.D. support Wayland?

[yushun]

Hello everyone, after I switched the GNOME desktop to Wayland, 0 A.D. can no longer start properly:  the interface doesn't load, but there is sound.

  Does anyone know what's going on? Everything was OK, when using Xorg.

 The IS is fedora40, Display interface: Nvidia GTX1660SUPPER.

 Appreciate any help.

 

 

 

[Stan`]

According to this https://code.wildfiregames.com/rP26929 which was included in Alpha 26 we should support it. If you run the game through the terminal does any log appear ?

[Norse_Harold]

Apparently Wayland isn't the default video output driver used by SDL2. It may be necessary to tell SDL to use Wayland instead of X11 with the following command on the Terminal. Or, it may be necessary to tell it to use X11 if you happen to have a version of SDL that defaults to using Wayland (version 2.0.22) and bugs in your graphics drivers, etc. cause issues with Wayland.

SDL_VIDEODRIVER=wayland /path/to/0ad

The post here has links with more information.

Edited August 15 by Norse_Harold

[yushun]

On 09/08/2024 at 11:32 PM, Stan` said:

According to this https://code.wildfiregames.com/rP26929 which was included in Alpha 26 we should support it. If you run the game through the terminal does any log appear ?

 

On 15/08/2024 at 12:32 PM, Norse_Harold said:

Apparently Wayland isn't the default video output driver used by SDL2. It may be necessary to tell SDL to use Wayland instead of X11 with the following command on the Terminal. Or, it may be necessary to tell it to use X11 if you happen to have a version of SDL that defaults to using Wayland (version 2.0.22) and bugs in your graphics drivers, etc. cause issues with Wayland.

SDL_VIDEODRIVER=wayland /path/to/0ad

The post here has links with more information.

Thank you for your reply. I tried to start 0ad by adding the SDL_DEVEODRIVE variable, but it still doesn't seem to have changed as before. Below is the startup log：

yushun@MiWiFi-RD03-srv:~$ SDL_VIDEODRIVER=wayland /usr/bin/0ad
TIMER| InitVfs: 359.264 us
FILES| Main log written to '/home/yushun/.config/0ad/logs/mainlog.html'
FILES| Interesting log written to '/home/yushun/.config/0ad/logs/interestinglog.html'
TIMER| CONFIG_Init: 4.18419 ms
Sound: AlcInit success, using OpenAL Soft
FILES| UserReport written to '/home/yushun/.config/0ad/logs/userreport_hwdetect.txt'
TIMER| RunHardwareDetection: 2.74501 ms
FILES| Hardware details written to '/home/yushun/.config/0ad/logs/system_info.txt'
TIMER| write_sys_info: 16.2195 ms
TIMER| InitRenderer: 2.70123 ms
TIMER| ps_console: 11.3407 ms
TIMER| ps_lang_hotkeys: 1.25768 ms
TIMER| common/modern/setup.xml: 121.536 us
TIMER| common/modern/styles.xml: 87.064 us
TIMER| common/modern/sprites.xml: 789.562 us
TIMER| common/global.xml: 235.866 us
TIMER| common/setup.xml: 134.072 us
TIMER| common/sprites.xml: 262.626 us
TIMER| common/styles.xml: 39.994 us
TIMER| pregame/backgrounds/: 88.39 us
TIMER| pregame/sprites.xml: 79.002 us
TIMER| pregame/styles.xml: 13.495 us
TIMER| pregame/mainmenu.xml: 17.082 ms

I noticed that in the userreportaw_wdetect.txt log, the sdl backend is already Wayland.

Thank you again for your reply，and @Stan`, Thank you.

mainlog.html system_info.txt userreport_hwdetect.txt

[yushun]

17 minutes ago, yushun said:

 

Thank you for your reply. I tried to start 0ad by adding the SDL_DEVEODRIVE variable, but it still doesn't seem to have changed as before. Below is the startup log：

yushun@MiWiFi-RD03-srv:~$ SDL_VIDEODRIVER=wayland /usr/bin/0ad
TIMER| InitVfs: 359.264 us
FILES| Main log written to '/home/yushun/.config/0ad/logs/mainlog.html'
FILES| Interesting log written to '/home/yushun/.config/0ad/logs/interestinglog.html'
TIMER| CONFIG_Init: 4.18419 ms
Sound: AlcInit success, using OpenAL Soft
FILES| UserReport written to '/home/yushun/.config/0ad/logs/userreport_hwdetect.txt'
TIMER| RunHardwareDetection: 2.74501 ms
FILES| Hardware details written to '/home/yushun/.config/0ad/logs/system_info.txt'
TIMER| write_sys_info: 16.2195 ms
TIMER| InitRenderer: 2.70123 ms
TIMER| ps_console: 11.3407 ms
TIMER| ps_lang_hotkeys: 1.25768 ms
TIMER| common/modern/setup.xml: 121.536 us
TIMER| common/modern/styles.xml: 87.064 us
TIMER| common/modern/sprites.xml: 789.562 us
TIMER| common/global.xml: 235.866 us
TIMER| common/setup.xml: 134.072 us
TIMER| common/sprites.xml: 262.626 us
TIMER| common/styles.xml: 39.994 us
TIMER| pregame/backgrounds/: 88.39 us
TIMER| pregame/sprites.xml: 79.002 us
TIMER| pregame/styles.xml: 13.495 us
TIMER| pregame/mainmenu.xml: 17.082 ms

I noticed that in the userreportaw_wdetect.txt log, the sdl backend is already Wayland.

Thank you again for your reply，and @Stan`, Thank you.

mainlog.html 28.49 kB · 0 downloads system_info.txt 10.6 kB · 0 downloads userreport_hwdetect.txt 14.12 kB · 0 downloads

 

[Norse_Harold]

Thanks for posting the screenshot and answering questions and trying some troubleshooting steps on IRC today.

My next idea involves changing the version of the nVidia proprietary drivers. This bug report mentions that egl-wayland provided by nVidia may be buggy (especially note bug 119), and when users change to an older or newer version of the nVidia proprietary driver suite then they fix similar issues.

For more ideas, see the discussions in bug reports posted about Fedora's package of Wayland. Also, come back to IRC for followup troubleshooting advice.