Project

General

Profile

Actions

Emulator Issues #10212

closed

"failed to submit command buffer" error in Star fox Adventures using Vulkan

Added by carrotfear666 about 7 years ago. Updated over 6 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
5.0-5426

Description

Game Name?

Star fox Adventures

Game ID? (right click the game in the game list, properties, info tab)

GSAE01

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

afb0306454b581e37a62170fdfd1de09

What's the problem? Describe what went wrong.

An error appears when trying to start Star Fox Adventures using the Vulkan backend.
The error pops up and prevents Dolphin from closing. Clicking Okay does nothing.
The only way to close Dolphin at that point is with task manager.

What steps will reproduce the problem?

Start Star Fox Adventures with the Vulkan backend

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

5.0-3326

What are your PC specifications? (CPU, GPU, Operating System, more)

Windows 7, i5, gtx 970

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

I attempted to play the game 3 times. The first time, the error appeared immediately.
The second time, It appeared after several seconds of black screen.
The third time, the same several seconds of black appeared, then the opening video started playing. I didn't go any further than that.


Files

Capture.PNG (31.5 KB) Capture.PNG carrotfear666, 04/14/2017 04:53 PM
Capture.PNG (36.1 KB) Capture.PNG carrotfear666, 04/17/2017 07:33 AM
Actions #1

Updated by Stenzek about 7 years ago

Can you try with PR5270? If you had MSAA enabled, it may be fixed now.

https://github.com/dolphin-emu/dolphin/pull/5270 or if you need a prebuilt version, https://dl.dolphin-emu.org/prs/pr-5270-dolphin-latest-x64.7z

Actions #2

Updated by carrotfear666 about 7 years ago

Stenzek wrote:

Can you try with PR5270? If you had MSAA enabled, it may be fixed now.

https://github.com/dolphin-emu/dolphin/pull/5270 or if you need a prebuilt version, https://dl.dolphin-emu.org/prs/pr-5270-dolphin-latest-x64.7z

Tried again with the latest version of Dolphin and MSAA enabled, all other settings the same. Exact same result.

Actions #3

Updated by Stenzek about 7 years ago

This PR hasn't been merged yet, so if you used the latest git build it won't have these changes included.

Actions #4

Updated by carrotfear666 about 7 years ago

Stenzek wrote:

This PR hasn't been merged yet, so if you used the latest git build it won't have these changes included.

Started it three times. No crash. Though the Nintendo logo at the beginning seems to be off center. It's slightly too far to the right.

Actions #5

Updated by Stenzek about 7 years ago

Could you try recording a fifolog of the game starting with the OpenGL backend (say, 600 frames, 10 seconds at 60hz), and try playing it back in the Vulkan backend and seeing if it crashes?

Open Tools->Fifo player before booting the game, enter the frame count, and hit record, wait, and then save.

If you can get a fifolog that causes the Vulkan backend to reliably error out, that'll help significantly in narrowing down the issue.

Actions #6

Updated by carrotfear666 about 7 years ago

Stenzek wrote:

Could you try recording a fifolog of the game starting with the OpenGL backend (say, 600 frames, 10 seconds at 60hz), and try playing it back in the Vulkan backend and seeing if it crashes?

Open Tools->Fifo player before booting the game, enter the frame count, and hit record, wait, and then save.

If you can get a fifolog that causes the Vulkan backend to reliably error out, that'll help significantly in narrowing down the issue.

Played the OpenGL fifo in Vulkan, no crash.

Actions #7

Updated by Stenzek over 6 years ago

  • Status changed from New to Fixed
  • Fixed in set to 5.0-5426

Pretty sure the MSAA fix should have taken care of this. If the issue is still persisting on the latest master build, please update the issue.

Actions

Also available in: Atom PDF