Mike A

Thanks Bentraje - got it : )

Here's a techy question for the Houdini crew : ) In C4D there is a very handy menu command that I use quite frequently: Mesh > Axis > Reset scale (with compensate points on). This is super helpful when you get model that has had it's axis scaled non-uniformly. It resets (normalises) the axis and compensates the point positions so they retain their positions in world space. Is there anything similar in H ?

I think that's a good strategy Dave. I'm just starting a second pass on the Hipflask stuff myself. Too much to try and fully absorb and do at the same time. I've been a trainer myself for many years, so it's helpful to be reminded what it's like to be on the other side of the equation!

Like this? C4D camera culling.mp4

Yes - this is correct. The RS sky model is based on an analytic model of daylight. You can select the older 'Preetham' model, or the newer 'Hosek-Wilkie' model. The latter is recommended. However... Rs also supports the C4D Physical Sky shader as well. So if you want more artistic control you can use that. One note: The C4D physical sky is baked to a texture, so you will need to increase the texture resolution for detailed results - typically 8k+. I'm not in front of Rs right now, but there is a setting in Rs render settings to set the resolution as a default, or you can set it in the material texture node. ** Having written this I'm not sure if the Phys Sky is supported in the new nodes shader system, or just in the older Xpresso shader graph. I'm using the latter in R21.

I think you know the answer to that one 🤣

I 'played around' with Houdini 2 or 3 or 4 times over the last few years... and gave up very quickly. A few months ago I decided to try again and give it some real learning effort. I'm glad I did. It's an amazing piece of software. Is it for everyone and for every requirement? No. Is it perfect? Far from it. I've used various 3D softwares over my career and this is a serious step up from them all. I invested in some good learning materials (Hipflask.how) and after an intensive month or so of serious study I'm beginning to feel quite comfortable in the main SOP (surface operator) context. I'm building useful stuff. I've hardly opened C4D over the last few weeks and when I did so yesterday I actually felt quite lost for a moment! I don't think there is any 'ultimate answer' on the best way to learn stuff like this. You've just got to find your own way by sampling tutorials and learning resources and finding the one(s) that fit with your learning style. That's what I did. After that it's simply a case of 'labour' until you get to that 'tipping point' where things start to make sense. It can be tough to get through that, because there is a lot to learn and a lot of it doesn't always seem to be productive at the time. It's learning the piano and playing scales, it's the woodworker practicing cutting clean joints, it's the language learner getting to grips with the basics... I think the big initial stumbling block for many users is simply the fact the Houdini is so 'fundamental'. Nothing is hidden. Everything can be manipulated. That gives amazing power, but as we all know - with power comes responsibility : ) To 'get Houdini' you really have to know and understand the fundamentals: points, vertices, prmitives, normals, vectors... the sort of stuff you think you know, but it turns out that maybe you don't know quite as well as you thought you did. C4D = screwing together an IKEA cabinet. Houdini = a plank of walnut and a room full of power tools. There are good use cases for both of course : )

Just a off the cuff comment: if you chamfered those edges (ie: a 'flat bevel' ) rather than with a rounded fillet, would that make your life easier, but still offer some reflection action?

I've really no idea, although I should have said that I opened and rendered it with C4D R21 / Redshift 3.5.0.3

19.5 - Impressive!

Yes. This is what I get... LOGO ONLY0450.tif

It is rendering with Alpha (transparency) for me. If you open it in Photoshop or After Effects, are you seeing the transparency?

I've not used Topaz myself, but I've heard great reviews about their video upscaling tool that's in the suite that Zeden linked to.

I feel your pain and sympathize. Thankfully my 3D work is full of hard surface products, and no people.

Why?

Neat video - seconded.

Bookmarked that channel for when I get out of kindergarten and move up to to the big school : )

Thanks for the heads up - I'm looking forward to seeing what's new.

What cards are you using Adam?

PS: If you do need this level of brightness - and you only have a modest number of lights in total, maybe you could solve the problem by duplicating them. Have a visible set of lights with a lower intensity, and a non-visible close duplicate with the required intensity.

You need to reduce the 'Max subsample intensity' - so it is 1, or closer to 1. Render settings > Sampling > Unfied Samling > Filter. This reigns in the values of the overbright - 'whiter than white' - pixels that are causing this antialiasing issue. See the 'Filter' section on this page: https://help.maxon.net/c4d/en-us/Default.htm#_REDSHIFT_/html/Sampling+-+Advanced.html#SamplingAdvanced-Filter If you sample (eyedropper) the pixels of those lights using the 'pixel' tab in the render view settings (the gear wheel icon), you'll find they are around '10' - eg: 10x brighter than 'white'. That very bright value against a black surround is causing these antialiasing issues. The problem is exaggerated by the shallow angle the edges of some of the lights make compared to the horizontal - which always emphasizes antialiasing issues. All told - three things together that each add to the problem.

Maybe you should ask him: When you last bought a car, did you choose one simply on the basis that ' it looked good and had wheels and stuff" ? You have my sympathies.

I didn't know you could do that : )

@Cerberawill be along shortly : ) but I would have thought an extra edge loop or two would be your solution.

Why? It's a good looking well made model as it is.