Overclocking the EE (discussion) (testers wanted)

[willkuer]

Uh no... All of gregory GSdx changes since February?

Gsdx changes should not affect your build if you just use the newest gs plugin.

The savestate bump is maybe an issue. You can not use up2date savestates with the ee over clocking version.

[Lagahan]

Gsdx changes should not affect your build if you just use the newest gs plugin.

The savestate bump is maybe an issue. You can not use up2date savestates with the ee over clocking version.

Yeah that's what I'm doing, GSDX has come on leaps and bounds lately!

almost as interested as in 3D Vision compatibility, my most wanted feature that won't probably exist for a long long time

Seconding that, problem is it would likely be a game by game basis just like 3D vision itself, and would be a huge pain in the ass on performance Would love to be able to view games in 3D with the Rift It would probably be likely that we'd see a complete GSDX rewrite to handle games using mipmapping long before 3D would be covered, I'm fine with that anyway as long as EE overclocking gets into main!

[ssakash]

Hello Folks, I have done some changes to Blyss's EE overclock commit to make it obey presets and restore defaults settings and also did some changes to the underclock function values above 2 and simplified the overclock stuffs a bit. I asked blyss about it and started to continue the improvements on this commit since Blyss was apparently Busy IRL.

So, If anyone is interested you could check the updated EE overclock build and provide suggestions to improve on any field. Thanks

Here's the build : https://www.dropbox.com/s/rszw62fg01q3ef...2.exe?dl=0

I'll PR it if it's okay with everyone, here's the code for those who are interested : https://github.com/PCSX2/pcsx2/compare/m...EE_Control

[hellbringer616]

is the updated build up to date with master?

[ssakash]

is the updated build up to date with master?

yes, of course.

Looks like it's 2 commits behind actually, that shouldn't be a problem.

[Lagahan]

Lookin good! Jumps in clockspeed are a bit big but a lot easier to read the UI now!

[Blyss Sarania]

Looks nice, but the descriptions(red text) need to be changed(the English is not very good):

for 33% - "Increases hardware requirements. May increase in game FPS"
for 50% - "Greatly increases hardware requirements. May noticeably increase in game FPS"

The first lines of each are fine.

Otherwise looking good, good job!

[ssakash]

Lookin good! Jumps in clockspeed are a bit big but a lot easier to read the UI now!

Thanks for the feedback , my priority was to make it simple and follow the same format as the previous slider. are there anything worth improving on at the current implementation ?

Looks nice, but the descriptions(red text) need to be changed(the English is not very good):

for 33% - "Increases hardware requirements. May increase in game FPS"
for 50% - "Greatly increases hardware requirements. May noticeably increase in game FPS"

The first lines of each are fine.

Otherwise looking good, good job!

Thanks, updated the text. you're the english master after all.

[Lagahan]

I've noticed big improvements in Quake 3, Wipeout Fusion and Ratchet & Clank 1, but in Ratchet's case since its using software mode on GSDX my CPU cant quite keep up with a 33% overclock. The original game stuttered a little, for example on the Metropolis level where you can see a lot of the city but at 33% OC its gone though I can only get 46fps/50 (PAL) so its just  a little bit too hard to run. I don't really notice it with async mix on the audio though so I run it at 33% OC all the time. I've noticed an increase in smoothness in parts of Killzone during intense scenes as well but again its just a tiny bit too hard to run for my current CPU.

I definitely think it should stay in the emulator, though if needs be for simplicity it should be hidden as a hack somewhere. This hack version could also override the ini settings which were kept for backwards compatibility to allow for more granularity when enabled, but when disabled returning to the old version (0, 1, 2). A big help to making sense of it would be a display of internal game FPS alongside of the output render FPS.

In a few years when CPU's IPC and clocks go up even farther we'll definitely be able to see the benefit in some games. I'm used to gaming at 120hz low persistence or on my Rift so every extra bit of smoothness is a godsend when you're used to zero motion blur. Even if there's a slim chance of running games better than they originally did we should take it!

[masterotaku]

are there anything worth improving on at the current implementation ?

Please, can we have higher overclocks than 50%? I'd also like more granularity, like having options from +10% to +100% in 10% increments. If you want to keep bigger steps, it could be +16.67%, +33%, +50%, +66.67%%, +83.33% and +100%.

I want higher than 50% OC because in Kingdom Hearts 2 Final Mix, in the "Valley of the Dead" location, when there are a few of those spirit balls, the game can't keep 120fps and falls back to 60fps. That's at 50% OC, of course. It also happens when there are a lot of effects in blattles and similar things. The 120fps patch demands more overclocking than the 60fps one.