Sign in to follow this  

Should inFrustrum work on a sub mesh basis?

Recommended Posts

I have a scene not quite ready, but essentially a human mesh appears.  It does some skeleton posing coordinated with some morphing.  The scene is using an arcrotate camera.

The human has meshes for eyes, eyelashes, eye browse, teeth, & tongue which were all merged prior to export.  They are a single mesh with multi-materials, so sub-meshes, in BJS.

If you zoom in, the sub-meshes disappear early.  I am not sure, is this was supposed to happen?  BTW, If no animation is done or only the morphing, then this does not happen.  If I do the QI.skeleton posing this results.  The series of poses do lower the skeleton, which are part of a defense.  Could it be since bones are done on gpu, frustrum is not done based on being slightly crouched?  It does look really weird.


Share this post

Link to post
Share on other sites

It should not be the case. The isInFrustum uses the bounding info. But for GPU modified meshes, the bounding info is not updated (as it lives on CPU side) and if the deformation is important enough the bounding info could be completely off :)

In this case I suggest to turn off mesh selection with mesh.alwaysSelectAsActiveMesh = true

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.