keppn

Yeah, I assumed even midrange wouldn't be achievable with Nexus, but I'd love to be proven otherwise. I have no time atm to try it out myself...

I don't care for renderings – I just want to see the viewport buuUUURRRRrrn! (I love Embergen 😊)

I would be happy with a mid-scale-solution working inside of C4D - think "Car is splashing through a big puddle". Imho, neither xParticles nor Realflow(C4D-Plugin) can do that in a way that is not painful. Judging from the sneak-preview, Nexus is not going to change that 😞

Every example scene was quite small-scale, so I'm not that excited 😕

It's not just UI though, a lot of workflows are just really convoluted. I'm still happy that I once managed to export a low-res Mesh with matching Displacement for Hi-Res Details and UVs to C4D... that was a downright horrifying experience, haha 😅

Second that. I doubt they'll revamp the whole thing though, they're too far down the rabbit hole. Plus, I think the zBrush-Comnunity suffers from collective Stockholm syndrome 🙂 But maybe they can offer an alternative UI, like 'Blender for Artists', for example. Still, a ton of work. But if anybody could do it, it's Maxon, so I hope they will ..

Great release, lots of cool and useful stuff 🤩 Extra thanks for implementing WatchFolders in the Asset-Brower, I really do feel heard. 👍

Personally, I don't need a single new feature -- only speeeeeeeeeeeeeed!

Hahaha, thanks guys! 🙂

So, for the first time ever I attempted to model something organic with Lego, instead of C4D 😄 It totally felt like making Pixel-Art in 3D, with a lot of similar challenges regarding volume preservation and readability. How do you like it?

Thank you so much @Icecaveman 🙂 Ah, meetings and opinions... or worse: Opinions in Meetings! The way I'd defend that detail: "That's the antenna and sensor array, man! Do you want this ship to fly blindly? Do you want it to crash? Do you want your future grand-grandchildren to crash with it?!" On another note: While modelling, I tried to imagine the different use-cases. How does it land, when it picks up a container? How should the cockpit look, to give the best overview? What are the engines for In-orbit-Flight? (In the wings). What is the hyperlight-Engine? (On Top). How can the frame accomodate to cargo of different sizes? You get the idea. In a lot of ways, this thinking first felt limiting, but in the end, it led to more interesting-looking solutions. See: Antenna array 🙂

Ha, let me get a super old design of mine out of the garage. This must be from the Cinema R10 era, when I bought my first license and began to dabble with 3D for realz 😄 So, please be gentle with critics 😄 The design is about a carrier spacecraft - more or less, just a "strap-on-engine" to standardized modular containers. In this case, for people 🙂 I was interested to explore a design that combines extremes... a fat block of unwieldy cargo, but combined with some delicate elements reminding of dragonflies or seagulls. Some topics mentioned in this thread can be recognized as well... areas of high detail vs low detail, lights for scale, core/shell etc. Random additional infos: - The little yellow globe is the cockpit with 270°-View. There are even little people inside, but I don't have a close-up - I don't think I've posted this anywhere yet, so these are images waiting decades for their premiere😄 - Standard Renderer -- those took ages on some brutal VAIO-Laptop. That thing was so loud XD

The node examples shown here seem somewhat labourious for little benefit. I can handle a redshift material with ~20 nodes, but that's about it. More than that, and (for me) nodes become just too complex to maintain and troubleshoot. All I really wanted from C4D is: keep the goods, but make it 100x faster. I don't want to learn an entirely new and unfinished workflow paradigm to get a speed boost in C4D. If I wanted that, I could just hop to Houdini, where everything is ready and waiting. Packing up the node complexity into easy-to-use capsules was a smart and promising move to integrate node-power into the classic workflow - but so far, I don't see capsules that I would use on a daily basis. Perhaps that is just a documentation/tutorial problem as well. tl;dr -- I just neeed speeeeed!

I'll write some more next week, when I'm back from vacation 🙂

My insights for organization: Proper naming and tagging is vital. I mostly rely on naming folders and files in a "speaking" way. For searching, I use the simple but powerful "Everything"-app for windows. And Adobe Bridge / Connecter for a visual search. Regarding folder structure: I avoid nested folders as much as I can. That seems counterintuitive, but nested folders just lead to less visibility and discoverability of files. In my opinion, "Flat and broad" is the way to go. I tend to not have a very granular folder structure, as most of the times I start my search with a (generic) keyword and finish my search visually. That way I don't have to tag for days and allow inspiration by scrolling through somewhat unsharp search results. I do have an absolutely annoying tick with keeping a strict folder name syntax that borders on being unhealthy 😅. I love looking at a clean directory, and do so since the DOS days 😆

Yeah, it's a lot of work to keep a warehouse of stuff in order. But it pays off big time!

Yeah, the pages are a bit disconnected. Which is quite ironic 😆

https://www.designconnected.com/about

They have an asset shop at https://www.designconnected.com. So I guess they provide Connecter as a free tool to make it easier to manage shopped assets - in a way like Quixel Bridge for Megascans. It seems to work completely offline... in fact, i just browsed the features for the first time in a long while, and they added some stuff like PBR-Previews that seem quite handy. I think I'll give it another try...

Then again, Bridge can't even properly preview HDRI's, just like it's 1998 🙄 So, interesting to see further suggestions!

"Connecter" could be a solution? https://www.designconnected.com/connecter/ I have tried it only briefly. I immediately missed Bridge's ability to render Raw-Files with Lightroom's xmp-Edits. I think I'll never get out of Adobe's grasp, sigh 😅

Try to cut (Ctrl+X) the xRef from the scene and then immediately paste it again (Ctrl+V). Sometimes that solves xRef hiccups...

Yeah, I have the red banner, too. Posting works though (obviously :D)

I'm not sure if it really qualifies as a "Quality of Life"-Feature -- but the Take System is the super-huge thing for me in C4D. I make a lot of product visualizations for my company, and the Take System easily allows me to automate a rollout across the whole product range. It's just so awesome! I love building my own automated asset-assembly lines 🙂 In a way, it's a QoL-Feature, because the end-result would be also achievable "on foot". Only much more painful 😄 Edit: I'm not very familiar with other DCCs - is something similar available beyond C4D?

I've had a similar problem once, and it was fps-related. My C4D-scene was setup with 24 fps. I rendered it as an image sequence and imported that to Premiere. The Premiere project setting was also 24 fps. BUT! When I imported my rendered image sequence, Premiere decided to interpret it as 25 fps -- introducing a very similar amount of jitter as shown in your video. The solution: After importing the image sequence into premiere, go to your project bin, select the clip, rightclick and search for "interpret footage as" (or something similar). In the dialogue, select your correct fps. Only after doing this, use the clip in the timeline. Now everything should be smooth as butter. I guess, the same solution applies to other apps than Premiere as well.