Well, I move some panels very slowly with an effective speed of <1 pixellength per frame. Though, it seems, all panels are snapped on integers. The panel's motion is stuttering all the time and I can only circumvent it, when I set a low fps_max (=30) and move them with integer values without time correction via time_step to make it move smoothly. Entity panels are no option, since my panels move between other panel-layers, too.

Here is some sample code:

Code:

---

PANEL* pan;
pan = ...;

pan->pos_y += 0.1 + sin(total_ticks) * 0.1 * time_step;
pan->pos_x += sin(total_ticks) * 0.5 * time_step;

---

Can you please circumwent this by giving panels var precision?

Cheers, Christian

I'll check if this is possible. However, a solution for the stuttering problem is precalculating the frames per pixel, rounding it to the next integer N, and moving the panel by one pixel every Nth frame.

Honestly, I do not get what you are driving at. The motion is in my example associated with a sin wave and the time_step value, which is not static if I do not limit the fps_max. Do you mean, that I take the position of my panel and add motion only to a second "position". When the position is 1 pixel or more related to the original panel, I move the panel?

Hm, I will check it out. Thanks, that you will check it on your side, too

Cheers
Christian

No, my suggestion would not work with a sine wave motion, only with a straight motion. I am not sure if DirectX allows to blend 2D objects between pixels at all, without going to 3D. But I've put this on my list of things to check.

I have no problem at all with panel movements... is that just me?

Try to use my code. When the panel coordinates allow only integer's and you move them very gently, they "snap" all the time, because you cannot pose them on 3.5 or 6.03 or that kind of stuff.

Ah like that. Never noticed it all that much, but it would be nice if directX supports it .

Did you checked this? If this doesn't work I will work out a custom solution for this.

do the calculation with floats and then always set the panels coordinates to that floats. I know that it will interrupt your workflow a bit, but that would be a workaround for now.

I do that already But the representaion is not suited for floating point values.