Emulator Issues #13060
closed
Failed to submit command buffer
0%
Description
Game Name?
At least 2 different Games - Nintendo Puzzle Collection amd NASCAR Thunder 200. I do have a few other games on if you need more to test (Dirt to Daytona, NAscar 2011,
Dr. Mario Online Rx, and NASCAr 2005: Chase for the Cup)
Game ID? (right click the game in the game list, Properties, Info tab)
(GPZJ01 for NPC, GNCE69, for NAscar Thunder 2003)
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
4409437f76675190d221b36e848eaa86 for NPC, 2ff456ea48e6799655d179fa84784f95 for Nascar Thunder 2003
What's the problem? Describe what went wrong.
I get the "Failed to submit command buffer" issue
What steps will reproduce the problem?
for NPC, I did the first level for Panel de pon, and did a race at bristol for NT03
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes, was tested with 5.0.17499 and 5.0.17508
Is the issue present in the latest stable version?
[Yes/No and version number here]
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
I believe it was in 5.0.17499, as I didn't have an issue beforehand.
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
No GPU issues.
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel i5 11400F, RX 550 2GB, 12GB 3200MHz RAM, windows 11
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
[Anything else here]
Updated by FireNX70 over 1 year ago
I'm having the same problem, I've been playing F-Zero GX and it also happens there. It's not an AMD/Win11 specific issue either, since I'm on NVidia and Win10. It started before 17499 as I started experiencing this when I updated from 17467 to 17491. It's particularly annoying that it seems to happen at random as it would make bisecting a pain in the ass.
Updated by pokechu22 over 1 year ago
Also, can you enable the video log and set the level to "error" (or to "info"), since more information should be present there when the issue happens?
Updated by FireNX70 over 1 year ago
As much as 5.0-17499 would make sense, I went 17467 -> 17491 -> 17536 and I know for a fact this was already happening before 17536.
I just checked the dates on my downloads folder and found that I downloaded the latest NVidia driver right after downloading 17467, and I remember installing it because I thought it might be the driver so it must have actually already been a thing by 17467. Before that I was on 17403 and I don't remember having that problem, although I don't know how much I really used that build.
As for logging; I got it working but I have no idea how long it might take to get the error again, since this seems to happen at random.
Updated by moo925 over 1 year ago
I would also add that I just tested 5.0.17538, and after having a 9 second Think on Super Hard for Panel De Pon, it still happens, it came up before I was going to face Pure.
Windows 11 was also updated to the 22H2 version as well just before playing on 5.0.17499.
Updated by moo925 over 1 year ago
17549: still has the same issue with a VK_ERROR_OUT_OF_DEVICE_MEMORY (-2) now, which is clearly false, only using 34% right now of 12GB RAM with this Google Chrome Window open (6.8GB Comitted).
Updated by pokechu22 over 1 year ago
Note that it would probably be out of graphics card memory and not general memory - you might be able to see this in task manager if you select the GPU itself on the performance tab.
Updated by moo925 over 1 year ago
Nope, it was only usng 0.4-0.5GB when it happened, nothing seemed out of the blue when the message came up.
Updated by moo925 over 1 year ago
17569 seems to have fixed the issue, case closed.
Updated by JMC4789 over 1 year ago
- Status changed from New to Fixed
- Fixed in set to 5.0-17569
Thanks!