Project

General

Profile

Actions

Emulator Issues #4001

closed

007 Nightfire crash

Added by essendonfc18 almost 14 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
JIT
% 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

What's the problem?
The game crashes after the first mission's loading screen, cannot advance further in the game.

Dolphin version with the problem (as it appears in the title bar, Ex.: "R
4779" or "R 6403M"): R 6916

(optional) Dolphin version that does not have the problem:

Operating system and version:
32-bit or 64-bit: 32-bit

Game ID (as it appears in game properties, Ex.: "GZ2P01" or "RSBE01"):
GO7E69

Build command-line (not on Windows):

Was the ISO a plain dump from disc, compressed and/or scrubbed?
Um, not too sure?

Please provide any additional information below.
You cannot play any part of the game, as when you first start the game without a save file, you go straight to the first mission without going to the main menu.

Actions #1

Updated by DimitriPilot3 almost 14 years ago

AFAIK, the workaround is to use the JITIL recompiler instead of JIT. If it works, then it is likely a JIT-only issue...

(Make sure not to press the START button when you're in that first mission, by the way)

Actions #2

Updated by aavindraa almost 14 years ago

Yeah JITIL will help you get past that part. After you've unlocked other levels, you can switch back to JIT.

Still an issue though, this shouldn't be closed.

Actions #3

Updated by DimitriPilot3 almost 14 years ago

I just found out, in debug mode (Dolphin.exe -d), that disabling the JIT-ing of "LoadStore Floating" instructions is enough to prevent the (regular) JIT recompiler from crashing when going into the first (prelude) mission.
That sounds about right, as the "common\TuningVars.txt" file (in INI format?) in the ISO (filesystem) contains a lot of floating point values... :P

The culprit instruction is Jit64::stfd(), as sl1nk3.s figured out in issue 2442. Commenting the "if (js.memcheck)" code block to "disable" that instruction solves this problem.

Actions #4

Updated by DimitriPilot3 almost 14 years ago

  • Category set to jit
Actions #5

Updated by skidau almost 13 years ago

  • Status changed from New to Fixed

This issue was closed by revision 67e38fb6c654.

Actions #6

Updated by skidau almost 13 years ago

This issue was closed by revision daf7e965219e.

Actions

Also available in: Atom PDF