Leaderboard

1 layer of noise is almost never enough to create displacement rocks. Your tutorial probably suggested Voronoi noise because it is very good at producing those hard angular formations that other noises lack. However that will look fairly shit on its own. You are also using the worst type of Voronoi noise - the one that gives you that dent in the centre of faces - I would go with one of the other types, which doesn't do that. So what you need is to distort that First noise layer with a second, using the distortion in the filters menu, perhaps driving it with Electric noise, and then layering up a couple of other, more detailed noise types above that on top of it (like Luka / Buya, or FBM for example), but with lessening mix amounts, and in interesting layer modes (overlay or multiply works well) to give you the mid and small-range detail. So, all that goes on within a layer shader, which you can get by choosing it instead of the noise you have now (which will automatically become the first child of it). There is no single 'right answer' or 'perfect setting' I can give you - you have to use your artistic sensibility, and play with all the parameters, and try loads of different combos of noise types and scales until you get what you want. Also, remember that displacement modelling only gets you so far. The last, smallest level of detail should come from the bump map in your material. That can also be (high octave) noise-driven, where you can adjust delta to achieve stunningly sharp final detail. CBR

Maxon is ignoring the fact that they need new users and students to grow. But they have shown a total lack of respect for those users: 1) They got rid of the cheaper versions of C4D (Prime and Bodypaint), 2) They started charging for student versions (while every other DCC student version is free), 3) They refuse to create a cheaper or free indie version, 4) And their subscription price is too high. Subscriptions can be attractive if they are really cheap. I gladly pay my Octane subscription because it is cheap. Adobe slashed piracy with their subscription because it is really cheap too (and they have different prices for different markets, taking in consideration the local cost of living). But Maxon subscription is ridiculous expensive. It's not worthy.

I really don't understant this kind of decisions. I'm sure subscriptions are much more profitable to a company in a long term, but is it worthy to disturb the user community with such decisions and making users leave the software forever? Unlike adobe software , cinema 4d has a LOT more competition. So, removing options like perpetual licensing creates rage among the cinema 4d "veteran" users that use the software for years. Also its not appealing for new ones, knowing that they must spend a lot of money to have a license. Cinema 4d biggest commercial advantage is the price for studios with some anual income. The commercial license is way cheaper than any in autodesk soft and wayyyy cheaper than houdini's. In this case scenario it's ok. However, if your company groes and you need let's say to use some team render nodes via team licenses (in order to work with deadline), then the price per license goes wayy higher. But it ceases to be ok for freelancers or hobbyists that don't make much money per year. In that case, the indie licenses are much more appealing. And there is an enourmous community of c4d freelancers that are already checking other options. Despite the fact that i really like to work with c4d i see somehow a dark cloud above in c4d's future. Users can adapt, so probably what many users will do is: changing software (to blender, or something else with indie) use c4d pirated versions remain in older versions until its not usefull anymore, I fear that if users start to fade away and there is no more new users, this software will start to die like many others (less plugins being written, less help online, etc). Thats why its really important to listen to community advices and wishes. I would keep perpetual, subscription, and a long lasting free learning edition with limitations to at least help new users to integrate (and when i say learning edition i meant to everyone that wants to learn and not just people in school) cheers

