Posts: 3.091
Threads: 76
Joined: Dec 2008
Reputation:
57
04-20-2011, 02:35 PM
(This post was last modified: 04-20-2011, 02:37 PM by smartstrike.)
an i7 at 2.8 Ghz is not enough for Tenkaichi 3 to get max speed....speed hacks is rendered uneffective.
that game it's pretty demanding around a magnitude of 4~5Ghz......try OC a little.
if Rezard has that game Tenkaichi 3 i'm sure he will gave some perfect examples.
Main PC1:i5-4670,HD7770(Active!)
Main PC2:i5-11600K,GTX1660Ti(Active!)
PCSX2 Discord server IGN:smartstrike
PCSX2 version uses:Custom compiled build 1.7.0 64-bit(to be update regularly)
smartstk's YouTube Channel
Posts: 4.504
Threads: 14
Joined: Jul 2009
Reputation:
89
Keep an eye on the EE and GS percentage, since the video card is the bottleneck in that configuration you may need to tinker with scaling and such.
The second and possible issue source is the turbo feature on iX CPUs. A wild guess is suggesting the use of a "High Performance" power saving plan at Windows Control Panel under the Power Options.
Imagination is where we are truly real
Posts: 1.678
Threads: 28
Joined: Mar 2011
Reputation:
49
Location: India
04-20-2011, 03:04 PM
(This post was last modified: 04-20-2011, 03:06 PM by recoder.)
Turned on the power.... done... ahh.. fps around 57 fps to 60 fps. Got a good speed in the PAL version.
Please answer the question when Core 2 Duo @ 2.85 Ghz can run pcsx2 at full speed( 60 fps - constant) then why can't Intel i7 860 ghet a full fps at constant
Posts: 4.504
Threads: 14
Joined: Jul 2009
Reputation:
89
04-20-2011, 04:05 PM
(This post was last modified: 04-20-2011, 04:21 PM by nosisab Ken Keleh.)
The iX CPU uses a complex turbo feature which can increase the clock on some cores while effectively reducing it on other cores, beyond this it try to run bellow the nominal clock whenever possible to reduce power consumption. Of course it is helped doing so by the Windows Power saving feature and sometimes they don't understand one the other very well.
To calculate the demand and to know if it should run at nominal clock value or even turbo, the average CPU load is used as measure (involved in a same process). By design PCSX2 multitask EE and GS in two cores, some times one the two is heavily loaded while the other seat down in low levels, this seems to fool the power plan into believing the average load is low, so no turbo and sometimes not even the nominal clock is used (to know if this "bug" is hitting keep an eye on a external CPU load monitor, it probably will show all cores low loaded while EE or GS is screaming desperately).
PS: This show clearly the difficulty of multithreading a pipeline model like PS2... when EE is saturating it can't provide enough output to make GS work hard, this cause the feedback when the CPU clock rate may become lower... which cause less EE output (while screaming at near 100% the provided CPU clock usage)...which leaves GS yet more light... which translates for lower average load... rinse, repeat... and the picture ugliness emerge in all it's glory.
Imagination is where we are truly real
Posts: 23
Threads: 1
Joined: Mar 2011
Reputation:
0
Errr, does that translate to "Old Console + New Hardware = Annoying problems?"