Project

General

Profile

Emulator Issues #11564

Resident Evil 3 Lock UP

Added by shatteredlites 8 months ago. Updated 5 months ago.

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

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]

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

History

#1 Updated by shatteredlites 7 months ago

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

#2 Updated by JMC4789 6 months ago

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

Yeah, confirmed.

#3 Updated by JMC4789 6 months ago

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

#4 Updated by Kribuchman 5 months 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)

#5 Updated by shatteredlites 5 months 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.

#6 Updated by JMC4789 5 months 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.

Also available in: Atom PDF