Project

General

Profile

Actions

Emulator Issues #10068

open

Spyro: Enter The Dragonfly - Pupils missing from Sparx in credits

Added by Fog almost 8 years ago. Updated about 3 years ago.

Status:
New
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?

Spyro: Enter The Dragonfly

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

GS8E7D

What's the problem? Describe what went wrong.

The pupils are completely missing from Sparx's eyes during the credits of the game, which I guess is a metaphor for how bad this game is.

This has been tested on latest master, all the way to 4.0.2, with the same issue occurring on all versions.

What steps will reproduce the problem?

Reach the credits of the game

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-1656

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

I've attached a three-frame FIFO log of the issue.


Files

spyroetd_eyes.zip (735 KB) spyroetd_eyes.zip Fog, 01/31/2017 04:22 PM

Related issues 1 (1 open0 closed)

Related to Emulator - Emulator Issues #9474: Transparent Wiimote graphicAccepted

Actions
Actions #1

Updated by pokechu22 about 3 years ago

Actions #2

Updated by pokechu22 about 3 years ago

This is the same issue as #9474 - the game configures the alpha stage to use dest = prev, but prev is never initialized. This results in unpredictable behavior on hardware (generally using values from whatever was last drawn, in this case the bushes in the background, object 111 in that fifolog). Looking at a longplay the eyes seem to flicker on console, too. There is occasional buggy behavior with the hardware fifoplayer, but most of the time doesn't behave the same as the longplay and various speedruns I found: see https://youtu.be/5-F83yU52rg

There is no easy way of fixing this in the hardware renders, unfortunately. It may be possible to fix with the software renderer.

Actions

Also available in: Atom PDF