I tried to generate my own df3 ghost with Gill Trans makecloud makro but
encountered the following problem.

I have a figure (the ghost itself), its eyes, a clothing and its hair. That are
four meshes. I closed all holes very carefully with Meshlab and inspected the
results with Wings. No holes remained. Then I put the objects after the usual
conversion with PoseRay into the makecloud-macro having additional very small
black spheres at the corners of the bounding box of the whole figure (to ease
the recomposition of the four resulting df3 files and the rescaling). Now I
observe that the last frame with an intersection of the object is repeated until
the end of the animation. If I stop the animation and start it again with a
higher frame_number I have the expected black screen after the pass of the
object. Has someone of you ever experienced such an odd behaviour?

Best regards,
Michael

Post a reply to this message

On 24-9-2013 20:57, MichaelJF wrote:
> I tried to generate my own df3 ghost with Gill Trans makecloud makro but
> encountered the following problem.
>
> I have a figure (the ghost itself), its eyes, a clothing and its hair. That are
> four meshes. I closed all holes very carefully with Meshlab and inspected the
> results with Wings. No holes remained. Then I put the objects after the usual
> conversion with PoseRay into the makecloud-macro having additional very small
> black spheres at the corners of the bounding box of the whole figure (to ease
> the recomposition of the four resulting df3 files and the rescaling). Now I
> observe that the last frame with an intersection of the object is repeated until
> the end of the animation. If I stop the animation and start it again with a
> higher frame_number I have the expected black screen after the pass of the
> object. Has someone of you ever experienced such an odd behaviour?
>

Hmmm, no. Strange indeed. It would suggest a remaining hole somewhere... 
Have you checked the normal orientation of the faces in the original 
mesh? If some are switched that may lead to strange results maybe.

Have you tried to put all the objects into one single mesh? Might be 
worth the test. In my own ghost, the eye balls are part of the mesh for 
simplicity's sake. Of course, then I cannot colour them separately in 
another df3.

Thomas

Post a reply to this message

Thomas de Groot <tho### [at] degrootorg> wrote:
>
> Hmmm, no. Strange indeed. It would suggest a remaining hole somewhere...
> Have you checked the normal orientation of the faces in the original
> mesh? If some are switched that may lead to strange results maybe.
>
> Have you tried to put all the objects into one single mesh? Might be
> worth the test. In my own ghost, the eye balls are part of the mesh for
> simplicity's sake. Of course, then I cannot colour them separately in
> another df3.
>
> Thomas

Thanks Thomas!

Indeed I had "holes". MeshLab indicated no holes, but introduced default
additional textures for the holes it has closed. PoseRay breaks the meshes by
materials, so I had a union of several meshes (only three with the eyes). In
many cases this is not a problem, but only one seems to be allowed for the
object-pattern used by makecloud. After having removed the additional materials
and exported the mesh with PoseRay again resulting in one group, the problem was
gone.

The black screens at the higher frame_numbers after a restart of the animation
are still a riddle, but who cares now? Most likely the parsing is a bit
different with animations.

And yes I'd like to have a different media to the eyes.

Best regards,
Michael

Post a reply to this message