open [13119] Pokemon Sword/Shield random input hangs #13119

Open
opened 2026-01-02 20:43:12 -03:00 by Accord · 0 comments
Owner

Branch: __refs_pull_13119_head

alessiot89 opened issue at 2024-02-22 14:24:

Is there an existing issue for this?

  • I have searched the existing issues

Affected Build(s)

Mainline 1722

Description of Issue

Randomly playing Pokemon Sword/Shield the game hangs but the audio (the music) continues to play. Most of time the issue is temporary fixed toggling fullscreen/windowed with F11. However, sometimes toggling between windowed and fullscreen mode doesn't fix and the game completely freezes. This happens both in windowed mode and in fullscreen mode.

Expected Behavior

No hangs should occurs.

Reproduction Steps

There is no specific way to reproduce it sadly, it happens randomly playing the game.

Log File

yuzu_log.txt

System Configuration

CPU: Ryzen 5 3600X
GPU/Driver: RX 67000 XT driver "AMD Software: Adrenalin Edition 24.2.1 for HELLDIVERS™ 2" version 23.40.19.01
RAM: 32GB DDR4 @3600
OS: Windows 10 22H2 build 19045.3930
Controller: XBOX Series X/S controller, last firmware updated (the issue happens with both bluettoth and usb mode)

alessiot89 commented at 2024-02-23 22:42:

