The UI elements are made in After Effects and then composited to the C4D scene.

@@ironscavenger Thanks for your prompt response! May I ask one more question if you don't mind, how could you make the shader texture to make the UI have the glow effects?

Yeah, reading the manual always helps and just doing tons of experiments :D

Yes

@@ironscavenger they all receive the same rotation

So of what use is your comment?

Collada (DAE) and then conversion to FBX. Watch the linked tutorial at the end to see my workflow :)

normal ik wont work here. you need contrain tags. YT search for Mechanical Rigging in Cinema 4D | Week 2 and check min 15 or so and onward

Xpresso and Character Contraint Tags

Width controls the distance between the lines and bevel controls a falloff that basically blurs the lines to make them appear softer.

Kann leider keine konkrete Laptopempfehlung geben. Wie beim Desktop-PC auch sollten aber idealerweise die "üblichen Verdächtigen" (CPU, RAM, GPU) gut ausgestattet sein. Zurzeit würde ich immer zu einer nVidia RTX Karte greifen, da CUDA und Raytracing von vielen Softwares und Tools genutzt werden (können). After Effects ist sehr RAM hungrig, hier würde ich nicht unter 32 GB gehen. CPU hängt von deinen primären Softwares ab. Generell gilt aber schnelle Single-Core Performance vs. Multithread. Softwares wie z.B. Cinema 4D profitieren nur bedingt von vielen Kernen - hier lohnt sich also eher ein Prozessor mit weniger Kernen aber schneller Taktzahl. Simulationen z.B. in Houdini oder CPU-basiertes Renderimg profitieren von so vielen Kernen wie möglich, auch wenn diese ggf. niedrigere Takte haben. Wenn du eher Graphicdesign (After Effects, Photoshop und co) lastig unterwegs bist, ist ein Laptop sicher noch ok. Solltest du aber in Richtung 3D gehen wollen kann ich nur dazu raten auf jeden Fall eine starke Desktopmaschine zu holen, da man hier auf einem Laptop auf Dauer nicht wirklich glücklich wird.

Although this is not wrong, it's just not feasible to render images at 2x or 3x the size, especially when producing animations. Rendering at 3x the resolution results in 9x the rendertime, so e.g. instead of 1 day you would wait more than a week for your animation to finish. The example shown in the video is attributed to wrong lighting settings in the 3D software. Having lower intensity lights at rendertime and just fixing exposure in post would have helped here. There would have also been a few rendersettings that could have helped to prevent aliasing. The resolution of the renders has not been changed at any point. EDIT: Typos.

@@ironscavenger One thing will never change, if you source material isn't up to snuff you can't always save it in post. The render was fine. The jagged edges were from upsampling. Anyone who works with CG knows that upsampling pixels is never going to give you a good result. Unless it's got a lot of motion and blurring. If you're making stuff for yourself you can wing it. In a pro environment that won't work.

@@DMDvideo10 ? This render was the exact same size as the After Effects composition. It has not been upscaled in any way. Antialiasing due to overexposure is not an unusual problem when rendering. I don't know what point you're trying to make.

​@@DMDvideo10 I'm a bit late to this discussion, but one thing to note is that aliased edges isn't always from upsampling. For example, I render out all my CG layers without anti-aliasing because it's the only way you'll get accurate results when using ID masks and zDepth passes (which are not anti-aliased). If you've ever seen really bad halo'ing around the edges of a CG render when trying to add Depth of Field using a zDepth pass, this is 100% due to the beauty layer having anti-aliased edges while the info zDepth does not. That being said, you're totally right in that trying to do proper compositing on top of upsampled CG will introduce many problems!