Jump to content


Regular Member
  • Content Count

  • Joined

  • Last visited

Community Reputation

11 Poor

Contact Methods

  • Website URL

Profile Information

  • First Name
  • Last Name
  • C4D Ver
    R20.026 Studio

Recent Profile Visitors

871 profile views
  1. 10 min keynote from the new MAXON ceo! Just announce the big news and wrap it up. I like his style! Tim Cook can learn something from this.
  2. Thx again for narrowing the problem down to the Tile setting in the texture tag, Bezo! Now the problem is totally solved.
  3. hey Dan, Just reapplying the texture tag didnt work for me. Only remapping the UV's worked. (or changing the projection type in the texture tag as Bezo said)
  4. Thx a lot Bezo! That explained and solved the problem.
  5. Does anyone has a solution or workaround for this Edge bevel shading bug: After beveling an edge, part of the newly created polygons will be transparant. This bug is present in both the Bevel tool as in the bevel deformer. You can see the problem in the screenshot or in the attached file. Edge bevel shading bug.tif Edge bevel shading bug.c4d
  6. This is something that's on my wishlist for C4D for a long time. There's a plugin (Nitro Falloff) that you can try. We need a 'fit to selection' button for deformers, similar to the 'fit to parent' we allready have. It would make all deformers at once very powerfull modelling tools. You can do it now but it's just too cumbersome to manually adjust the cage to your selection.
  7. Apple has announced a new Mac Pro for 2019. This machine should finally turn around the neglect high end Mac users have suffered the last 8 years. If possible I would wait for this machine, but this can be another 12 months and this may not be possible for you. Right now the iMac pro is the best Apple has to offer for 3D.
  8. Make the plane smaller so the image (and alpha) covers the whole area.
  9. I think he meant the 32core threadripper 2990WX CPU (not video card). For around 3000 euro you can build a render node with a Cinebench score of 5000. This is really great value. Building a render node with Xeon processors with similar performance you would need a dual processor machine that costs more than twice that. This way you dont have to switch to a third party renderer and can keep rendering in Physical Render. With Team Render you can combine the CPU power of your iMac pro and the render node. You will be able to render 3 to 4 times as fast as you do now.
  10. Working with instances in the Volume Builder (or linking objects which is similar) is really buggy in my experience. I only work with objects as childs of the Volume Builder. Because if I use instances or link objects sooner or later C4D will crash or the viewport will be messed up. Objects you have set to Subtract will suddenly render as Union. Or some object in the Volume Builder will not render in the Viewport anymore. I'm still a big fan of Volumes but I hope MAXON can fix these bugs because for now only objects as childs of the builder are stable to work with. And that's a shame because a lot is possible when you can have a hierarchy of objects and link these objects into several different Volume Builders.
  11. first slant the cube and then use the loop cut tool to make the 3 subdivisions hold shift to make a center cut and then press the plus once to make three evenly spaced cuts
  12. In stead of investing in plugins like X-particles and an external renderer I would also suggest you invest that money in a hardware upgrade. If you are working in C4D on a 13 inch screen you will spend most of your time opening and closing windows and menu's... and scrolling in the object manager. At the very least buy a big external screen.
  13. I also tried to find a way to do that but also didn't succeed. I was hoping to do it by applying a vertex color tag to the Volume Mesher. The objects you use in the Volume builder could then be used as fields to color the final mesh. Unfortunately you cannot apply a vertex color tag to the Volume Mesher. Lets hope this can be added in a future update.
  14. hello Fritz, Good to hear you are investigating the issue. To answer your questions: Once the problem started every Volume Builder had the issue as soon as I dragged an object in the layer list of the Volume Builder. Even after restarting C4D and rebooting Win10. No plugins installed. Imported my custom layout from R19, don't think this is the issue because it worked fine for 3 days , I played for at least 10 hours with the Volumes before the issue started. When I first triggered the bug I was manipulating the points of polygon objects inside Subdivision cages. These subdivision objects where linked in a Volume Builder. I did allready had a few of crashes with fields. Setting a Freeze Field to grow in combination with a Delay Field in the Fields list of a plane effector would always crash C4D. Not sure this is related but it is also a problem manipulating objects that are in a layer list. I understand that a bug can corrupt a C4D scene file so that the Volume Builder object doesnt work anymore. What is strange about this issue is that even after a reboot and in a new C4D file a new Volume Builder object would still have the problem. If I encounter the issue again or have some insights that can help I will report it. I hope you can solve the issue, Volumes is really a great addition. regards Jan
  15. Thx, Srek. I did a fresh install of R20 and Volumes works again as it should, hopefully the problem doesnt return.



C4D Cafe is the largest CINEMA 4D community. We provide facilities for discussion, showcasing and learning our favorite software :) Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, get your own private messenger, post status updates, manage your profile and much more. If you need to find solution to your problem or otherwise ask for help, Cafe is the right place.
  • Create New...