Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Unexpected API error "ErrorDeviceLost" during battle with Fire Emblem Engage intermittently #6747

Open
Zakarini opened this issue Apr 29, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Zakarini
Copy link

Zakarini commented Apr 29, 2024

Description of the issue

Occasionally in battle, the entire system will lock up and then Ryujinx closes itself suddenly. It unfortunately took 28ish turns of constant battles to cause the crash. I was on the Divine Paralogue - The Ancestor map. I do not know if it is that map, the amount of fights I did, or the turn count. Since it happened as the fight was ending, I will assume fights for reproduction steps. This crash was against a Wyvern like enemy if that matters.

The last lines from the log read

01:52:15.513 |E| GUI.RenderThread Application : Unhandled exception caught: Ryujinx.Graphics.Vulkan.VulkanException: Unexpected API error "ErrorDeviceLost".
   at Ryujinx.Graphics.Vulkan.CommandBufferPool.Return(CommandBufferScoped cbs, ReadOnlySpan`1 waitSemaphores, ReadOnlySpan`1 waitDstStageMask, ReadOnlySpan`1 signalSemaphores) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.Graphics.Vulkan\CommandBufferPool.cs:line 281
   at Ryujinx.Graphics.Vulkan.PipelineFull.FlushCommandsImpl() in D:\a\Ryujinx\Ryujinx\src\Ryujinx.Graphics.Vulkan\PipelineFull.cs:line 273
   at Ryujinx.Graphics.Vulkan.Window.Present(ITexture texture, ImageCrop crop, Action swapBuffersCallback) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.Graphics.Vulkan\Window.cs:line 344
   at Ryujinx.Graphics.GAL.Multithreading.CommandHelper.<>c.<InitLookup>b__5_1[T](Span`1 memory, ThreadedRenderer threaded, IRenderer renderer) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.Graphics.GAL\Multithreading\CommandHelper.cs:line 43
   at Ryujinx.Graphics.GAL.Multithreading.ThreadedRenderer.RenderLoop() in D:\a\Ryujinx\Ryujinx\src\Ryujinx.Graphics.GAL\Multithreading\ThreadedRenderer.cs:line 144
   at Ryujinx.Graphics.GAL.Multithreading.ThreadedRenderer.RunLoop(ThreadStart gpuLoop) in D:\a\Ryujinx\Ryujinx\src\Ryujinx.Graphics.GAL\Multithreading\ThreadedRenderer.cs:line 113
   at Ryujinx.Ava.AppHost.RenderLoop() in D:\a\Ryujinx\Ryujinx\src\Ryujinx\AppHost.cs:line 925
   at System.Threading.Thread.StartCallback()

Reproduction steps

  1. Play through the game until you beat Chapter 6.
  2. Once on the world map, there should be a path that goes along the left side of the world map, follow that path to a new sub-world map
  3. Begin the Divine Paralogue - The Ancestor
  4. Do as many fights as possible, enemy reinforcements begin spawning in threes at the bottom of the map after you pass the 2nd ice row in the castle like structure. They will spawn for 35ish turns apparently, and will spawn every 3 turns. Fight every single one.
  5. Eventually it may crash. If it doesn't crash before the end of the chapter, then I believe you avoided it.

Log file

[Ryujinx_1.1.1291_2024-04-28_23-14-08.log] (https://github.com/Ryujinx/Ryujinx/files/15145803/Ryujinx_1.1.1291_2024-04-28_23-14-08.log)

OS

WIndows 11

Ryujinx version

1.1.1291

Game version

2.0.0

CPU

Ryzen 5800X

GPU

Nvidia 4070 - Driver 551.86

RAM

32GB

List of applied mods

No response

Additional context?

You will need the Expansion Pass DLC for the title to play on the exact map I was playing on.

Unknown if this is a factor currently, but I was using the Borderless Gaming application (found on Steam) to have Ryujinx as a borderless window. I'll play without it borderless for a bit at a later date and update if that made a difference.

@Zakarini Zakarini added the bug Something isn't working label Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant