Project

General

Profile

Actions

Emulator Issues #10747

closed

[Build 5968+] Multiple issues with Vulkan

Added by Der_Siebte_Schatten over 6 years ago. Updated over 6 years ago.

Status:
Invalid
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:

Description

Game Name?

For the first issue, all GameCube BIOS (PAL, NTSC-U and NTSC-J)
For the second issue, at least TimeSplitters 2 and TimeSplitters: Future Perfect

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

TimeSplitters 2 : GTSP4F
TimeSplitters: Future Perfect : G3FF69

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

GameCube BIOS:

  • PAL : 85e7f7fdeff9fa6ecb52aa0a38cd2eb4
  • NTSC-J : 00cff6ae2938bb37ef355385add3dc16
  • NTSC-U : fae2b558ffc344467170520d62177e5c

Games:

  • TimeSplitters 2 : f1a546493a43a75513f842e0e55e51db
  • TimeSplitters: Future Perfect : 0e451d7f41d5d5843fd666c6f07a8537

What's the problem? Describe what went wrong.

Issue n°1:
With Vulkan selected, Dolphin will crash instantly when loading the GameCube BIOS, either for the main menu or for the startup animation. Works by bypassing the animation (selecting the "bypass main menu" option) or using other rendering engine (Direct3D 11 for example).

Issue n°2:
On some games (at least the two TimeSplitters), with Vulkan selected, an infinite loop of error message "Failed to send command buffer" will show up during the initial game loading. Does not show up with another rendering engine as well.

What steps will reproduce the problem?

Both issues can only be reproduced with Vulkan selected.
Starting with build 5968, start the GameCube main menu or enable the startup animation for the first issue.
For the second issue, start one of the two TimeSplitters games without the startup animation and wait the game to fully loads.

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: Build 6105

Is the issue present in the latest stable version?

No (as Vulkan is not supported on version 5.0 stable).

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.)

Build 5968 (as stated there: https://forums.dolphin-emu.org/Thread-build-5968-new-issues-with-vulkan)

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

Laptop: MSI GE72-2QF Apache Pro
CPU: Intel Core i7 5700HQ @2.7GHz (3.5GHz in turbo mode)
GPU: Intel Graphics 5600HD + nVidia GTX970M (selected for Vulkan)
RAM: 16 GB DDR3 Kingston
HDD: 128GB SSD + 1TB HDD
OS: Windows 10 Professional x64 Build 16299 (Insider Preview, ring Release Preview)

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

Graphics Configuration:

  • Backend: Vulkan (experimental)
  • Adapter: nVidia GTX970M
  • Aspect Ratio : Force 16:9
  • Internal resolution: 3x native resolution (1080p)
  • Anti-Aliasing: 4x MSAA
  • Anisotropic Filtering: 8x
  • Ubershaders: Hybrid
  • Post-Processing Effect: Off
  • All other options are in default settings, except Vertex Rounding (On)

Issue n°1:
Windows Error Reporting log on this issue
(See Screenshot "Capture.PNG")

Material errors, logged alongside with some of the Dolphin's bugs (not every time)
(See Screenshot "Capture2.PNG")


Files

Capture2.PNG (32.5 KB) Capture2.PNG Material error, logged with some of the Dolphin crashes Der_Siebte_Schatten, 12/30/2017 12:51 AM
Capture.PNG (36.4 KB) Capture.PNG Windows Error Reporting log on Dolphin crash Der_Siebte_Schatten, 12/30/2017 12:51 AM
Actions #1

Updated by Der_Siebte_Schatten over 6 years ago

I forgot to mention, for issue n°2, that the only way to exit Dolphin when in this loop is to terminate the program with Windows's Task Manager.

Actions #2

Updated by Stenzek over 6 years ago

There's a known issue (possible driver bug) with the NVIDIA + Vulkan + MSAA combination. Does it still break if you disable MSAA?

Actions #3

Updated by Helios over 6 years ago

  • Status changed from New to Invalid

I feel really bad for saying this considering how much effort you put into this report, but we need one issue per report. Can you submit these as different issues?

After trying what Stenzek suggested

Actions #4

Updated by Der_Siebte_Schatten over 6 years ago

Helios wrote:

I feel really bad for saying this considering how much effort you put into this report, but we need one issue per report. Can you submit these as different issues?

After trying what Stenzek suggested

Well, at least I'll have just to copy/paste...

Actions

Also available in: Atom PDF