Well as far as I know, this goes for all Subscription models out there, but I might be wrong.

As you have nice CPU, you might wanna check xParticles for C4D. Those are kind of a standard at this point for C4D.

So, if someone decides to invest a large sum of money into the software, they basically have no more support on faulty aspects of this software, less than 6 months after its release? This doesnt feel right at all. When you buy something, this something needs to work as it is intended, full stop. This is the way it was before the subscription model was adopted. My perpetual license of R18 got updates even 1 year afterwards with essential fixes. I understand obviously that new features are added within each release, and sometimes a new feature could already contain a fix for an old p

Tell me how many times you fixed something if QA or Management didn't tell you? And no that doesn't sound like that at all, at least that was not the point and I also mentioned priorities.

Your bend deformer is not ideal here (even with keep Y length ticked), because it can only bend in one direction and the glass bends in 2 directions. And of course it will look 'plonked on' and not part of the glass because that's exactly what it is ! If you really did want photorealism here, you would be modelling that logo into the glass directly (which would require years of experience and fairly insane skills) or cheating via something like the volume builder. But, if the camera isn't too close, or standards aren't too high then most people would just do it with displacement or

You are right. If Chriss Schmidt's presentation had been the official MAXON presentation I could imagine that there would have been less complaints. Therefor it also might be a communications problem.

"Devs only fixes what they are told to fix and nothing more." This sounds very much like resistance from developers to fix anything and they need to be "told" to do so. That is not true. It is always a question of priorities and these are created by evaluating many factors and inputs.

That question should go to management or QA, not devs. Devs only fixes what they are told to fix and nothing more. What they can do is say that its to risky to fix depending on the cycle timeframe but again, severity of the issue also plays part into that. So some issues might not be fixed do to sever risk of braking something else which would cause even more issues. Unfortunately, no you will not see those fixes inside R23 at any point, R23 was closed book after first Service Pack, so if you want to see fixes, you need to upgrade to S24. If you would buy perpetual of

Yeah, I saw yesterday Chris Schmidt´s presentation "live" and must say it was breathtaking...

I have a question regarding bug fixes on each release of C4D to the developers: There was a quite repetitive bug that happened in the timeline, when copying keyframes from one object to another (specially when working with characters, needing to copy a walk cycle from left feet to right feet for example...) that would work in a very inconsistent manner. I've submitted a ticket a few months ago about this, and pointed at this forum for the issue. I've experimented very quickly with S24 last night, and noticed that this bug is now fixed. But, what about version R23? Will it get t

People really need to watch Chris Schmidt's EXCELLENT overview of S24 at RocketLasso before they pass any sort of judgement. He takes almost 90 minutes to explain everything and is very thorough. From the standpoint that this is a 0.5 release (IMHO as it was only six months since the last release), I find it a very respectable set of features. Look....everything in this release is focused on USER EFFICIENCY which is never a bad thing and something which you will only appreciate after you used it for a bit and then try to go back to the old way of doing things. I can see that ha

What you could also use is a Normal map. Bump map are flat, you get no Highlights, but nice for tiny details like scratches, Displacement is usually very high on performance, render speeds while Normal maps are something in between. At least with Normal map you will get highlights form the logo. But for best visuals probably displacement is your friend, especially if you dont have heavy scene to render. Glass in general is really really performance costly so you need to be careful. In the image below you can see how I used Normal map for that logo on the glass.

Well...prior to the subscription roll out you were able to show that perpetual upgrade information for multiple versions of C4D (Prime, Broadcast, Studio, etc). So why is it now so difficult? You did mention an impact if people own multiple MAXON products. Does that imply, as a Redshift owner, that my upgrade pricing for C4D and Redshift will be a bundled price that is lower than if I upgraded each separately? Just looking for clarity as what was once readily available information is now hidden (from a user perspective) and such invites suspicion. Dave

That seems to be only for R19 and below. This changed for R20 and above, so in short, I don't know the way to change this, sorry.

I somehow changed my material preview from the left one to the right one, and I haven't found out how switch it back. Can anyone help me? Many thanks

that would probably be best done with a displacement map, ie greyscale image of the logo applied in the displacement channel of the texture. anything white will be raised and black will stay still ( using intensity as opposed to intensity centred. You can experiment with the softness of the edges to create the curve / bump. You have to make sure your glass has some nice even topology for that and enough of it, but should give a nice result. Deck