Project

General

Profile

Actions

Emulator Issues #11564

closed

Resident Evil 3 Lock UP

Added by shatteredlites about 5 years ago. Updated over 2 years ago.

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

0%

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

Description

[Resident Evil 3 Nemesis]
[GLEE08]
[428abf23e4c06dbfcbd3cea2fa577385]

What's the problem? Describe what went wrong.

[Resident Evil 3 Nemesis fails to load past the point Jill is escaping through a Door in the very begining]

What steps will reproduce the problem?

[Game is broken regardless of renderer or settings]

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

[5.0-9583]

Is the issue present in the latest stable version?

[No]

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

[AMD RX 480 4GB, i5 6402p 8GB, Windows 10]


Files

re3.dff (3.06 MB) re3.dff shatteredlites, 04/02/2019 06:18 AM
Actions #1

Updated by shatteredlites almost 5 years ago

heres a fifo log on dx12 doesn't really matter all backends give the same results

Actions #2

Updated by JMC4789 almost 5 years ago

  • Status changed from New to Accepted
  • Priority changed from Normal to High
  • Milestone set to Current

Yeah, confirmed.

Actions #3

Updated by JMC4789 almost 5 years ago

If you have time, can you bisect to when this behavior started happening?

Actions #4

Updated by Anonymous almost 5 years ago

The game actually progresses correctly with dual core turned on - tested with both master and 5.0. I disagree with OP, this issue seems to be present in 5.0 as well, just need to turn dual core off. Bisected all the way back to 4.0-9154 (https://github.com/dolphin-emu/dolphin/pull/3601)

Actions #5

Updated by shatteredlites almost 5 years ago

Kribuchman wrote:

The game actually progresses correctly with dual core turned on - tested with both master and 5.0. I disagree with OP, this issue seems to be present in 5.0 as well, just need to turn dual core off. Bisected all the way back to 4.0-9154 (https://github.com/dolphin-emu/dolphin/pull/3601)

ill be damned dual core fixes it. surprising to say the least. i was told its best to leave it off since it causes issues.

Actions #6

Updated by JMC4789 almost 5 years ago

It's expected in certain cases due to certain timings being slightly different in single core. Dolphin has shit timings in general, so sometimes jiggling them around works out.

Actions #7

Updated by JMC4789 over 2 years ago

  • Status changed from Accepted to Fixed
  • Fixed in set to 5.0-15579

This is fixed in single core in the latest builds. I merged the duplicate of this issue with the main dualcore issue. Fixed by 5.0-15579

Actions

Also available in: Atom PDF