[Bf-funboard] RGB Curve Node – cursor jumps back

[Marc Dion]

in that video you posted, the curve-point did not jump back to the original
position.  It jumped to where you had moved the mouse.

The delay is caused by the viewport rendering using up too much system
resources.

When this happens,  fundamental operations like keyboard and mouse IO
cannot be processed immediately, instead the commands build up in a cue.

Then once the CPU has a bit of time allocated to house-keeping(IO), the cue
is processed and a flood of old keyboard and mouse calls are suddenly
processed even though they are no longer relevant.

For me, under  OS X, if I set the rendering tiles to 16x16 then this almost
never happens and I can spend hours using the viewport rendering
interactively without too much issue.

When I've been baking textures,  I often forget to change back to 16x16
since baking requires higher tile sizes even for CPU rendering this will
get very bad for me.

The 512x512 tile size I use for baking textures will lock up the CPU long
enough per cycle to cause IO  sputtering for viewport rendering but it's
fine when I remember to change back to 16x16.

I think you can go as low as 8x8 for tile sizes.  Try that and see if it
helps.

Otherwise we should be patient until someone has inspiration in this area.
Sergey's been putting thought into this so maybe something will come out of
that.

On Tue, Apr 28, 2015 at 1:48 AM, <mond at email.cz> wrote:

>
>
> On mouse release, cursor jumps (or appear) back on place of initial click.
>
> That's really uncomfortable and unexpected behavior.
>
> https://dl.dropboxusercontent.com/u/55113627/RGB_Curve_behavior_50%25.mov
>
>
>
>
>
> What does it mean in everyday situations?
>
> Accidentally reverted just done adjustment.
>
>
>
>
> Why?
>
> Eyes were watching image to see result and didn't noticed that cursor
> jumped
> back … by another click (to continue in adjusting curve) is first action
> like reseted to initial state.
>
>
>
>
> ---------------------
>
>
>
>
> What I (and I'm sure others) do, is to grab a RGB curve and watch image
> (don't curve) to see how adjustment results. Result is not refreshed
> (visible) until you release curve dragging, after than you can see result
> and click again to continue adjusting curve. But this is not that bad.
>
>
>
>
> The bad part is fact that for each step of curve adjusting we have to
> travel
> our eyes over screen - from image to node - repeatedly to hunt control
> point
> by "jumping" cursor.
>
>
>
>
> This "jump" is maybe helpful behavior for value slider, but definetely not
> for curves.
>
> I fight with this behavior for many years, so I want to ask if it possible
> to change behavior into expected behavior.
>
> Or is there for this behavior any reason?
>
>
>
>
>
> Thank you for your attention and your opinion.
>
>
>
>
> Filip (vklidu)
>
>
>
> _______________________________________________
> Bf-funboard mailing list
> Bf-funboard at blender.org
> http://lists.blender.org/mailman/listinfo/bf-funboard
>