Game-compatibility: 454107D9 - Need for Speed Most Wanted (2005)

Created on 30 Jun 2016  ·  35Comments  ·  Source: xenia-project/game-compatibility

Marketplace

Tested on (https://github.com/benvanik/xenia/commit/3d1d4dea47dd95117befe436ed292ad79ca5ee13)

Issues:

After intro movies, the game crashes after trying to press A to continue.

Log:

Log file

Screenshot(s):

0001
0003
0004
0009
0011

Labels:

(state-intro)

cpu-timing gpu-readback state-gameplay tech-engine-eagl

Most helpful comment

@DiamondMaster07 As far as I've investigated, the HDR shader still doesn't work correctly during the NIS, it just gets minimized when the depth of field effect is present. The DOF itself doesn't apply even though it used to in OpenGL, here's an old screenshot with it working correctly

xenia 2016-09-27 03-17-13-79

All 35 comments

I managed to bypass the initial crash and stay ingame by setting the timescale to 4x. It also has to be turned down to 2x or less before the videos or they get stuck. Always crashes after taking control of the car.
Video: https://www.youtube.com/watch?v=waha-75R6Ig
A screenshot of quick race:
xenia 2016-09-13 20-09-16-94
Graphical issues: fake HDR shader constantly maxed out, no car reflections, car shadow texture rendering partly, messed up interface.
@Razzile label as gameplay and gpu-shader-errors

I'm 2 weeks late but here're the logs anyway
OpenGL (warning, enormous)
Vulkan (crashes on startup for some reason)

I don't know if it's a good thing or a bad thing, but crashing takes much longer on https://github.com/benvanik/xenia/commit/8ccefa160076c13a1cb4e2a8e1d7fc7e254a6b4b. Freezes on taking control over car, then waits, then crashes. This was the first time it happened(atleast for me)

Log:
xenia.txt
Running from default.xex itself and not from an iso

GREAT PROGRESS!
Tested on: https://github.com/benvanik/xenia/commit/1e9786eae395ef09de81e82d1c13d6426c7dc6c5
Game does not crash when taking over control a car!
HUD is not visible
The 4x timescale trick still needed
And I'll try to finish a race(didn't crashed, I quitted)
And I'll try to record a video

Video about gameplay(quick race): https://youtu.be/bCEbDGHgNN0
Forgot to send the log file(and I won't do a race again today, sorry)
@Deathlock47 Try to get to the carrer mode. I couldn't(I don't know what to press)

@DiamondMaster07 Yep, everything works now
xenia 2017-05-15 16-05-14-81

@Deathlock47 How can you go to the career mode? I tried everything but I'm stuck, I know the menus are functional, I just don't know what to press in what order.

Edit: I've found out what causes the 4x timescale bug. World updates! If you set it down to 1x, you can stay ingame as long as you don't update the world(load a new chunk).
Also, I've figured out how to get into career mode.
And another thing. If you put the devbuild xex file to the retail files, you can enable debug menu which appears as broken as any other hud elements, but at least it loads.

@DiamondMaster07 Not really. You need to modify that devbuild xex as I did, it's way bigger and it's rebuilt for retail X360.

@Deathlock47, nice to meet you, my old heli fan :P

@osdeverr Glad to see you too fella. How did you modify the dev xex so it doesn't crash?
Btw any of you had success booting on Vulkan? I still get an instant crash to this day

Vulkan still crashes for me
Osdever can't test Xenia cuz his cpu is not compatible with xenia

Tested on: https://github.com/benvanik/xenia/commit/2cf0b39bf5454ffee8055ad33d92f6ff991a1c8f
Game now has an issue with textures, only car model's textures load.
desktop 08 08 2017 - 16 18 39 07
desktop 08 08 2017 - 16 18 25 06
desktop 08 08 2017 - 16 17 48 05
desktop 08 08 2017 - 16 17 42 04
desktop 08 08 2017 - 16 17 35 03
desktop 08 08 2017 - 16 17 27 02

