RivaTuner v2.05 development and alpha-testing

Well, 2.04 is released so now I can start developing 2.05 and can play with new independent shader clock control interfaces a bit more. I've already added a slider for adjusting shader clock and I need a few G8x owners for alpha testing it and brainstorming final shader clock UI implementation. Keeping currently existing driver/hardware ratio limitations in mind (http://forums.guru3d.com/showthread.php?t=238083) I'm still unsure it is is a good idea to provide completely independent shader clock control, probably we should keep it ratio based.
Also, I've tried to make a workaround for the ForceWare's internal clock frequency programming optimizations, which currently require ROP clock change to be performed to get new shader clock applied. Now RT analyzes the clocks being set and if it detects that shader clock is changed but ROP is not - it first downclocks ROP by 1MHz then returns it back together with changing shader clock. It will make shader clock adjustment more simple for beginners.

So if you've read shader clock overclocking tutorial thread and if you feel that you completely understand it - I offer you to join 2.05 development and shader clock UI brainstorming. In this case send me your email via PM and I'll send you alpha version of 2.05 with shader clock adjustment UI prototype.

 

Yes. Send a PM with email address and I'll forward you alpha tomorrow in the morning.

 

Here we go. I've just forwarded the first alpha of 2.05 to everyone who sent me emails via PM.

 

That's not that simple. There is no strict rule telling if ratio is good or bad.

 

Some development progress:

I've decided to change ShaderClockRatio handling behavior. Now defining a ratio via ShaderClockRatio in PowerUser settings no longer results in hiding shader clock slider completely and adjusting shader clock automatically. In new alpha RT will still shows shader clock slider when ratio is defined, but it will not allow you to drag it independently from core clock slider in this case. Now the ratio affects core clock slider dragging only - as soon as you move core clock slider RT also synchronically adjusts shader clock slider position using the raitio you've defined.
In other words, now ShaderClockRatio affects UI, but not clock programming directly.

New alpha version will be available tomorrow.

 

That's _your_ system's limit and it is not have to be the same for others.

 

I repeat once again that the limits are DIFFERENT for different systems and it is IMPOSSIBLE to predict which one is currently in use. Let's stop wasting the time please.

 

Guys, I've just sent you new alpha version of 2.05 including the following changes comparing to the first alpha:

- Changed ShaderClockRatio handling behavior. Now defining a ratio via ShaderClockRatio in PowerUser settings no longer results in hiding shader clock slider completely and automatically adjusting shader clock synchronically with ROP clock. Now RT still shows you shader clock slider when you define a ratio via PowerUser tab, but it doesn’t not allow you to drag shader clock slider at all. Now the ratio affects core clock slider dragging behavior - as soon as you move it RT also synchronically adjusts shader clock slider position using the ratio you've defined. This allows you to use manual ratio-based shader clock adjustment and at the same time load and apply the profiles with different ratio, reset clocks to defaults (which can use different ratio too), etc, etc. In other words, now ShaderClockRatio affects UI, but not clock programming directly.

So please check it with and without ShaderClockRatio.

Please take a note that I've forwarded it only to those who sent me any feedback (now or in the past).