Jump to content


Regular Member
  • Content Count

  • Joined

  • Last visited

Community Reputation

20 Noble Beginner

About janheylen

  • Rank
    C4D Cafe Junior

Profile Information

  • First Name
  • Last Name
  • Location
  • Website URL

Hardware | Software Information

  • C4D
  • OS
    Windows 10
  • GPU

Recent Profile Visitors

1,364 profile views
  1. Thx for the tip, Mike. Working in greyscale with lines is something I will also try.
  2. Thx! This Preview Illumination Adjustment solved the issue.
  3. I'm trying out redshift. The material previews don't update with the renderview running. I understand there's some technical limitation behind this but it doesn't really give a great first impression of a well integrated first party renderer. When using redshift lights and materials the gouraud shading in the C4D viewport looks totally blown out. Is there a way to get a somewhat close approximation of the colours and lightning? In the screenshots below you can see a simple scene with a dome light and an area light. The gouraud shading in the viewport just look
  4. A twitter user posted an amazing technique to smoothly join separate pieces of intersecting geometry. I understand he uses a Houdini Digital Asset (HDA) inside C4D to somehow blend the normals. Can anyone provide some more insight into this? I cannot find more information on it. https://twitter.com/yamadadaikida/status/1275055594043437056
  5. I think you can use a bump or normal map for this look because I don't really see any deformation of the contour shape. It will also render faster and should fix the problem with the distortion of the round edges. If you use a 3D noise you don't even need UV's.
  6. Not all camera types are supported by S&T, Gentleman is one of them I think. I do have a workaround: Use a Front camera. Put your model (or whole scene) in a FFD deformer and morf it so it matches the Gentleman's camera deformation. I attached a scene with the setup. gentleman S&T.c4d
  7. I'm trying to constrain a sphere object (a hand) to an spline point (the end of an arm). I put a point selection in the target field of the clamp constrain. But the sphere sticks to spline itself instead of the spline point. I added three screenshots. 1. The clamp constrain tag settings. 2. The sphere follows the spline point like it should. 3. The sphere doesnt follow the spline point but sticks to the spline I think I must have some wrong settings in the constrain tag. Anybody know how to do this?
  8. Ok I found a solution: releasing the license in my MAXON account did the trick.
  9. Anybody else run into this license server problem? (see screenshot) I can log into my MAXON user account online but for whatever reason when I start up C4D I can not use the program I paid for because of some license server problem. I only installed C4D on 1 machine.
  10. 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)
  11. 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 i
  12. 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?
  13. 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.
  14. 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
  15. 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?
  • Create New...