Poll: How should the EE cycle rate slider be handled ?
This poll is closed.
Invert the slider
66.67%
14 66.67%
Follow the current slider format
33.33%
7 33.33%
Total 21 vote(s) 100%
* You voted for this item. [Show Results]

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
EE overclock slider
#1
Hello PCSX2 users,

Currently there's quite a heated discussion going on around GitHub based on the placement of slider values on EE cycle rate option. As most of the users might know, new negative slider values for overclocking the EE was recently merged to the Master branch. (#816)

While this was a really good addition to the EE Cyclerate slider and also has a probability to be a potential alternative fix for timing issues (#82) , this did also introduce few irregularities on the GUI side from an user perspective.


[Image: UeHGfrV.png]


The irregularities are that most of the users might expect the values +1 , +2 to overclock and conversely the negative equivalents to underclock the Emotion Engine's Clock speed. ( most likely the natural assumption by new users of the Emulator ) which conflicts with current slider since it actually does the opposite of what the new users might have expected it to do. Tongue2

Whereas, Regular users of the emulator might have got accustomed to the positive values for the underclock and would naturally expect the negative equivalents to be an option for Overclocking.

The following Poll has been made on intention to find out the consensus among the users regarding the placement of the slider value functions. also please try to provide logical reasons for choosing any of the following options on the Poll , Thanks Smile

Some notable quotes from users of PCSX2 :-
  • willkuer Wrote:I am no friend of inverting the slider btw. To change an existing feature into the opposite is a usability crime. At least for a 'short' time. I dont see the point why overclocking needs to be to the right. Sure the emulated 'clock rate' increases with overclocking. But the time period between events is decreased and the unlocked fps are decreased (due to cpu limitations). To define one direction as the one and only truth is not possible here.
  • blackbird Wrote:I for one would like it to be inverted. Dolphin already has it like this and it makes lot more sense.
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction

[Image: 84t1dRu.png]
Reply

Sponsored links

#2
I disagree with Willkuer. Flip it if the code won't be too much trouble.
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#3
(11-06-2015, 06:54 PM)Nobbs66 Wrote: I disagree with Willkuer. Flip it if the code won't be too much trouble.

Inverting the slider is trivial, I'm more concerned about the other users opinion on the slider format. the poll and posts would eventually decide the outcome.
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction

[Image: 84t1dRu.png]
Reply
#4
I vote to invert it. To me it is intuitive that the rightmost value would make the EE go faster.

Slightly off-topic but still about "bad" GUI design:
I argue that the GSdx Software mode "Extra rendering threads" option is bad design.
How many times have the regulars here had to explain that it should be set to "the number of cores of your processor, minus one"?
Because of this, I believe renaming it to "Rendering threads" and setting the minimum to 1 would be better.
Reply
#5
(11-06-2015, 07:45 PM).r5 Wrote: How many times have the regulars here had to explain that it should be set to "the number of cores of your processor, minus one"?
Because of this, I believe renaming it to "Rendering threads" and setting the minimum to 1 would be better.

But that would mean it's using 2 threads, it is extra rendering threads over the main thread we would have to recode it so the gs plugin takes that value -1
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#6
Fip it if you can do it while maintaining preset compatibility. I originally did it that way.

You know the line that says "EE cyclerate(not recommended"? You can change that so it's like this:

"Overclock<-----------EE clock-------------->Underclock"

or

"Underclock<-----------EE clock-------------->Overclock"

or similar which makes it obvious which way is which. No matter whether you flip it or not. This eliminates the problem of it being "different" than before.

The English is fine btw, not perfect but totally understandable.
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply
#7
(11-06-2015, 09:59 PM)Blyss Sarania Wrote: Fip it if you can do it while maintaining preset compatibility. I originally did it that way.

You know the line that says "EE cyclerate(not recommended"? You can change that so it's like this:

"Overclock<-----------EE clock-------------->Underclock"

or

"Underclock<-----------EE clock-------------->Overclock"

or similar which makes it obvious which way is which. No matter whether you flip it or not. This eliminates the problem of it being "different" than before.

The English is fine btw, not perfect but totally understandable.

The text change looks a bit unprofessional though Tongue2 , maybe something more short and equally easier to understand ?

Preset compatibility shouldn't be a problem Smile
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction

[Image: 84t1dRu.png]
Reply
#8
I guess you could shorted it to OC and UC, but having the full words does look easier to understand. The EE Clock bit could be put above it to shrink the amount of information there, or visa versa
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#9
I think the problem here is that it is in the speedhacks section. Increasing something in the speedhacks section shouldnt yield lower speed.

If you want to have a slider manipulating the clock rate put it into the ee tab and not in the speedhacks section.

Using lower than normal values here really means less vsyncs. And thats exactly what i would expect.



What i said about the usability crime is that everybody would expect after using 0.9.8, 1.0, 1.2.1 that increasing the ee slider one tick is the best for his athlon x2. At least between the stable revision where it was introduced up to the next stable release we will have confusion.

On the code level the change is trivial.
Reply
#10
I could have sworn I had a post in this thread.
[Image: pNm13X9.gif]
Windows 10 Pro x64 | Intel Core i7-4790K @ 4.00 GHz | PowerColor R9 290X 4GB | G.SKILL 16GB (4x4GB) DDR3 1600 RAM | Samsung 850 EVO 250 GB SSD | Seagate ST3000DM001 3TB HDD

CPU Intensive Games
GPU Intensive Games
Games that don't need a strong CPU
Reply




Users browsing this thread: 1 Guest(s)