Printable Version of Topic

Posted by: Wile_E_Coyote Feb 22 2007, 11:57 AM

I have a large sphere textured with a movieclip skin.
I have several smaller spheres textured with a colorskin rotating around them.
When I mouse over one of the small spheres the whole rotating stops.
That is when the problem appears.

Some of the faces of the large spere has it's movieskin removed, and I end up with holes in my sphere.

A solution I have found is to keep rotating it every frame, but with the same angle, so the image appears static, but it's still a big cpu load..

Is this a known problem?
Is there a better (less cpu intense) workaround you guys know of?

Cheers!

Posted by: kiroukou Feb 22 2007, 12:50 PM

Hi Wile,
Can you precise your sandy version? Is it the beta or the 1.1 ?

Thanks.

Posted by: Wile_E_Coyote Feb 22 2007, 01:11 PM

Sure,

I'm still using the 1.1 version.
When I switch to a textureskin, I don't have this problem,
but with a movieskin it happens every time....

Posted by: Petit Feb 22 2007, 02:02 PM

I have this problem too using Sandy 1.1. Any rotating object using RotationInterpolator,
are at risk of loosing one or more of its faces when the interpolator is paused.
the faces comes back immediately when the interpolator resumes.

It is ugly, and I don't have a solution.

It seems that the rendering process for the interpolated object is stopped before
the whole object is drawn. Maybe the interpolator should set a pause flag and check
that all the objects faces are rendered before it actually stops. (?)

Posted by: Wile_E_Coyote Feb 22 2007, 02:54 PM

That might not be a bad idea at all actually....

As I stated in my original post, another option is to keep updating, but with a static rotation....
But that is a very ugly solution I think, as it's still using a lot of cpu power...

But thanks for the confirm that it wasn't my sloppy programming causing this 'interesting effect' as a colleague described it....

I switched to the textureskin, as it's suffiecient for what I have in mind now.

thanks!

Posted by: kiroukou Feb 22 2007, 04:10 PM

Yes in the 1.1 this bug was present.
It has been fixed in the 1.2, but it is still a beta relase so it depends on your needs