search

cai567890 / pcsx2

Automatically exported from code.google.com/p/pcsx2
1 stars 0 forks source link

Stuntman NTSC-U has massive gfx issues and unplayable speeds #1132

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
1) Did the game ever work correctly (i.e. not have this problem) on the
Official PCSX2 build or an earlier version of PCSX2 playground?
(If so, please specify the latest pcsx2-playground or Official revision
that last worked.)
I don't believe so. Many others have reported the same issues with this game.

2) What steps will reproduce the problem?
1. Launch the game 
2. Attempt to enter gameplay

3) What exactly happens when you experience this issue (listing any console 
errors or screen output you receive)?
FMV slows down to about 1 FPS (in Hardware mode) with massive gfx issues 
(software/hardware). Once in gameplay, correct gfx can be acheived only be 
entering software mode AND turning off mipmaps with INSERT key. FPS is about 
5-10, even on a Sandy bridge. 

4) What version of PCSX2 are you using? On what operating system? Plugins?
Default setup (gfx=GSDX)
Win7 x64

5) Please provide any additional information below.
Screenshot of what gfx look like:
http://imageshack.us/photo/my-images/402/unledjvb.jpg/

Original issue reported on code.google.com by wespipe...@gmail.com on 4 Sep 2011 at 5:20

GoogleCodeExporter commented 9 years ago 
Altho its likely to look even worse, can you try ZeroGS for me?

Original comment by refraction on 4 Sep 2011 at 10:58

GoogleCodeExporter commented 9 years ago 
Looks about the same (with default settings), though that intro scene is 
faster. I referred to it as a FMV earlier - it's not, the FMV is fine. It's 
just when you actually get into the level and the models are first being 
rendered that everything starts to crawl and nothing is displayed correctly.

Here's another shot of how gameplay looks.
http://imageshack.us/photo/my-images/199/unledfpm.jpg/

Original comment by wespipe...@gmail.com on 5 Sep 2011 at 5:39

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hmm looks like it was made by the same folks as driver parallel lines, the 
issues sound very similar too. I'm afraid there isn't much of a solution 
currently but mtvu speedhacks helps a bit

Original comment by refraction on 5 Sep 2011 at 2:09

GoogleCodeExporter commented 9 years ago 
Just wanted to update the post and let you know nothing has changed with this 
game - gfx are not drawn properly and game runs @ 2 fps in hw. Needs software + 
disable mipmaps (del key), but of course in a 3d racing game has unplayable 
speeds with that setup.

Is there any new settings/hacks released in the past here that could help this 
that I can test out?

Original comment by wespipe...@gmail.com on 23 Jun 2012 at 8:22

GoogleCodeExporter commented 9 years ago 
Also, I saw on the compat list the pal version is fine. Could that be true? 
Seems like this issue would be regardless of game region. But let me know if 
so, I can find one on amazon or something. Thanks!

Original comment by wespipe...@gmail.com on 23 Jun 2012 at 8:33

GoogleCodeExporter commented 9 years ago 
It looks like the Europe version is the same as NTSC, however it is playable 
with GSDX in software mode, but VRAM usage is massive, so it's still slow.  
Slowly Playable :P

Marking as a GSDX issue, although it might not be.

Original comment by refraction on 21 Aug 2012 at 7:07

GoogleCodeExporter commented 9 years ago 
Game broken completely by r5367-5371 - one of those five revs causes the game 
to not go in-game after opening cutscene - probably r5368. Worked "normal" in 
r5366. 

Along with that, some of the menu 2d gfx are corrupted - text on first boot 
screen, disc icon during load screen. Every version since has these new gfx 
bugs and freeze upon entering gameplay. We're going the wrong direction here! 
:P

Original comment by wespipe...@gmail.com on 7 Sep 2012 at 5:53

GoogleCodeExporter commented 9 years ago 
Can you see what happens with the EE timing gamefix and also the DMAC busy 
gamefix?

Original comment by ramapcsx2 on 7 Sep 2012 at 6:44

GoogleCodeExporter commented 9 years ago 
On latest build, no change with DMAC fix. With EE fix, the boot text is fixed 
(disc icon not) and we actually go in game, but then it still freezes a few 
seconds in (software or hardware). So the PCSX2 EE is still not working 
properly with this game, especially in recent builds.

Original comment by wespipe...@gmail.com on 8 Sep 2012 at 6:45

GoogleCodeExporter commented 9 years ago 
Just wanted to report this issue still persist. No change in the past year.

Original comment by wespipe...@gmail.com on 19 Oct 2013 at 6:03

GoogleCodeExporter commented 9 years ago 
All the same with r5875. The new PCSX2 1.2.1 doesn't fix any of the problems 
with this game.

Original comment by theportu...@gmail.com on 17 Mar 2014 at 8:11

GoogleCodeExporter commented 9 years ago 
i have the same problem.. so it's doesn't work or i can fix the problem?

Original comment by Lesc...@hotmail.it on 19 Apr 2014 at 11:04