Stuntman [SLES 50288] (E)

[Nachbrenner]

status=4;
version=1.7.0;
console=PS2;
crc=790a4acb;
img_t=1161438294j015;
img_f=1161438288j015;
wikiurl=Link;

Code:

empty

[FlatOut]

PC Specs:

CPU: Intel Core2Duo @ 3.4Ghz
GPU: AMD Radeon HD6000 @ 2GB

Build Description: PCSX2 1.2.1 Stable release - Windows
If other please specify:
pcsx2 v1.3.1-934 Git - Windows

BIOS Used: Europe v02.00 Console

EE/VU Clamp modes: Normal/Normal

Speedhacks Used:
Default & Off

Gamefixes Used:
Automatic

Amount of testing done (little/medium/much/completed-game):
Little

Comments:

• Works fine, except gameplay runs at just 20fps in Hardware mode. Game even runs a few fps higher in Software mode. Speedhacks don't help, or make things worse.
  

• In Git build turning on Accurate Date will crash the game at the end of loading a level.
  

Bugs:

• In Hardware mode there are graphical distortions to textures. There's no known solution, use Software mode instead.
  

• With Direct3D9 Hardware renderer the screen during gameplay appears darker than usual and the number of graphical issues increases (more so in stable release). There's no known solution, use one of the other Hardware renderers or use Software mode instead.
  

Status:
Playable
(Software mode status: Excellent)

[shideravan]

PC Specs:

CPU: Intel® Core™ i7-4790
GPU: NVIDIA GeForce GTX 1070

Build Description: PCSX2 V1.7.0-dev-2741
If other please specify: N/A

BIOS Used: USA v01.60(07/02/2002) Console

EE/VU Clamp modes: Normal/Normal
EE/VU Rounding: Chop/Chop

GSdx Settings: Software, Bilinear (Forced excluding Sprite)

GSdx HW Hacks: None

Speedhacks Used: None

GameFixes Used: Assumed to be automatic.

Amount of testing done (little/medium/much/completed-game): medium

Comments:

Using hardware mode works only if using a low upscaling (eg.: 2X). Looks perfect in software mode.

Driv3r (U/E) also has similar issues probably due using the same game engine.

Bugs:
In hardware mode (eg.: Vulkan) it uses a lot of VRAM. I can use hardware mode just with low upscaling (eg.: 2x), but some graphical problems happens.

Status: In-game

[refraction]

This game has AI pathing issues, it is not "playable"

[Chern40_7]

PC Specs:
CPU: Intel® Pentium® CPU G2030 @ 3.00GHz
GPU: PALIT GeForce GT 1030 @ 2 GB


OS:Windows 10 Home x64
Build Description: PCSX2 Nightly - v1.7.2564 Release Pack - Windows 


If other please specify: N/A


BIOS Used: Europe v02.00(14/06/2004) Console


EE/VU Clamp modes: Standard
EE/VU Rounding: Standard


Speedhacks Used:
* VU Cycle Stealing: 2
* MTVU


Gamefixes Used: N/A


Amount of testing done (little/medium/much/completed-game):
Little


Comments:
The game runs at 20/25 FPS.


Bugs:
In fact, this game really suffers from graphical bugs and buggy AI in four levels and is likely to be fixed in the distant future.


Status:
InGame

[hmgc2002]

PC Specs:
CPU: AMD Ryzen 5 7520U @ 2.80GHz
GPU: AMD Radeon™ 610M


OS:Windows 11 Home x64
Build Description: PCSX2 Nightly - v1.7.5201 Release Pack - Windows 


If other please specify: N/A


BIOS Used: Europe v02.00(14/06/2004) Console


EE/VU Clamp modes: Standard
EE/VU Rounding: Standard


Speedhacks Used:
* VU Cycle Stealing: 2
* MTVU


Gamefixes Used: N/A


Amount of testing done (little/medium/much/completed-game):
Little


Comments:
The game runs at 30fps in hardware mode, with heavy slowdowns in some parts(specially explosion/fire effects). Otherwise, it runs perfectly in software mode.


Bugs:
The game has some graphical bugs, and is unplayable after the first level of "A whoopin' and a hollerin'", because of the AI pathing. It is still an issue and won't likely be fixed for a long while.


Status:
InGame