Emulator Issues #4106
closedCannot push any box in Resident Evil 1 when build using default project settings.
0%
Description
What's the problem?
Cannot push any box in Resident Evil 1 when build using default project settings.
Dolphin version with the problem (as it appears in the title bar, Ex.: "R
4779" or "R 6403M"):
Dolphin x64 R7175
Operating system and version:
32-bit or 64-bit:
Windows 7 x64
Game ID (as it appears in game properties, Ex.: "GZ2P01" or "RSBE01"):
GBIE08
Was the ISO a plain dump from disc, compressed and/or scrubbed?
gcz
Please provide any additional information below.
Cannot push any box/object in Resident Evil 1 when build latest Dolphin using VC2010 and default settings (ie. floating point model set to fast - /fp:fast).
Changing floating point model to precise (/fp:precise) in Core project resolve this issue.
This video demonstrates issue: http://www.youtube.com/watch?v=ChKznKClo0w
Updated by Anonymous over 13 years ago
When compiled Core project with /fp:precise
Updated by Anonymous over 13 years ago
someone please send me your memory card save file, or upload it somewhere.
Updated by Anonymous over 13 years ago
Updated by irencepn over 13 years ago
tap...@gmail.com can you please compile latest revision for me (with /fp:precise) thx
Updated by Anonymous over 13 years ago
Updated by Anonymous over 13 years ago
- Status changed from New to Accepted
Hey, I noticed this only happens in x64 dolphin. Just wondering if anyone else noticed the same thing...?
Updated by Anonymous over 13 years ago
Seems X64 Dolphin uses Interpreter on some instructions (Default(inst);return;).
Interpreter has some mixed double/float arithmetics, and as written on msdn forum, fp:fast favor float instead of double.
I done now some testing: disabled precompiled headers in Core project then compile whole project on fp:fast except Interpreter_FloatingPoint.cpp - issue gone! So this file seems to be fault this. I reverted changes to my project ad set: #pragma float_control(precise, on) at beginning of Interpreter_FloatingPoint.cpp - issue gone.
So conclusion is that some of interpreted functions that are used only in X64 Jit/JitIL are causing this issue.
Updated by Anonymous over 13 years ago
- Status changed from Accepted to Fixed
This issue was closed by revision r7200.