Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Smackdown vs Raw 2006, 2007, and 2008 titantron problems with 1.6.0
#1
I'm having an issue with the Smackdown vs Raw games on the new PCSX2 1.6.0 update. I noticed that the titantron videos of the wrestlers while playing on 1.6.0 are either just black, no movies are playing or one frame is frozen. Was working fine on 1.4.0. I'm using OpenGL HW but I noticed OpenGL SW didn't fix it. DirectX11 didn't help either. Seems to only be an issue with Smackdown vs Raw 2006, 2007 and 2008. Every other wrestling game I've tested works fine with the titantron graphics, even the first Smackdown vs Raw title. I've tried EE cyclerate to +1 or +2 but even that didn't fix it, but it does fix it on 1.4.0.


Specs:

i5-6600k
GTX 1080
16GB RAM

PCSX2 specs: everything default except for resolution which I have on 3x native and anisotropic filtering which i have on x16.

Uploaded videos displaying the problem in all 3 games. Apparently with 2007 and 2008, in Orton's entrance, it fixed itself for a split second but only when the pyro was going off.

2006: https://youtu.be/KLXUJyNrrmk

2007:  https://youtu.be/zbcSU55ZWP0

2008:  https://youtu.be/FI__eraWCK4
Reply

Sponsored links

#2
can you try a fest boot instead of full boot ?
before this, check if automatic gamefixes are enabled
CPU : I7 2600K Oc'ed @ 4.2Ghz
Mobo : Intel P67 southbridge
GPU : NVIDIA Geforce GTX 750 Ti
RAM : 6 Go
Reply
#3
(05-13-2020, 02:34 PM)jesalvein Wrote: can you try a fest boot instead of full boot ?
before this, check if automatic gamefixes are enabled

hey there, fast boot did not change anything and automatic gamefixes are enabled. I am puzzled as to what might have broke them going from 1.4.0 to 1.6.0
Reply
#4
You seem confused. You require ee cycle skipping +1 or +2 (and not ee cycle rate) to get titantron working.
Reply
#5
(05-13-2020, 03:15 PM)prafull Wrote: You seem confused. You require ee cycle skipping +1 or +2 (and not ee cycle rate) to get titantron working.

oh, thank you!!! this fixed it!
Reply




Users browsing this thread: 1 Guest(s)