I think all this is related about controller polling rate, especially with BT devices... I noted when this happens than after few seconds the controller goes in idle and stops to responds to yuzu (the debug controller windows doesn't give signs of it being alive), fullscreen tabbing most of times "unstuck" the situation, like some kind of race condition maybe on controller polling being reset with the swap chain mode changes..

Squall-Leonhart commented at 2024-02-24 09:13:

Issue is because of the dropping of the controller, all i can say is get a BT 4.1 receiver and nothing higher for the best compatibility with switch controllers.

alessiot89 commented at 2024-02-24 11:05:

no, it's not a BT only issue, this happens also in wired mode.
also if it was a BT stability issue, this would not be solved instantaneously toggling fullscreen/windowed with f11 most of the time. Plus I don't have this problem with other programs, games and emulator when using my controller, either BT or wired mode.
finally, this seems to happen on "transitions" view, or when the game is like waiting for an input like on dialogue or moving in/out from a game menu or exiting a battle, while it doesn't happen when travelling, moving around the game world (walking, running, bicycle) even if I stay in idle for a while.
my bluetooth card is also an intel 9260, BT version: 5.1, which is working fine in every other scenarios outside yuzu and is more than enough to manage a 1-2 meters distance connection https://www.intel.com/content/www/us/en/products/sku/99445/intel-wirelessac-9260/specifications.html

Squall-Leonhart commented at 2024-02-24 11:18:

no, it's not a BT only issue, this happens also in wired mode.
Well yes, when disconnecting or connecting a controller the application will wait on the device setup within SDL's input handler, if you try to interact with the window in this case windows itself may close the temporarily hung process, if the emulated game is communicating vibration or motion data to and from the controller at the time this disconnection happens you can wind up with an access violation.
What also works against you is the USB issues present on the Zen 2 and 3 architectures that result in the root port resetting periodically to correct hung events. - Contrary to AMD's insistence, is not fixed on all systems.
also if it was a BT stability issue, this would not be solved instantaneously toggling fullscreen/windowed with f11 most of the time.
Thus demonstrating you have no idea what goes on or what happens with application handles on window change events.
Plus I don't have this problem with other programs, games and emulator when using my controller, either BT or wired mode.
I call bs to this, SDL has constructor latency everywhere its used, and its a frequent issue opened on sdl's tracker.
my bluetooth card is also an intel 9260, BT version: 5.1, which is working fine in every other scenarios outside yuzu and is more than enough to manage a 1-2 meters distance connection https://www.intel.com/content/www/us/en/products/sku/99445/intel-wirelessac-9260/specifications.html
5.1 receivers are wholly problematic with switch hardware, this is known fact.

alessiot89 commented at 2024-02-24 11:30:

the controller is not disconnecting. reconnecting the xbox series x/s controller takes some seconds in usb mode (like 3 or so) and even more in BT mode (like 10 or so), while toggling between fullscreen/windowed restores the input instantly.
The games even recognise the input I pressed while the controller wasn't working in-game, e.g.: the controller stops to responds in the game, last input pressed was the button mapped as "A" button, I toggle fullscreen/windowed, than the game immediately responds to the "A" button even if I remove my finger from it before toggling F11 key on my keyboard. Of course switching from USB to BT while the game is running it is a different task but I am not talking about this.
and this is happening pokemon sword (so I guess shield to since are basically the same game) even if before opening yuzu I turn off the BT card, I connect the controller with the usb cable and than I start yuzu and load the game.
so I guess it's some kind of SDL issue
I tried also to upgrade the xbox controller firmware (using the windows store xbox accessories app) but didn't help.
Which makes a bit harder to debug I guess, this happens randomly, it cannot for many minutes or it can happens frequently in few seconds. I am not familiar with yuzu debugging and profiling, but when this input hangs happens the rest of the game logic seems to continue fine, since graphics and music do not hang.. is there any profiling/debug view mode outside the controller debug window to see the input handling? like something from the polling rate or an input queue?
edit: as for the usb bug on some AMD motherboards I didn't notice it, maybe my model isn't affected
motherboard chipset drivers are up-to-date to last version by amd
I updated as well the intel BT/wifi card drivers too, so I guess is some kind of sdl issue, unless pokemon has a weird input polling/handling system

Squall-Leonhart commented at 2024-02-24 11:42:

edit: as for the usb bug on some AMD motherboards I didn't notice it, maybe my model isn't affected
It's a PCIE bus issue that can manifest when multiple gen4 devices are present on the CPU, the link on the cpu generates excessive errors and issues the usb controller a reset command, in some cases this reloads all hubs and devices but usually it acts like a dam has rapidly filled up and someone suddenly opens a flood gate letting forth all the buffered commands, it can be affected by altering the priority of Interrupts in the MSI Utility provided by guru3d user mbk1969
@german77 would refactoring the HID IPC have potentially broken games in very particular circumstances and ways?
@alessiot89 can you try with msvc artifact attached to https://github.com/yuzu-emu/yuzu/actions/runs/8026455810?pr=13135

alessiot89 commented at 2024-02-24 12:10:

edit: as for the usb bug on some AMD motherboards I didn't notice it, maybe my model isn't affected

It's a PCIE bus issue that can manifest when multiple gen4 devices are present on the CPU, the link on the cpu generates excessive errors and issues the usb controller a reset command, in some cases this reloads all hubs and devices but usually it acts like a dam has rapidly filled up and someone suddenly opens a flood gate letting forth all the buffered commands, it can be affected by altering the priority of Interrupts in the MSI Utility provided by guru3d user mbk1969

@german77 would refactoring the HID IPC have potentially broken games in very particular circumstances and ways?

@alessiot89 can you try with msvc artifact attached to https://github.com/yuzu-emu/yuzu/actions/runs/8026455810?pr=13135
testing now..
shall any specific advanced controller setting?

immagine

alessiot89 commented at 2024-02-24 12:14:

dang happened again
edit: I wanna see if having steam in background can be an issue
edit2: happened again, it's not steam.
I also further noticed that not only F11 toggle unfreeze the input but also pressing the windows start menu or opening the side bar of the action centre unstuck this
so maybe, mine is just a guess since I never dealt with sdl in coding, there is some problem in the row input queue?

alessiot89 commented at 2024-02-24 13:41:

speaking about SDL, I also notice this, although not sure how much related: https://github.com/libsdl-org/SDL/issues/9106
I currently set the controller as "Pro Controller" since it matches better the xbox controller
edit: also noted this https://github.com/libsdl-org/SDL/issues/9019

alessiot89 commented at 2024-02-25 23:11:

seems like sdl 2.28.2 may fix the problem
https://github.com/Ryujinx/Ryujinx/issues/3301
https://github.com/libsdl-org/SDL/releases/tag/release-2.28.2
edit: dang, is yuzu already using it? :\

alessiot89 commented at 2024-02-26 22:15:

seems like sdl 2.28.2 may fix the problem Ryujinx/Ryujinx#3301 https://github.com/libsdl-org/SDL/releases/tag/release-2.28.2

edit: dang, is yuzu already using it? :
yes the version is the same however the binary it's not. not sure if SDL relese is wrong since all versions for windows are literally the same (same hashing), I downloaded the VC version (although as I just said it's totally equal to the mingw version) and the situation seems better. I need more time to test/play but I was able to have like over 1 hour session without random missing focus using the "official" SDL dll

german77 commented at 2024-02-27 00:04:

