Project

General

Profile

Emulator Issues #11857

GFEE01 hangs at startup with dualcore enabled since 5874 (hybrid xfb)

Added by LinusOrLucy 7 months ago. Updated 7 months 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?

Fire Emblem: Path of Radiance

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

GFEE01

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

4098af6d672eeae8749f9da67309c537

What's the problem? Describe what went wrong.

Starting at 5.0-5874 (introducing Hybrid XFB), this game does not get past the first few frames on my machine (Windows 10, GTX 1070, i7-6700K).

What steps will reproduce the problem?

  1. Start GFEE01; the first few frames of the health warning (not my image) show up: sometimes "Press any button to continue" begins showing up, sometimes after about 20-30s, a slew of frames plays before we get stuck.
  2. Stuckness manifests as FPS stuck at 30, VPS at ~60. After about 20s, FPS drops to 0 and no further progress seems to occur.

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 (10912)

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

5874

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

Fifolog attached (note that this didn't record on a few attempts), indicating that although the game gets stuck, it's not until a few frames in.

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

Processor Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4001 Mhz, 4 Core(s), 8 Logical Processor(s)

GPU NVIDIA GeForce GTX 1070
Driver Version 26.21.14.3630

Windows 10.0.18362 Build 18362

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

I tested this with default settings. In the logs, I noticed a bunch of:

videobackends\ogl\render.cpp:121 W[Host GPU]: id: 20052, source: API, type: Performance - Pixel-path performance warning: Pixel transfer is synchronized with 3D rendering.

leading up to

06:15:802 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: ---------WARNING : HANG AT HIGH WATERMARK----------
06:15:804 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: GP status 001100 --> GP is in unknown state.
06:15:804 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: Halting program in "DEMOInit.c" on line 806.
06:15:804 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 
06:15:804 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: Address:      Back Chain    LR Save
06:15:805 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x8031d9a0:   0x8031da30    0x802060e8
06:15:805 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x8031da30:   0x8031da40    0x8006e548
06:15:805 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x8031da40:   0x8031dd38    0x8020fe78
06:15:805 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x8031dd38:   0x8031dd60    0x8020832c
06:15:805 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x8031dd60:   0x8031dd68    0x800b4c44
06:15:805 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x8031dd68:   0x8031dea8    0x800b4c44
06:15:805 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x8031dea8:   0x8031deb8    0x800b50f4
06:15:805 core\hw\exi\exi_deviceipl.cpp:302 N[OSREPORT]: 0x8031deb8:   0x00000000    0x8020a740

I also bisected releases to determine that this issue was introduced at 5874. Note that I had no issues with dualcore enabled on earlier versions, so although this issue has the same fix as #7143, I believe it to be a distinct instance of some regression. In addition, CPU utilization is pretty low when this occurs (<6%).

log.dff (1.15 MB) log.dff LinusOrLucy, 09/16/2019 02:25 AM

History

#1 Updated by LinusOrLucy 7 months ago

Correction to reproduction point #2: "Stuckness manifests as FPS stuck at 0, VPS at ~60"

#2 Updated by Techjar 7 months ago

Nope, this isn't really a regression, just another dual core timing issue. Dual core is inherently unstable, so just about anything can cause the behavior to change.

Also available in: Atom PDF