Overclocking the EE (discussion) (testers wanted)

[jlwmanagement]

Thanks! I didnt change that because it didnt really add much to the screenie. I just wanted to get my words into graphic form

[Akio]

change EE cyclerate to
"EE cyclerate (Higher values require more powerful hardware)"

I think this will help.

Edit: also the slider currently moves in the opposite direction for underclocking, might that lead to confusion?

Some users might be confused but it's the right thing to do. The users will need to adapt.

would it be prudent to add some simple option in the speedhacks section. Something along the lines of a checkbox for (enable over/under clocking) and that has an effect on the EE slider? This is a mockup of what i mean:

I think the check box should be above the EE Cyclerate slider. This check box might raise a question about why this option needs a check box to enable it. But I think it's an acceptable compromise.

If we're going to do this, I suggest that when this check box is unchecked, the slider should be disabled and the handle should be at the default position.

Gregory had the idea of making a continuous slider - one that doesn't "snap" to ticks.

So e.g. you could set arbitrary values like +37% or -14% or whatever.

But if we do that then it no longer lines up with the current slider which screws with the presets and ini.

You can write a wrapper if you want to make it backward compatible.

[jlwmanagement]

If we're going to do this, I suggest that when this check box is unchecked, the slider should be disabled and the handle should be at the default position.

Agreed. I was thinking that the slider should be greyed out/disabled until they check the box. This helps the user understand that moving it is indeed a hack and can have consequences. Although having it directly under/above the EE slider may be a good idea

You can write a wrapper if you want to make it backward compatible.

I think we should strive for simplicity when we can. Especially when it comes to something like the GUI. I am not saying a wrapper is a bad idea, but in my programming experience, a simple GUI and implementation tends to be a good idea when the application is for the general public (and you have no idea how or what they will use to run it). Complexity is a very beautiful thing when it is done simplistically

[H.A Treesong]

Mmh, no noticeable improvement in Ibara (J).

This arcade port is a mess anyway so I first had to battle with the visuals trying to make it watchable.
Ended up choosing native with 'scanlines' in full vertical (tate/portrait) orientation.

Then I kept an eye on the actual game's natural slowdowns, but it's a degree of abnormal jerkiness I've noticed instead.
There are moments when the fast scrolling and overall action goes 'staccato' or 'choppy' if you like for a few seconds, this is not how the game behaves on real PS2.

Pushing the EE to 33% and 50% didn't help.

[Akio]

I think we should strive for simplicity when we can. Especially when it comes to something like the GUI. I am not saying a wrapper is a bad idea, but in my programming experience, a simple GUI and implementation tends to be a good idea when the application is for the general public (and you have no idea how or what they will use to run it). Complexity is a very beautiful thing when it is done simplistically

The wrapper works behind the scenes. The users won't be aware of it. It will definitely add some complexity to the code but it's unavoidable if we want to make it backward compatible.

[Blyss Sarania]

The wrapper works behind the scenes. The users won't be aware of it. It will definitely add some complexity to the code but it's unavoidable if we want to make it backward compatible.

It's not unavoidable. As long as the slider positions 1, 2, 3 map the same place they do now(in the stable release), then it will be compatible to the INI and everything else.

[Akio]

I mean when you can set arbitrary values.

[jlwmanagement]

I think setting arbitrary values is not an ideal thing to do because you lose a bit of control and it would make supporting the feature a little cumbersome. I suppose you could tell them to set it back to standard and see if the issue goes away but that isnt really support. It is more damage control. If there are a few set values, then they can be standardized and tested more thoroughly which will make a more solid product.

[Blyss Sarania]

I think the best option is a 5 position slider that is compatible and lines up with our current slider - at least for now. That is the easiest to implement by far.

[jlwmanagement]

I completely agree. I posted an image that could depict what that might look like. Although the checkbox may or may not be necessary depending on whether the dev folks want to have an extra step in determining if the hack is enabled.