yuzu
yuzu copied to clipboard
yuzu-emu
SHIN MEGAMI TENSEI Ⅴ Random Crashing
The game will cause the emulator to crash randomly. Not consistently reproducible but here is a log from one of the crashes I have experienced.
5800X 5700XT 21.11.2 driver 32gb of RAM yuzu_log.txt.txt
Experienced a freeze, game dropped to 0 fps while audio continued to play, pausing and continuing didn't do anything.
https://1drv.ms/t/s!ApzIkK--zvP0h7dO3hivB4cMWtF_QA?e=moyHTY
This log is from the game causing the emulator to freeze up on bootup, includes graphics debug enabled(idk how useful it will be in this specific instance) and all future logs I contribute will have it enabled after this post yuzu_log.txt .
This happens to me too. Only tested it on Yuzu EA 2177+ (I am not sure in which one I had the issue for the first time, but it was at least 2177).
Yuzu
- Version: EA 2201 (happened for the first time in a version between 2177 and 2200).
- API: Vulkan
- GPU accuracy level: Normal
- Docked/Handheld: Docked
- Window Adapting Filter: AMD'S FIDELITYFX SR
- Anti-Aliasing: None
- Resolution: x1
My specs:
- OS: Windows 10 21H1 (updated up until today)
- GPU: GTX 1060 3GB (driver 496.49)
- CPU. i7 4790 (not k)
- RAM: 16GB DDR3 1600MHz
- HDD: 1TB 7200RPM
- Using a HORI controller (but happened without the controller too)
How did it happen?
- The first time happened in the cave almost at the beginning of the game after engaging in a combat with the sword (X button).
- The second time happened in combat against the first boss after pressing A after a move.
- It happened for a third and a fourth time that I don't remember.
- The fifth and last time, that happened a while ago, I was getting engaged by a monster from behind.
I am not sure how to reproduce this since every time it was different. yuzu_log.txt.old.zip
The game will cause the emulator to crash randomly. Not consistently reproducible but here is a log from one of the crashes I have experienced.
5800X 5700XT 21.11.2 driver 32gb of RAM yuzu_log.txt.txt
Did you have more than 4Gb of ram ?
Ok finally the game completely froze up except audio again so heres a new log. played for about 2 hours just locked up while running around in da,at the second netherworld location. yuzu_log.txt
Like on my previous post (this), the specs remain the same.
Here is another crash log. This time the following line is at the end and it seems to have something to do with Vulkan. I will switch to OpenGL to see if the game still crashes. Last 5 lines of the log:
[1258.828525] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x000000000000D000 (start address = 0x0000000000000000, size = 65536) [1258.828527] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x000000000000E000 (start address = 0x0000000000000000, size = 65536) [1258.828529] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x000000000000F000 (start address = 0x0000000000000000, size = 65536) [1259.778150] Render.Vulkan <Critical> video_core\vulkan_common\vulkan_device.cpp:ReportLoss:670: Device loss occured! [1259.778408] Render.Vulkan <Critical> video_core\vulkan_common\vulkan_device.cpp:ReportLoss:670: Device loss occured!!
Game locked up again, used task manager to force close yuzu which resulted in a large log so i just copied the last bit.
[4873.077610] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocParam:202: (STUBBED) called type=1 [4873.094900] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E0000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094904] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E1000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094905] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E2000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094906] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E3000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094907] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E4000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094908] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E5000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094910] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E6000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094911] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E7000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094912] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E8000 (start address = 0x0000001AD50DE000, size = 49152) [4873.094913] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E9000 (start address = 0x0000001AD50DE000, size = 49152) [4873.102302] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocFree:247: (STUBBED) called [4873.113367] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E0000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113370] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E1000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113371] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E2000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113372] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E3000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113374] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E4000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113375] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E5000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113376] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E6000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113376] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E7000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113377] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E8000 (start address = 0x0000001AD50DE000, size = 49152) [4873.113378] HW.Memory <Error> core\memory.cpp:operator ():216: Unmapped ReadBlock @ 0x0000001AD50E9000 (start address = 0x0000001AD50DE000, size = 49152) [4873.118641] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocParam:202: (STUBBED) called type=1 [4873.118843] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocParam:202: (STUBBED) called type=1 [4873.163667] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocParam:202: (STUBBED) called type=1 [4873.163907] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocParam:202: (STUBBED) called type=1 [4873.175978] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocParam:202: (STUBBED) called type=1 [4873.176202] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocParam:202: (STUBBED) called type=1 [4873.186327] Service.AM <Warning> core\hle\service\am\am.cpp:SetTerminateResult:1497: (STUBBED) called, result=0x000002A2 [4873.186445] Debug.Emulated <Critical> core\hle\kernel\svc.cpp:Break:561: Signalling debugger, PANIC! info1=0x000000108A2B3F38, info2=0x0000000000000004 [4873.186448] Debug.Emulated <Critical> core\hle\kernel\svc.cpp:operator ():542: debug_buffer_err_code=0 [4873.186460] Debug.Emulated <Critical> core\hle\kernel\svc.cpp:Break:612: Emulated program broke execution! reason=0x0000000000000000, info1=0x000000108A2B3F38, info2=0x0000000000000004 [4873.186464] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:266: Backtrace, sp=0000000000000010, pc=00000000106684D4 [4873.186466] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:268: Module Name Address Original Address Offset Symbol [4873.186466] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:269: [4873.230957] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: sdk 0000007100056518 00000000105C2518 0000000000056518 _ZN2nn4diag6detail5AbortEPKNS_6ResultE [4873.230961] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: sdk 0000007100054E0C 00000000105C0E0C 0000000000054E0C _ZN2nn4diag6detail10VAbortImplEPKcS3_S3_iPKNS_6ResultEPKNS_2os17UserExceptionInfoES3_St9__va_list [4873.230962] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: sdk 0000007100054ED4 00000000105C0ED4 0000000000054ED4 _ZN2nn4diag6detail9AbortImplEPKcS3_S3_iPKNS_6ResultES3_z [4873.230963] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: sdk 0000007100054F6C 00000000105C0F6C 0000000000054F6C _ZN2nn4diag6detail9AbortImplEPKcS3_S3_i [4873.230964] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007101884B98 0000000009888B98 0000000001884B98 [4873.230965] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007101827074 000000000982B074 0000000001827074 [4873.230967] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071017D1AEC 00000000097D5AEC 00000000017D1AEC [4873.230968] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071017D1A04 00000000097D5A04 00000000017D1A04 [4873.230970] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007101703594 0000000009707594 0000000001703594 [4873.230971] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071018862C4 000000000988A2C4 00000000018862C4 [4873.230971] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007101885C90 0000000009889C90 0000000001885C90 [4873.230972] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007103BCC954 000000000BBD0954 0000000003BCC954 [4873.230973] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007103BCC814 000000000BBD0814 0000000003BCC814 [4873.230973] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007103BCC10C 000000000BBD010C 0000000003BCC10C [4873.230974] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007103BF461C 000000000BBF861C 0000000003BF461C [4873.230974] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007103BEFAAC 000000000BBF3AAC 0000000003BEFAAC [4873.230975] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007100F13910 0000000008F17910 0000000000F13910 [4873.230976] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007101F58D7C 0000000009F5CD7C 0000000001F58D7C [4873.230976] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071025629F8 000000000A5669F8 00000000025629F8 [4873.230977] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071024F4748 000000000A4F8748 00000000024F4748 [4873.230977] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071024F42EC 000000000A4F82EC 00000000024F42EC [4873.230978] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071020ECB48 000000000A0F0B48 00000000020ECB48 [4873.230979] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071024A3C18 000000000A4A7C18 00000000024A3C18 [4873.230979] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071024A3ECC 000000000A4A7ECC 00000000024A3ECC [4873.230980] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071016CF588 00000000096D3588 00000000016CF588 [4873.230980] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 00000071016CE5CC 00000000096D25CC 00000000016CE5CC [4873.230981] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 0000007101F43F08 0000000009F47F08 0000000001F43F08 [4873.230981] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: main 000000710188D7AC 00000000098917AC 000000000188D7AC [4873.230982] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: sdk 00000071000CFB44 000000001063BB44 00000000000CFB44 [4873.230983] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: sdk 00000071000D4310 0000000010640310 00000000000D4310 [4873.230983] Core.ARM <Error> core\arm\arm_interface.cpp:LogBacktrace:274: sdk 00000070EFA93FFC FFFFFFFFFFFFFFFC FFFFFFFFEFA93FFC
Ok finally the game completely froze up except audio again so heres a new log. played for about 2 hours just locked up while running around in da,at the second netherworld location. yuzu_log.txt
Same issue, using Vulkan and Nvidia GPU
Experiencing the same problem here, Win11, SMT5, Nvidia GPU, Vulkan, issue is as described. Thanks everyone.
Same issue for me, cushes on random encounters with "HW.Memory <Error> core/memory.cpp:operator():214: Unmapped ReadBlock @ 0x0000000000000000 (start address = 0x0000000000000000, size = 65536)". I'm linux manjaro and my specs are R7 5800x gtx 1070 and 32gb ram. Before crushing sound is still playing, videos dies! I was monitoring my cpu gpu vram and ram while it happend so I found out that after video dies vram usage start to incress untill I have no more vram and then it starts incressing ram usage and when it gets at 32gb emulators cushes !
This also occurs for me when using OpenGL. Same specs as before WIN11/gtx1080/lastest everything.
This occurs much, much less frequently in unlocked-fps mode by using the new per game setting for fps limit and limiting the game to 1x instead of the default 1000x. This will mitigate some of the occurrences of the bug, by limiting the fps to 60 when using the 60 fps lod mod. This setting affects unlocked fps gameplay, I am uncertain if this will affect those playing with locked-fps mode, yuzu runs a little faster when unlocked on my system so I prefer this approach for now until I learn a better or the right way to do it.
Testing with this configuration and I have had two crashes in 6 hours of gameplay, I typical get 60fps, while I can achieve fps higher than this, setting the 1x fps limit solved most of the crashing for me. I noticed that my old system has a better time with its minimum fps with this config and is generally more stable. I expect this will improve over time when the fine folks with Yuzu have time to work with SMT5.
When running unlocked I can see 70 to 80 fps in the best spots, but the crashes occur very frequently. It was only after setting the 1x per game fps limit that the issue was mostly mitigated on my system.
System Specs Windows 11 (Tuned) i6700k at 4.8Ghz 16GB DDR4-3466 / PC4-27700 DDR4 GTX1080 with v496.76 144 fps Display with gsync
Yuzu 2278 < typo (I don't recall what build I was on at the time.) Vulkan CPU: Unsafe GPU: Normal Scale: 2x FPS: 1x and unlocked-fps <-- (30fps or 60fps if you have the mod) FXAA SCALEFORCE
This occurs much, much less frequently in unlocked-fps mode by using the new per game setting for fps limit and limiting the game to 1x instead of the default 1000x. This will mitigate some of the occurrences of the bug, by limiting the fps to 60 when using the 60 fps lod mod. This setting affects unlocked fps gameplay, I am uncertain if this will affect those playing with locked-fps mode, yuzu runs a little faster when unlocked on my system so I prefer this approach for now until I learn a better or the right way to do it.
Testing with this configuration and I have had two crashes in 6 hours of gameplay, I typical get 60fps, while I can achieve fps higher than this, setting the 1x fps limit solved most of the crashing for me. I noticed that my old system has a better time with its minimum fps with this config and is generally more stable. I expect this will improve over time when the fine folks with Yuzu have time to work with SMT5.
When running unlocked I can see 70 to 80 fps in the best spots, but the crashes occur very frequently. It was only after setting the 1x per game fps limit that the issue was mostly mitigated on my system.
System Specs Windows 11 (Tuned) i6700k at 4.8Ghz 16GB DDR4-3466 / PC4-27700 DDR4 GTX1080 with v496.76 144 fps Display with gsync
Yuzu 2278 Vulkan CPU: Unsafe GPU: Normal Scale: 2x FPS: 1x and unlocked-fps <-- (30fps or 60fps if you have the mod) FXAA SCALEFORCE
This settings helped me a lot, I played for about 3 hours this morning without a single crash. I'm in EA 2244 tho, and I have the 472.12 Nvidia driver.
This occurs much, much less frequently in unlocked-fps mode by using the new per game setting for fps limit and limiting the game to 1x instead of the default 1000x. This will mitigate some of the occurrences of the bug, by limiting the fps to 60 when using the 60 fps lod mod. This setting affects unlocked fps gameplay, I am uncertain if this will affect those playing with locked-fps mode, yuzu runs a little faster when unlocked on my system so I prefer this approach for now until I learn a better or the right way to do it.
Testing with this configuration and I have had two crashes in 6 hours of gameplay, I typical get 60fps, while I can achieve fps higher than this, setting the 1x fps limit solved most of the crashing for me. I noticed that my old system has a better time with its minimum fps with this config and is generally more stable. I expect this will improve over time when the fine folks with Yuzu have time to work with SMT5.
When running unlocked I can see 70 to 80 fps in the best spots, but the crashes occur very frequently. It was only after setting the 1x per game fps limit that the issue was mostly mitigated on my system.
System Specs Windows 11 (Tuned) i6700k at 4.8Ghz 16GB DDR4-3466 / PC4-27700 DDR4 GTX1080 with v496.76 144 fps Display with gsync
Yuzu 2278 Vulkan CPU: Unsafe GPU: Normal Scale: 2x FPS: 1x and unlocked-fps <-- (30fps or 60fps if you have the mod) FXAA SCALEFORCE
Thank you for this Seems to run very stable after changing to 1x instead of 1000x No crashes so far
This occurs much, much less frequently in unlocked-fps mode by using the new per game setting for fps limit and limiting the game to 1x instead of the default 1000x. This will mitigate some of the occurrences of the bug, by limiting the fps to 60 when using the 60 fps lod mod. This setting affects unlocked fps gameplay, I am uncertain if this will affect those playing with locked-fps mode, yuzu runs a little faster when unlocked on my system so I prefer this approach for now until I learn a better or the right way to do it. Testing with this configuration and I have had two crashes in 6 hours of gameplay, I typical get 60fps, while I can achieve fps higher than this, setting the 1x fps limit solved most of the crashing for me. I noticed that my old system has a better time with its minimum fps with this config and is generally more stable. I expect this will improve over time when the fine folks with Yuzu have time to work with SMT5. When running unlocked I can see 70 to 80 fps in the best spots, but the crashes occur very frequently. It was only after setting the 1x per game fps limit that the issue was mostly mitigated on my system. System Specs Windows 11 (Tuned) i6700k at 4.8Ghz 16GB DDR4-3466 / PC4-27700 DDR4 GTX1080 with v496.76 144 fps Display with gsync Yuzu 2278 Vulkan CPU: Unsafe GPU: Normal Scale: 2x FPS: 1x and unlocked-fps <-- (30fps or 60fps if you have the mod) FXAA SCALEFORCE
Thank you for this Seems to run very stable after changing to 1x instead of 1000x No crashes so far
If you see any more crashes, be sure to let the Yuzu team know about it, as this was not a perfect solution for the bug when I wrote up this workaround. I am quite pleased that this approach has helped some people, made my morning.
Have a great holiday everyone.
I'm on yuzu 2360, before when it was crushing my ram usage would go to heaven and once it reach 100% it would crush, you guys fix it now (by fix it I mean made it worst) cause the game still stops on encounter and ram goes to 100% but unlike before now the emulator does not crush it just makes my pc unsuable cause I can bearly move the mouse with ram at 100% so no, not fixed !!!
I just installed version 2360, but from what you said, I'll wait for a more stable version.
That's correct, its still an issue, I can confirm, it does seems to be occurring more now, though I haven't looked into why as I have not been playing that title, I have been using my switch instead. I would like to continue on Yuzu when it is ready.
If there is a request for more logs please let me know I will provide them and I will upload them using the latest patreon build at that time. I should have access to any requested releases for that title.
just want to report that the random crashes are still there, sometimes I can play for 1-3hrs w/out crashing other time it will soft lock my entire desktop
specs: AMD Ryzen 7 5800H NVIDIA GeForce RTX 3060 16GB Ram Wins 10
Same problem here, crashes sometimes on starting a combat, it is not infrequent (about 1 in 10 as someone said). Using Yuzu EA 2685, unmodded game (30fps), Vulkan renderer, CPU accuracy Auto.
specs: 12900K 32GB RAM RTX 2080 Ti Win11
Same issues as everyone else. Logs tend to get over 100mb pretty quickly with the same errors
HW.Memory <Error> core\memory.cpp:operator ():215: Unmapped ReadBlock xxx
Also a ton of things like this:
[ 80.698633] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocFree:246: (STUBBED) called [ 83.061004] Service.NVDRV <Warning> core\hle\service\nvdrv\devices\nvmap.cpp:IocParam:201: (STUBBED) called type=1
Same problem here, crashes sometimes on starting a combat, it is not infrequent (about 1 in 10 as someone said). Using Yuzu EA 2685, unmodded game (30fps), Vulkan renderer, CPU accuracy Auto.
specs: 12900K 32GB RAM RTX 2080 Ti Win11
Same here also. Yuzu EA 2823, modded for 60fps, Vulkan, CPU accuracy Auto. Always a dice roll when entering a battle because the game might freeze, always paranoid that I should save before I run into battles because it'll crash and I'd have to redo some progress. What baffles me is the logs show literally nothing when it happens, making it really hard to tell what even happened when the freeze happens.
specs: AMD Ryzen 7 32GB RAM Win11 NVIDIA GeForce RTX 3060
Same problem here, crashes sometimes on starting a combat, it is not infrequent (about 1 in 10 as someone said). Using Yuzu EA 2685, unmodded game (30fps), Vulkan renderer, CPU accuracy Auto. specs: 12900K 32GB RAM RTX 2080 Ti Win11
Same here also. Yuzu EA 2823, modded for 60fps, Vulkan, CPU accuracy Auto. Always a dice roll when entering a battle because the game might freeze, always paranoid that I should save before I run into battles because it'll crash and I'd have to redo some progress. What baffles me is the logs show literally nothing when it happens, making it really hard to tell what even happened when the freeze happens.
specs: AMD Ryzen 7 32GB RAM Win11 NVIDIA GeForce RTX 3060
Same here. yuzu EA 2985 Happens on battle start very frequently. 1 out of 10 times, like someone said.
It's been a year and this is still an issue on the latest builds (mainline 1218 and EA 3072).
It's very frequent for me. Tried everything, from locking to 60 FPS, locking to 30, fullscreen, windowed, vsync on/off, CPU/GPU settings, turning on/off hacks, increasing pagefile (30gb on 16gb ram), nothing works.