Tested on (https://github.com/benvanik/xenia/commit/09c29bbdc5167347268f6a78163f30a09032ef1a)

Screenshots (OGL)

desktop 08 10 2017 - 16 15 58 08 mp4_snapshot_06 07_ 2017 08 10_21 19 14
desktop 08 10 2017 - 16 15 58 08 mp4_snapshot_06 51_ 2017 08 10_21 19 25

btw as i can see normal maps are borken @Parovozik

Tested on: https://github.com/xenia-project/xenia/pull/789
Vulkan works, same issues as OpenGL, but HUD renders correctly, half of the screen is no longer covered and runs on a better FPS.
Here's a video using the devkit version of the game(no gameplay/graphical differences, only a developer menu) https://youtu.be/ybkcVgWyrvU

However, Vulkan crashes on https://github.com/xenia-project/xenia/commit/2a3c66484e818364e321bab4f3bf00e5851c6f19

@DiamondMaster07 that doesn't make any sense as between 957 and 958 the only change was to the doc files

L I T

btw it was me who made the devbuild work shameless self-promotion

Thanks to @Parovozik (https://github.com/benvanik/xenia/issues/799) I managed to stay ingame with 1x timescale by removing every sound file from the game.
Video: https://youtu.be/hU_UwIi3HA8

@Razzile I tested it multiple times, https://github.com/xenia-project/xenia/commit/2a3c66484e818364e321bab4f3bf00e5851c6f19 broke something and Vulkan crashes on this build while https://github.com/xenia-project/xenia/pull/789 works just fine

@DiamondMaster07 What software you used for remove game files? I see there specific archives :)

Goes ingame on Vulkan again
Now shadows work properly, however the lower part of the screen frequently turns white
144
153

desktop screenshot 2017 12 23 - 21 58 15 48
desktop screenshot 2017 12 23 - 21 58 06 52
Here're some screenshots with VisualLookFilter turned off

Also sometimes the lower half of the screen freezes for some seconds

In short: Vulkan now has all the visual bugs except for the HUD that OGL has and has worse framerate than on 1.0.957

Some findings: when a NIS plays. the lightning is correct
Prologue NIS
desktop screenshot 2018 01 27 - 17 45 50 50
desktop screenshot 2018 01 27 - 17 46 22 70
Race intro NIS
desktop screenshot 2018 01 27 - 19 13 13 53

Here's a video showing correct lightning when a NIS plays, then showing broken lightning, when going ingame: https://youtu.be/2j_kbcZ6k-s

Also, when a frame breaks, shaders still apply(also seen in the video)
desktop screenshot 2018 01 27 - 17 45 56 48
This is the reason why half of the picture goes white sometimes(broken shaders)
desktop screenshot 2018 01 28 - 14 45 09 84

Tested on https://github.com/benvanik/xenia/commit/e4bc5968870f55cbebedb0aba5a5cb30a1962fa3
Previously bugged half-frames now cover the entire screen and are black, resulting in covering the whole 3D part of the garage menus and black flashes ingame

@DiamondMaster07 As far as I've investigated, the HDR shader still doesn't work correctly during the NIS, it just gets minimized when the depth of field effect is present. The DOF itself doesn't apply even though it used to in OpenGL, here's an old screenshot with it working correctly

xenia 2016-09-27 03-17-13-79

Tested on Xenia-DX12 (https://github.com/xenia-project/xenia/commit/d827bbeb6cc5bd2120350e9dc0c4998a8c36a1fe)
Log:
NFS MW DX12.log
Goes ingame but some lighting troubles:
bandicam 2018-10-05 03-37-34-385
bandicam 2018-10-05 03-38-26-106
bandicam 2018-10-05 03-38-51-618

Tested on https://github.com/xenia-project/xenia/commit/90c9c24ca5a5664789729df26071c2498df80f59 with --d3d12_readback_resolve=true

Graphics are emulated perfectly but performance is low
Still has CPU timing issues, free roam and races require to be launched at 0.13X CPU timescale
xenia-2
unknown
unknown

Tested on https://github.com/xenia-project/xenia/commit/5558c8aafefffca68ada82d3d7a389ac8fcedde6

Graphics without using d3d12_readback_resolve=true got a little better, though there are issues with overbright objects (particles, sky, etc)

Also found out that using disassemble_functions=true lets several chunks of audio load after pressing start without using time scale. Although after a new chunk of sfx loaded and played, audio mutes and still won't let go into gameplay. So, time scale x4.00 is still required to get into gameplay.

Showcase

Edit: added video.

Log:

log file

Screenshot(s):

Снимок экрана (41)
Снимок экрана (42)
Снимок экрана (49)
Снимок экрана (47)

GPU>CPU readback needed for correct eye adaptation to brightness.

The shaders are fixed by custom patches but that belongs in Canary (unfortunately)

The "fix" doesn't fix the shaders, it just disables the HDR shader. You get the same results if you decompile the game's files and replace the HDR.fx file with another one.

The "fix" doesn't fix the shaders, it just disables the HDR shader. You get the same results if you decompile the game's files and replace the HDR.fx file with another one.

yeah.. About that.. I got the debug build (don't ask how) and deleted the HDR.fx.. Nothing happened.. Still the same thing bro. And the thing with the brightness bug.. Its called "Bloom"..

The "fix" doesn't fix the shaders, it just disables the HDR shader. You get the same results if you decompile the game's files and replace the HDR.fx file with another one.

yeah.. About that.. I got the debug build (don't ask how) and deleted the HDR.fx.. Nothing happened.. Still the same thing bro. And the thing with the brightness bug.. Its called "Bloom"..

Yes, because the file you deleted is an uncompiled source file. You are supposed to REPLACE the hdr.fx.o file in FX/COMPILED - world.fx.o worked for me, the others either resulted in a black screen or a crash.
And bloom is an HDR effect.

The "fix" doesn't fix the shaders, it just disables the HDR shader. You get the same results if you decompile the game's files and replace the HDR.fx file with another one.

yeah.. About that.. I got the debug build (don't ask how) and deleted the HDR.fx.. Nothing happened.. Still the same thing bro. And the thing with the brightness bug.. Its called "Bloom"..

Yes, because the file you deleted is an uncompiled source file. You are supposed to REPLACE the hdr.fx.o file in FX/COMPILED - world.fx.o worked for me, the others either resulted in a black screen or a crash.
And bloom is an HDR effect.

Worldreflect.fx.o also works for me.. And we need to like lessen the Bloom effect.. Im pretty sure the Bloom is the one that is causing the weird bright shine effect since its a "HDR" effect.. That being an HDR effect means it is somehow tied to the hdr.fx.o file.. Replacng the hdr.fx.o will remove the Bloom.. So yeah.. I am sure that the Bloom is the overbright bug..

Was this page helpful?
0 / 5 - 0 ratings

Related issues

alexis23ange picture alexis23ange  ·  4Comments

benvanik picture benvanik  ·  6Comments

halotroop2288 picture halotroop2288  ·  3Comments

PhanHongAn0105 picture PhanHongAn0105  ·  7Comments

TotalCaesar659 picture TotalCaesar659  ·  4Comments