I doubt SDL is the issue here. Open the controller debugger... view->debugging->controller P1 you will see input in real time. If that stops working then is 100% sdl. If it's only in game then is an emulation bug.

alessiot89 commented at 2024-02-27 00:06:

When the controller stops to respond the controller debgger also show no input
so yes looks like an sdl issue
now I am using the official sdl dll and it seems fine, even putting the controller in idle for many minutes or so.

german77 commented at 2024-02-27 00:10:

Only difference with official SDL binary is that we build without WGI support. SDL dies when yuzu is launched through steam and WGI is active.

Squall-Leonhart commented at 2024-02-27 00:12:

Only difference with official SDL binary is that we build without WGI support. SDL dies when yuzu is launched through steam and WGI is active.
Should be fine with the xbox extended driver installed?

german77 commented at 2024-02-27 00:15:

Yuzu currently is on 2.28.2. I can build one with 2.30.0 if that fixes the issues even without WGI. We can update the submodule.

Squall-Leonhart commented at 2024-02-27 00:16:

Actually, it seems like SDL fixed this issue here github.com/libsdl-org/SDL@376ef4e418

alessiot89 commented at 2024-02-27 00:18:

Only difference with official SDL binary is that we build without WGI support. SDL dies when yuzu is launched through steam and WGI is active.
I see however so far, a couple of hours or a bit more, using the official SDL 2.28.2 with WGI seems fine. I am not launching yuzu trough steam though.


[Export of Github issue for yuzu-emu/yuzu. Generated on 2024.02.28 at 10:04:32.]

