Jump to content

Sign in to follow this  

Volume Builder concerns

Recommended Posts

Ill preface by saying I am running Win 10 X64, i7-6700k CPU with a GTX 960 GPU and 32GB of DDR4 Ram


So, I have attached the simplest of C4D Projects...  two cubes, one subtracted from the other inside a volume builder and volume mesher.


Two concerns... even on my PC which i think is fairly capable and modern... JUST doing a two object operation with volumes makes moving the inner subtracted cube move very slowly in the viewport, if i add another or two.. I start getting wireframes in the viewport and the cubes are almost impossible to move without slowing to a stop.


What good are volumes, if just subtracting a cube or two from another makes the project almost unusable?.. How could I possibly do any kind of job using volumes as a workflow if even in THE most simple example the project becomes so slow I cant even work on it.


Second question... I added two different materials to the two cubes in the scene... neither of which are being applied to the specific cubes.. 


How do u apply materials to different objects inside the volume?


Id love for someone to make me see what I'm doing wrong here... as I love the concept of volumes but apparently, as far as I can see I may need a Supercomputer to use them.




Share this post

Link to post
Share on other sites

Hey,  VST,



I have encountered much the same thing when working with volumes:   sometimes my computer would be made very slow indeed by a subtraction or union.  And my machine is fairly  powerful,  too.


I found that the problem was greatly alleviated if I:


  • made sure that the primitives or mesh objects I dropped into the Volume Builder did not already have an extremely high polycount.   For example,   I have my sphere primitive bumped editable with a Segment Count of 60,    rather than the usual 90--100 I usually prefer.   With your Cubes,    make them Editable with a polycount setting of 8---8---8.   The trick is to make your Volume Smoothing do all the smoothing work,    rather than putting high-poly objects initially into your Volume Builder.
  • switched the viewport's current Display Shading away from Gouraud and down to Hidden Lines mode,    at least while I am doing the object translation needed for a Subtraction or Union;   you can even leave your scene in Gouraud,  and instead apply a custom Display Tag to your Volume Mesher to temporarily reduce the demands it's making on your computer resources.
  • and of course,  as you know,   the whole Volume operation is made more CPU/RAM intensive if your Voxel Count is dialed very low,   or your Smoothing Iterations is too high.    One trick is to perform your Union or Subtraction while the Voxel Count is set to something loose,   like,  say,  5cm.     Then,   after you've gotten everything the way you want it,    dial the Voxel Count down to something finer,    like 1 cm.

And,  as you know,   the Meshes you get as a final result of Volume Building are invariably crazy-high in polygon count.   I almost always then apply a Polygon Reduction to that mesh;     you can reduce your polycount up to 75% or more,   with no discernible loss in visual quality.       All in the name of safeguarding your computer's resources and preventing a huge hang or crash.

And,  vis-a-vis your texturing your objects:   Bear in mind that,   once you drop a mesh (or other object) into the Volume Builder,     it ceases to be a "mesh".     It has become a voxel volume,  (a whole 'nother thang)  and,  as such,   will not take a Texture.     Only the Volume Mesher (in your OM)  can receive a texture.    And that Texture will apply to the whole stack of objects in the Volume Builder.      Somewhere online,   there is a tutorial of how you can use the Correction Deformer on the Volume Mesher to enable you to assign different textures to the different objects placed under the Volume Builder.    Though usually your goal is to create a whole new mesh with a single texture,   as the goal of Volume Building is not so much to allow you to to do Boolean-type operations,  but rather to yield brand-new objects which possess the unique "edge-smoothing" look that Volumes afford.

Best,  ras

Share this post

Link to post
Share on other sites
  • Topic Author
  • Just the type of advice I was looking for.. well written, to the point and effective.


    My thanks, this helped me a lot ras.


    Sage, :respect:

    Share this post

    Link to post
    Share on other sites

    You bet,  Sage!

    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.

    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.

    • Create New...