Maya. Including Arnold cost me €290 (Minus tax) this year as an Indy licence. C4D - with effectively no production render engine - would cost me €736. More than double. Hard to justify the upgrade from R21. Even with 95% of my work still in cinema. The BIG problem with subs is that you basically lose the ability to open your own files and assets (that you've spent years creating) if you evey stop paying . I dont think that's OK.

As a hobbyist, when I am using Cinema 4D it's an hour here, an hour there. Accumulating the hours I think it's safe to say that over the span of a year I probably am not using it more than a full week (nowadays). With that in mind I definitely am not fond of going subscription now, and am glad I can rely on my trusty R20. Granted, I upgraded yearly from R9-R11 (?) till R21 via MSA, but also spend more time with it back then. Still happy that I didn't take the jump to go subscription then. I seem to remember that in one of the forum discussions David McGavran, at one point in time, mentioned that getting rid of perpetual license was not on the table. Sad to see that this decisions has been reconsidered, for whatever reason. Still, I am not comfortable with reading how he keeps being referred to as the "AdobeGuy", even if it is being used as a pet name/nick name. Over the past weeks I have had been considering getting up-to-date with a brand new perpetual 2023, and use it every now and then for the coming years. With the news from this thread it's clear this won't be happening. I will stick to my R20 for as long as possible. Maybe get tempted to try some Blender, although I am currently not mentally available to learn new stuff. It seems difficult for some to understand that while users can be dissatisfied, they don't want to just Get Over It and simply switch DCC. After having spend more than a decade investing in Cinema4D, and liking it (till R21), I don't simply want to switch and needing to relearn all that is needed, including muscle memory.

Time for Volume 2 i think, kicking it off with a classic , keeping it clean as always 😄

OMG! The pore stretch and wrinkles are incredible. This is all Blender? Amazing! But how easy is it to achieve these types of results? I also get equally amazed at the majesty of Houdini large scale fluid simulations until I actually try to learn how to use Houdini. I would imagine it is the same with anything that comes this close to creating believable humans. The rigging alone must be very involved and take huge amounts of time to master. Then on top of all that are the shading trees to get the pore stretch just right. Now with that all said, at least Blender can get you there. There is no path that I have seen within C4D that will bring you to that same result. And you then have to ask why? The last improvement to character tools were R23...which is oddly right before Maxon purchased Pixologic. And then nothing. Remember what 3D-Kiwi would always tell us: Maxon will not touch any area of a program ahead of its roadmap for a complete rewrite. With this in mind, you have to look at Maxon acquisition of Z-Brush and ask what happens next. Why purchase the world's most pre-eminent character sculpting tool, Z-Brush, and then not provide an equally best-of-breed capability to animate those characters? I think the upgrades to the symmetry tool are the first step in a long road to upscale C4D's character rigging tools to this same level. But once again, outside of Motion Graphics, Maxon is playing catch-up and at a much slower rate than the rest of the industry is moving forward. That may be the price for stability and well-thought-out integration. Fortunately, my passions lie in hard surface modelling and there we have seen enough improvements to keep me happy. Dave

Thank you!! I feel disillusioned!! well, I have to change my glasses? Indeed, I don’t even remember checking the x-ray in the clamp! I have to be more careful, there are many parameters, all important, big thanks to you!!

The only reason the claws disappear is because they were ALSO set to x-ray like the Aquarium. X-ray does not support multiple levels of itself, so if you have a x-ray mesh inside another x-ray mesh it will indeed disappear and that is expected behaviour. On another note, you have some incorrect settings in the Cloth Surface - you are adding unnecessary subdivision, and not adding any thickness with it, which is why it is there in the tutorial ! CBR

Ok, found the problem, not a bug... You have global x-ray mode turned on in view settings. Disable that and everything returns to working as expected ! CBR

But with all that said, I do need to call out Maxon on when and how that decision to stop perpetual licenses with R25 was communicated. Let's start with when it was communicated. Doing it now was actually more damaging than originally perceived for the simple reason that everyone who has purchased a brand new R25 perpetual license over THE LAST YEAR for $3495 now realizes that they wasted their money. There is no perpetual upgrade path for them. If Maxon knew that perpetuals were coming to an end with R25, then that announcement should have been made PRIOR to R25 being released while still allowing R23 license holders the option to upgrade to R25 perpetual. They should NOT be making that decision AFTER R2023 was released. That is just wrong because it takes an important decision away from those who have kept current with their perpetual licenses. If they instead said R2023 is your last chance to get a perpetual license, you now have a choice: Do I upgrade knowing it is the last one or do I jump into subscriptions now knowing that is the only option going forward? Here you have a choice. But making it retroactive to R25 removes that choice and leaves everyone who did upgrade or purchased a full perpetual R25 license feeling a little duped. Adding insult to injury, let's discuss how it was communicated...or rather hinted at during the launch video. Paul Babb's communication on it at the September 7th launch meeting was not clear. It even made light of the growing speculation on using R2023 and the discontinuation of the "S" and "R" release cycle. Here is what he said and take note of how he tried to even make is sound like an after-thought to better hide its hidden significance: That was it. The words were pretty innocuous and did not initially sound alarming. Now in hindsight, we know exactly what that meant. Unfortunately, we did not hear it directly from them but rather had to dig for it. What do we take away from this? Well, we need to call it what it is: they were beating around the bush because they knew there would be backlash. They also left their customer service team to be the bearer of bad news and take the heat from the customer base rather than owning their decision, putting their face on it during the launch meeting, and being straight forward and up-front about it. How they rolled this out also provides some insight into what they think of their perpetual users. As to exactly what that insight is, I will leave up to you. So, while they get points for how they are managing the growth of C4D, they deserve a few demerits on how the decision to cancel perpetual licenses was communicated. Again, just trying to fairly call a few balls and strikes. I challenge Maxon leadership to own their decisions better in the future. They missed an opportunity to show integrity and leadership with this decision and I hope they will learn from it going forward. Dave

Again, same argument as before. What's the incremental cost of maintaining both subscription and perpetual at the same time? Relatively minimal. Even Houdini offers both. Why not have both? Go figure. TBH. Couldn't care less. I already made transition long before so I'm not affected. Any release in R22 to R27. Doesn't make me droll since these features are already existing in my chosen DCC and even better. Except perhapse Python 3. I kinda need Python 3 for future proofing. lol. R21 is still in Python 2. My only regret is buying a personal copy of C4D R21 and on the next release it went subscription and remove the $500 ish upgrade for every release.

It's kind of sucky that they didn't use the most recent version to announce the end of perpetuals so people knew from then on this would be the last, rather than just all of a sudden not have perpetuals, say basically nothing about it, and have the previous year's be the last perpetual. It's a bit of a sleazy way of doing it imo.