**Branch:** [__refs_pull_13119_head](https://accord.dravee.dev/Accord/yuzu-mirror/src/branch/__refs_pull_13119_head) #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) opened issue at [2024-02-22 14:24](https://github.com/yuzu-emu/yuzu/issues/13119): > ### Is there an existing issue for this? > - [X] I have searched the existing issues > ### Affected Build(s) > Mainline 1722 > ### Description of Issue > Randomly playing Pokemon Sword/Shield the game hangs but the audio (the music) continues to play. Most of time the issue is temporary fixed toggling fullscreen/windowed with F11. However, sometimes toggling between windowed and fullscreen mode doesn't fix and the game completely freezes. This happens both in windowed mode and in fullscreen mode. > ### Expected Behavior > No hangs should occurs. > ### Reproduction Steps > There is no specific way to reproduce it sadly, it happens randomly playing the game. > ### Log File > [yuzu_log.txt](https://github.com/yuzu-emu/yuzu/files/14375083/yuzu_log.txt) > ### System Configuration > CPU: Ryzen 5 3600X > GPU/Driver: RX 67000 XT driver "AMD Software: Adrenalin Edition 24.2.1 for HELLDIVERS™ 2" version 23.40.19.01 > RAM: 32GB DDR4 @3600 > OS: Windows 10 22H2 build 19045.3930 > Controller: XBOX Series X/S controller, last firmware updated (the issue happens with both bluettoth and usb mode) #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-23 22:42](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962095976): > I think all this is related about controller polling rate, especially with BT devices... I noted when this happens than after few seconds the controller goes in idle and stops to responds to yuzu (the debug controller windows doesn't give signs of it being alive), fullscreen tabbing most of times "unstuck" the situation, like some kind of race condition maybe on controller polling being reset with the swap chain mode changes.. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2024-02-24 09:13](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962307020): > Issue is because of the dropping of the controller, all i can say is get a BT 4.1 receiver and nothing higher for the best compatibility with switch controllers. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-24 11:05](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962329252): > no, it's not a BT only issue, this happens also in wired mode. > also if it was a BT stability issue, this would not be solved instantaneously toggling fullscreen/windowed with f11 most of the time. Plus I don't have this problem with other programs, games and emulator when using my controller, either BT or wired mode. > finally, this seems to happen on "transitions" view, or when the game is like waiting for an input like on dialogue or moving in/out from a game menu or exiting a battle, while it doesn't happen when travelling, moving around the game world (walking, running, bicycle) even if I stay in idle for a while. > my bluetooth card is also an intel 9260, BT version: 5.1, which is working fine in every other scenarios outside yuzu and is more than enough to manage a 1-2 meters distance connection https://www.intel.com/content/www/us/en/products/sku/99445/intel-wirelessac-9260/specifications.html #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2024-02-24 11:18](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962331697): > > no, it's not a BT only issue, this happens also in wired mode. > Well yes, when disconnecting or connecting a controller the application will wait on the device setup within SDL's input handler, if you try to interact with the window in this case windows itself may close the temporarily hung process, if the emulated game is communicating vibration or motion data to and from the controller at the time this disconnection happens you can wind up with an access violation. > What also works against you is the USB issues present on the Zen 2 and 3 architectures that result in the root port resetting periodically to correct hung events. - [Contrary to AMD's insistence, is not fixed on all systems.](https://www.reddit.com/r/Amd/comments/13yhdup/2023_almost_3_years_later_and_we_still_have_the/) > > also if it was a BT stability issue, this would not be solved instantaneously toggling fullscreen/windowed with f11 most of the time. > Thus demonstrating you have no idea what goes on or what happens with application handles on window change events. > > Plus I don't have this problem with other programs, games and emulator when using my controller, either BT or wired mode. > I call bs to this, SDL has constructor latency everywhere its used, and its a frequent issue opened on sdl's tracker. > > my bluetooth card is also an intel 9260, BT version: 5.1, which is working fine in every other scenarios outside yuzu and is more than enough to manage a 1-2 meters distance connection https://www.intel.com/content/www/us/en/products/sku/99445/intel-wirelessac-9260/specifications.html > 5.1 receivers are wholly problematic with switch hardware, this is known fact. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-24 11:30](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962333972): > the controller is not disconnecting. reconnecting the xbox series x/s controller takes some seconds in usb mode (like 3 or so) and even more in BT mode (like 10 or so), while toggling between fullscreen/windowed restores the input instantly. > The games even recognise the input I pressed while the controller wasn't working in-game, e.g.: the controller stops to responds in the game, last input pressed was the button mapped as "A" button, I toggle fullscreen/windowed, than the game immediately responds to the "A" button even if I remove my finger from it before toggling F11 key on my keyboard. Of course switching from USB to BT while the game is running it is a different task but I am not talking about this. > and this is happening pokemon sword (so I guess shield to since are basically the same game) even if before opening yuzu I turn off the BT card, I connect the controller with the usb cable and than I start yuzu and load the game. > so I guess it's some kind of SDL issue > I tried also to upgrade the xbox controller firmware (using the windows store xbox accessories app) but didn't help. > Which makes a bit harder to debug I guess, this happens randomly, it cannot for many minutes or it can happens frequently in few seconds. I am not familiar with yuzu debugging and profiling, but when this input hangs happens the rest of the game logic seems to continue fine, since graphics and music do not hang.. is there any profiling/debug view mode outside the controller debug window to see the input handling? like something from the polling rate or an input queue? > edit: as for the usb bug on some AMD motherboards I didn't notice it, maybe my model isn't affected > motherboard chipset drivers are up-to-date to last version by amd > I updated as well the intel BT/wifi card drivers too, so I guess is some kind of sdl issue, unless pokemon has a weird input polling/handling system #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2024-02-24 11:42](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962336341): > > edit: as for the usb bug on some AMD motherboards I didn't notice it, maybe my model isn't affected > It's a PCIE bus issue that can manifest when multiple gen4 devices are present on the CPU, the link on the cpu generates excessive errors and issues the usb controller a reset command, in some cases this reloads all hubs and devices but usually it acts like a dam has rapidly filled up and someone suddenly opens a flood gate letting forth all the buffered commands, it can be affected by altering the priority of Interrupts in the MSI Utility provided by guru3d user mbk1969 > @german77 would refactoring the HID IPC have potentially broken games in very particular circumstances and ways? > @alessiot89 can you try with msvc artifact attached to https://github.com/yuzu-emu/yuzu/actions/runs/8026455810?pr=13135 #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-24 12:10](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962344502): > > > edit: as for the usb bug on some AMD motherboards I didn't notice it, maybe my model isn't affected > > > > It's a PCIE bus issue that can manifest when multiple gen4 devices are present on the CPU, the link on the cpu generates excessive errors and issues the usb controller a reset command, in some cases this reloads all hubs and devices but usually it acts like a dam has rapidly filled up and someone suddenly opens a flood gate letting forth all the buffered commands, it can be affected by altering the priority of Interrupts in the MSI Utility provided by guru3d user mbk1969 > > > > @german77 would refactoring the HID IPC have potentially broken games in very particular circumstances and ways? > > > > @alessiot89 can you try with msvc artifact attached to https://github.com/yuzu-emu/yuzu/actions/runs/8026455810?pr=13135 > testing now.. > shall any specific advanced controller setting? ![immagine](https://github.com/yuzu-emu/yuzu/assets/9203066/fe4d779a-2af1-4679-9f8b-1116fcc21d9b) #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-24 12:14](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962345372): > dang happened again > edit: I wanna see if having steam in background can be an issue > edit2: happened again, it's not steam. > I also further noticed that not only F11 toggle unfreeze the input but also pressing the windows start menu or opening the side bar of the action centre unstuck this > so maybe, mine is just a guess since I never dealt with sdl in coding, there is some problem in the row input queue? #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-24 13:41](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1962366968): > speaking about SDL, I also notice this, although not sure how much related: https://github.com/libsdl-org/SDL/issues/9106 > I currently set the controller as "Pro Controller" since it matches better the xbox controller > edit: also noted this https://github.com/libsdl-org/SDL/issues/9019 #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-25 23:11](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1963095059): > seems like sdl 2.28.2 may fix the problem > https://github.com/Ryujinx/Ryujinx/issues/3301 > https://github.com/libsdl-org/SDL/releases/tag/release-2.28.2 > edit: dang, is yuzu already using it? :\ #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-26 22:15](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1965395718): > > seems like sdl 2.28.2 may fix the problem [Ryujinx/Ryujinx#3301](https://github.com/Ryujinx/Ryujinx/issues/3301) https://github.com/libsdl-org/SDL/releases/tag/release-2.28.2 > > > > edit: dang, is yuzu already using it? :\ > yes the version is the same however the binary it's not. not sure if SDL relese is wrong since all versions for windows are literally the same (same hashing), I downloaded the VC version (although as I just said it's totally equal to the mingw version) and the situation seems better. I need more time to test/play but I was able to have like over 1 hour session without random missing focus using the "official" SDL dll #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/5944268?u=0ce9c0fd0fb51813509fedff9ee9fa0ec1ff42dc&v=4" width="50"></div>[german77](https://github.com/german77) commented at [2024-02-27 00:04](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1965547346): > I doubt SDL is the issue here. Open the controller debugger... view->debugging->controller P1 you will see input in real time. If that stops working then is 100% sdl. If it's only in game then is an emulation bug. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-27 00:06](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1965549685): > When the controller stops to respond the controller debgger also show no input > so yes looks like an sdl issue > now I am using the official sdl dll and it seems fine, even putting the controller in idle for many minutes or so. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/5944268?u=0ce9c0fd0fb51813509fedff9ee9fa0ec1ff42dc&v=4" width="50"></div>[german77](https://github.com/german77) commented at [2024-02-27 00:10](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1965555245): > Only difference with official SDL binary is that we build without WGI support. SDL dies when yuzu is launched through steam and WGI is active. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2024-02-27 00:12](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1965560274): > > Only difference with official SDL binary is that we build without WGI support. SDL dies when yuzu is launched through steam and WGI is active. > Should be fine with the xbox extended driver installed? #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/5944268?u=0ce9c0fd0fb51813509fedff9ee9fa0ec1ff42dc&v=4" width="50"></div>[german77](https://github.com/german77) commented at [2024-02-27 00:15](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1965562877): > Yuzu currently is on 2.28.2. I can build one with 2.30.0 if that fixes the issues even without WGI. We can update the submodule. #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/1098176?v=4" width="50"></div>[Squall-Leonhart](https://github.com/Squall-Leonhart) commented at [2024-02-27 00:16](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1965563408): > Actually, it seems like SDL fixed this issue here https://github.com/libsdl-org/SDL/commit/376ef4e418d9489f5ecdd5159020184370b4ba63 #### <div><img width="50" height="50" src="https://avatars.githubusercontent.com/u/9203066?u=adc0b89e80b4115a6d3c470e44f46e361ad78bdd&v=4" width="50"></div>[alessiot89](https://github.com/alessiot89) commented at [2024-02-27 00:18](https://github.com/yuzu-emu/yuzu/issues/13119#issuecomment-1965566151): > > Only difference with official SDL binary is that we build without WGI support. SDL dies when yuzu is launched through steam and WGI is active. > I see however so far, a couple of hours or a bit more, using the official SDL 2.28.2 with WGI seems fine. I am not launching yuzu trough steam though. > ------------------------------------------------------------------------------- > [Export of Github issue for [yuzu-emu/yuzu](https://github.com/yuzu-emu/yuzu). Generated on 2024.02.28 at 10:04:32.]
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Accord/yuzu-mirror#13119
No description provided.