Pokemon Sword crashing on linux

Yuzu Support
#1

My pokemon sword hangs after a few minutes of play and the characters are not displayed correctly with white lines on the body
[System]
OS: Manjaro Linux 20.2.1 Nibia
Arch: x86_64
Kernel: 5.10.15-1-MANJARO
Desktop: KDE
Display Server: x11

[CPU]
Vendor: GenuineIntel
Model: Intel® Core™ i3-3220 CPU @ 3.30GHz
Physical cores: 2
Logical cores: 4

[Memory]
RAM: 7.7 GB
Swap: 20.0 GB

[Graphics]
Vendor: AMD
OpenGL Renderer: Radeon RX550/550 Series (POLARIS12, DRM 3.40.0, 5.10.15-1-MANJARO, LLVM 11.0.1)
OpenGL Version: 4.6 (Compatibility Profile) Mesa 21.1.0-devel (git-d8236e32de)
OpenGL Core: 4.6 (Core Profile) Mesa 21.1.0-devel (git-d8236e32de)
OpenGL ES: OpenGL ES 3.2 Mesa 21.1.0-devel (git-d8236e32de)
Vulkan: Supported
yuzu_log.txt (858.9 KB)

#2

In order for us to provide better support, we need to see the log generated by Citra. This guide will walk you through how you can obtain the log file: How to Upload the Log File.

#3

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

#4

yuzu_log.txt (7.0 KB)

#5

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

#6

Your log get s cut short before starting the game. Make sure you didn’t re open yuzu before sending it.

#7

System Information for Support

Client Version                                yuzu Development Build master-mainline-636-4728-ga55b12001
Operating System                              Manjaro Linux
CPU                                                   Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz | AVX
RAM                                           7.73 GB
Pagefile / Swap                               15.00 GB
CPU Emulation Accuracy Level                  1
Graphics API                                  OpenGL ?
Graphics Renderer                             Radeon RX550/550 Series (POLARIS12, DRM 3.39.0, 5.9.16-1-MANJARO, LLVM 11.0.1)
Docked Mode                                   [x]
CPU Multicore                                 [x]
Async GPU                                     [x]
Assembly Shaders                              [ ]
Async Shaders                                 [x]
GPU Emulation Accuracy Level                  High

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

#8

yuzu_log.txt (858.9 KB)

#9

System Information for Support

Client Version                                yuzu Development Build master-mainline-636-4728-ga55b12001
Operating System                              Manjaro Linux
CPU                                                   Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz | AVX
RAM                                           7.73 GB
Pagefile / Swap                               15.00 GB
CPU Emulation Accuracy Level                  1
Graphics API                                  OpenGL ?
Graphics Renderer                             Radeon RX550/550 Series (POLARIS12, DRM 3.39.0, 5.9.16-1-MANJARO, LLVM 11.0.1)
Docked Mode                                   [x]
CPU Multicore                                 [x]
Async GPU                                     [x]
Assembly Shaders                              [ ]
Async Shaders                                 [x]
GPU Emulation Accuracy Level                  High

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

#10

The lines are a problem in OpenGL affecting AMD cards.
The crash is strange, did you press “Y” while playing?

#11

yes, I pressed
I replaced the driver table with the Mesa-Git I don’t know if that changes anything

#12

the game does not crash when I press y, but at any time during the emulation

#13

Is this manually built or are you using our appimage?

#14

I’m using this file
yuzu-linux-20210218-540014e83.tar.xz

#15

Try the appimage from here: https://yuzu-emu.org/downloads/

https://github.com/yuzu-emu/yuzu-mainline/releases/download/mainline-0-543/yuzu-20210218-540014e83.AppImage

#16

I already tried it with appimage, so I tried it with this file

#17

Any suggestion? I want to play

#18

Sorry, I can’t figure it out. Can you open an issue providing that log fie and explaining the problem? That way the devs take a direct look at it.

#19

OK, thanks for the help

1 Like