Project

General

Profile

Actions

Emulator Issues #13453

closed

Trauma Team: Skeleton bug (Demons & Death mission)

Added by KAGE-008 10 months ago. Updated 10 months ago.

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

0%

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

Description

Game Name?

Trauma Team

Game ID? (right click the game in the game list, Properties, Info tab)

SK3EEB

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

[Put MD5 Hash here]

What's the problem? Describe what went wrong.

According to the wiki page for this game, it has an issue with the skeleton graphics (noticeable in the mission '7-7: Demons & Death') which is apparently caused by a very old commit back before 4.0 was released, specifically 3.5-594 ([[https://dolphin-emu.org/download/dev/8d5299c20b69f524b20a8d9451aaf754b36690cc/]]). The issue is that certain parts of the skeleton aren't properly rendered no matter which settings you use, especially the skull that is invisible. As that mission is very late in the game (technically near the end), I have attached a save file where all levels are unlocked and accessible.

What steps will reproduce the problem?

  1. Open the game and load the attached save.
  2. In game, select mission 7-7 'Demons & Death' and choose the second option that lets you skip pre-mission cutscenes.
  3. Progress as normal until you reach the part where you have to examine the skeleton.

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. I did test on the very latest build and the issue is still there. For reference I also used 5.0-19141 and 5.0-20778 which are my 'daily driver' builds.

Is the issue present in the latest stable version?

As it is impacting all builds from 3.5-594 onwards, yes.

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

3.5-594

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

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

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

AMD Ryzen 5 3500U, Radeon Vega 8 iGPU, Windows 10 Pro 22H2, all drivers are up to date as well.

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

I have attached a full save for the game which has the aforementioned mission unlocked.


Files

534b3345.zip (6.73 KB) 534b3345.zip Trauma Team save file KAGE-008, 01/15/2024 01:05 AM
SK3EEB-1.png (329 KB) SK3EEB-1.png Proper rendering of skeleton KAGE-008, 01/15/2024 01:05 AM
SK3EEB-2.png (333 KB) SK3EEB-2.png Skeleton bug KAGE-008, 01/15/2024 01:17 AM
panicalert.png (162 KB) panicalert.png OatmealDome, 01/15/2024 04:06 AM
traumateam.dff.zip (1.26 MB) traumateam.dff.zip OatmealDome, 01/15/2024 04:06 AM
SK3EEB on 19141.PNG (731 KB) SK3EEB on 19141.PNG KAGE-008, 01/15/2024 03:55 PM

Related issues 4 (1 open3 closed)

Related to Emulator - Emulator Issues #13136: Vertex Explosion in Pocoyo RacingFixed

Actions
Related to Emulator - Emulator Issues #10312: VertexManagerBase.cpp:95 E[Video]: Too little remaining index values. Use 32-bit or reset them on flush. (non-fatal)Fixed

Actions
Related to Emulator - Emulator Issues #6135: Super Mario Sunshine Grass Broken by Vertex Loader CleanupFixed

Actions
Related to Emulator - Emulator Issues #13456: VertexManager MAXVBUFFERSIZE panic alert when using Metal backendNew

Actions

Updated by OatmealDome 10 months ago

The skeleton appears to be rendering correctly for me, but I do get a bunch of panic alerts from the vertex loader ("buffer not large enough for all vertices", "increase MAXVBUFFERSIZE").

I've attached a FIFO log and a screenshot of the error.

Specs:

macOS 14.2.1, Dolphin 5.0-20586, Metal backend

MacBook Pro 16" (2019), Intel i9-9880H, AMD Radeon Pro 5500M

Actions #2

Updated by pokechu22 10 months ago

  • Related to Emulator Issues #13136: Vertex Explosion in Pocoyo Racing added
  • Related to Emulator Issues #10312: VertexManagerBase.cpp:95 E[Video]: Too little remaining index values. Use 32-bit or reset them on flush. (non-fatal) added
  • Related to Emulator Issues #6135: Super Mario Sunshine Grass Broken by Vertex Loader Cleanup added
Actions #3

Updated by pokechu22 10 months ago

  • Regression start set to 3.5-594

I'm unable to reproduce using the attached fifolog (I don't own the game so that's the only way for me to test). I also can't reproduce the panic alert (though OatmealDome told me that it only happens with the metal backend (which only exists on OSX)).

I do see that the skeleton consists of 65535 vertices followed by 19209 vertices, which is a lot, but I thought we had fixed the relevant issues (in particular #13136 was fixed in 5.0-18171 / https://github.com/dolphin-emu/dolphin/pull/11402).

Can you upload your Dolphin.ini and GFX.ini files? Maybe the issue is caused by a specific setting somehow.

Actions #4

Updated by pokechu22 10 months ago

  • Regression changed from No to Yes
Actions #5

Updated by KAGE-008 10 months ago

Turns out my 5.0-19141 instance (with portable.txt to avoid any conflicts) gives proper rendering of the skeleton, as shown below. Looks like the commit in 18171 fixed it after all.

Actions #6

Updated by KAGE-008 10 months ago

Btw, 'as shown below', I meant the attached screenshot. But yeah, it can be closed now :)

Actions #7

Updated by OatmealDome 10 months ago

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

Thanks for the update. I'll open a separate bug for the Metal issue.

Actions #8

Updated by OatmealDome 10 months ago

Actions

Also available in: Atom PDF