Leaderboard

If you don't want to use plugins and only the C4D features, you can make your own normal material with 3 layers of falloff shaders in Camera space, linear gradient, each RGB color in one XYZ direction (1,0,0 for red, 0,1,0 for green, 0,0,1 for blue), and make sure you disabled the Color Management in the Image Color Profile render settings. Apply this material fo your objects and the camera will be the render projection. I don't know if it's really that you want but it normally works for this purpose.

Hello, The UV projections occupied my mind for quite a while, I made some tools to unwrap them, to make the edition easily, add features to BP UV Edit... But the problem was still the same, the UV edition is still boring to do and quite often we prefere to use the common automatic projections when it's possible. I was wondering, could we simply make other kind of projections to fit more shapes ? So I came up with a new plugin, the UV Projector ! It works like a deformer object and only edit the UVW property, it have some interesting new UV projections with the advantage to not have to make the object editable ! Here is some new projections : Rhombicuboctahedral : It's like a cubic projection with the 45° edges. Cylinder with deformations : Like the classic cylinder, with deformations to adjust the shapes. Half-cylinder : Some times you want to have only one side round and the other side plane. Y shape : It's maybe still a bit wobbly to setup but it gives a nice start. The last is I think the most interesting, it's a plane shape with editing points : Simply uset he point mode to move the surfaces points and adjust them to your object, you can literraly wrap it around your object ! All the features and download here : https://code.vonc.fr/projecteur-uv The free version is limited to 1000 polygons count with all the features so you can still enjoy it. The plugin is a part of the Vonc Suite that contains others tools. If you have other projections shapes ideas don't hesitate !

Whoa, you were absolutely right - switching the order of the cloner and the sweep immediately fixed the issue. Thank you so much! I had no idea the order of un-grouped objects in the object manager could have an effect like that. I very much agree that it's impressive how many ways there are to do things in C4D. It's always fun to see how different people will approach the same problem. I'll definitely give your method a try after I finish up this project. Thanks again for your help!

Yeah it took me a while to wrap my head around the workflow. I'm still figuring it out but from what I found is: All animation is done in DCC of choice e.g. C4D, Blender etc. Bake out that animation in Alembic and bring into Clarisse. Cameras are also baked out and brought in this way too. All shading and lighting is handled in Clarisse. you can also do shading through Substance. There's a lot of customizing that can be done with Python scripts. A lot of users write and share their scripts for their workflows. I've only scratched the surface so haven't become very knowledgeable of it yet but that is some of what I think is workflow

From the past I remember plugin NlinShader by Frapl... R13 screenshot

Sounds like a priority issue of some sort. I would try putting the Cloner object below the Sweep in the Object manager so that the sweep calculates first. If that doesn't work, then I would consider doing this another way such as animating the Sweep's End Growth parameter to reveal it and then use expresso to match the arrow to the End Growth point, which is how I do stuff like this. I do admire the uniqueness of your approach though which shows how there are so many countless ways of doing the same thing in Cinema.

Ingenious thinking there @Cesar 🙂 Great share... I'd never have thought of that ! CBR

Noticed this as well a few days ago. Haven't read the actual fine-prints, but I guess it has something to do with allowing MAXON to keep your data, etc ... Note that online activation has been present since the first days of R21. One of the reasons why I stick with R20.

Thanks CERBERA for your detailed answer. Interesting to know, I suspected in SDS context non-planar polygons were not really an issue as from past experience the polys often subdivide without any artefacts. It seems it is more a feature for hard surface modelling as you say. Thanks for again for clarifying 👍