Jump to content

janheylen

Regular Member
  • Content Count

    41
  • Joined

  • Last visited

Community Reputation

15 Noble Beginner

About janheylen

  • Rank
    Cafe Ronin

Profile Information

  • First Name
    Jan
  • Last Name
    Heylen
  • C4D Version
    R21
  • Website URL
    www.janheylen.be

Recent Profile Visitors

1,050 profile views
  1. In a new scene the IRR fuctions again. I also tried copying the objects from the scene with the broken IRR to a new scene and in this new scene the IRR works again. So that's a workaround but the problem returns quite fast. For example when i'm changing the color of a material the IRR wil sometimes update and sometimes just turn black and not render anything. It seems to be mainly a problem when you change a parameter with a slider. When I enter a numeric value and press enter or change a node connection the IRR will be more responsive (but still not always)
  2. I never had this problem in R20. I never used the IRR much before. But the last few weeks I was learning the node system and for this the IRR worked fine, never had a problem with it. I tried your solution, thx for that, but it didnt work. After several times, changing renderengines and turning the IRR on and off, C4D crashed. I took the opportunity to write a bugreport. Now the IRR updates again, but very slow. Just changing the color of a basic material applied to a sphere lit by one directional light takes almost two seconds to render. In R20 this was almost instantaneously.
  3. I installed R21 and the interface is much sharper and looks good on a 4K screen. So far the good news. Unfortunately the IRR became slower and doesn't automatically update when you change a parameter. (which is the whole point of the IRR) A lot of the time the screen just stays black. When I'm building a shader I rely on the IRR to quickly update when I change something to see the result. Now this workflow is broken. I have to hit ctrl+R all the time to make a screen render. Does anyone else have this problem?
  4. thx Hrvoje, that's what I thought after checking the sprite node in Redshift which has the same limitation. And a BIG thank you for your Youtube series about nodes. I checked (some) of them and the technique to feed noises into the bias input of a gradient turned out to be a golden tip. Noise+gradients are a powerfull combo.
  5. I'm trying to use the Scatter node to distribute an image with an alpha channel over the surface of an object. I can can get cutout shapes that overlap eachother but the transparancy of the image is lost. I found this in the Help docs: Shape Here, brightness values or the numeric values 1 or 0 can be used to shape the UV tiles. Imagine this as an alpha mask that affects UV coordinates. Only the white regions will remain visible (1) and the black regions (0) will be cut off in the UV tile. If in-between values or grayscales are input, the values will be either rounded up or down. Does this mean that it is not possible to have semi transparant pixels when you use the scatter node?
  6. I have to renew my MSA before the end of august. If I would be a Prime user I could do this for 160 euro (without tax) here in Belgium and get the full R21. Because I am a Studio user I have to pay 550 euro (without tax) for the same product?
  7. I really hope this is as great as it looks. It is made by the same talented developer who made the Zbrush Zremesher tool so it should be good. Automated retopo of Boolean, CAD en VDB models is what I would call industry changing ;) The developer said the C4D plugin would come out in the late Fall. (according to someone in another forum who contacted him)
  8. I try to light a scene with an hdri image in a sky object. I have a sphere with a chrome material in the scene and a sky object with a hdri applied to it in the luminance channel. In the render settings GI is turned on. In the viewport I can see the HDRI texture reflected in the sphere but in de final render the texture is not visible. What am I missing here?
  9. 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.
  10. Thx again for narrowing the problem down to the Tile setting in the texture tag, Bezo! Now the problem is totally solved.
  11. 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)
  12. Thx a lot Bezo! That explained and solved the problem.
  13. 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
  14. 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.
×
×
  • Create New...