keppn

I'm coming to the site mostly on mobile. The red banners are piling up, do I get one for every payment I made? 🙂

CV-LayerComps has been updated a while ago. I've been happily using it in C4D 2023. It also allows you to set a layer, where newly generated objects go ("CV-ActiveLayer") https://www.cineversity.com/vidplaylist/cv_toolbox/cv_toolbox

Sorry, I didn't mean to boast, but rather point out that the Asset Browser shouldn't lock up your system - which hopefully can be solved.

Whatever works! 😄 Also, sometimes it's just the time to walk a new path, even if the first walk isn't the fastest. New tech tends to pay off tremendously down the line, so props to you! Thanks for sharing 🙂

I must admit, I'm flabberghasted by the amount of preparation you're willing to do to achieve a good composite. The workflow seems overly labourious to me, but maybe I didn't grasp the requirements properly. Couldn't you... just model that room, for example?

On my system, "Speedup Asset Search" runs as a background task. I can fully work while it's doing it's thing, even on heavy scenes.

You mentioned " internal mograph cache" in your original Post. I guess, that's what's lost in your tests. Try to save the mograph cache externally. I guess the file size of the external cache will be exactly the size-difference in your test.

Yes, please, more Info! 🙂

Cool tech indeed! The single snippet of geometry you posted above looks quite unintuitive, though... is it hard to develop the form, so it patterns nicely?

The log file should have useful information to help pinpoint the problem. I'd recommend to open a Thread on the official Redshift forum; Adrian and the community are very insightful and can probably read a solution from your provided log. https://redshift.maxon.net

It does hold up even for close-ups, never tried that before, actually 🙂 (Added some texture for the Macro-feelings)

Hmm, no problem here. You can use the attached file for reference. I guess there's something odd about your bump.jpg Laser.c4d

I didn't have time to look at your file, but off the top of my head, you can try these steps: 1. Cache the emitter (Simulate -> Bake Particles) 2. Add a "MoGraph"-Cache-Tag to your cloner and bake the MoGraph Animation 3. Put everything into a "Connect"-Object. Disable "Weld points" 4. Now export the Connect-Object into an Alembic. Try leaving all Export options at the default for the first try. In case you can't solve it this way, there's a plugin called "Nitro Bake" It is a little awkward to buy, install and use, but it actually saved me from going mad two times 😄 https://nitro4d.com/product/nitrobake3/

Ouh, that looks sweet!

Wow, that is priced steeply for a 1.0 release. Strange strategy for a challenger. Also, their marketing stuff is really atrocious, their mails and website look like early 90s stuff. I just hope their product quality is exceptional...

Redshift RT really needed much more time in the oven, even as a beta release. On my system, the "RT"-Button is like a 100%-reliable "System Restart"-Button. They trained me to NOT use their product, in this regard 😕 Anyway, somebody bring the realtime! 😄

Thank you, very insightful! Let's hope for "Unreal for Filmmakers", just like "Blender for Artists". I find the Game Stuff distracting, too, but realtime is certainly the way into the future!

Do you mean: 1 - The blocky cut-out? 2 - The stepping in the flow? 3 - Something else?

Is there some story or idea that connects the well and the sword? Before going into the practicalities, I think it's always worth to ask yourself: "What do I want to communicate? What should the viewer feel? What's the tonality?" Answering these questions first makes it a lot easier to make decisions on movements, camera angles, colors, cuts, etc.

Merry Christmas! Btw, our christmas tree this year is a digital set-extension (via projector🙂) https://photos.app.goo.gl/MVsT4etgQLKiUqaf6

I hope, some day we'll get some well-made presets. Connect "shoelace" to "iron ring", and done - as far as I'm concerned, the technical stuff can remain under the hood...

Personally, I love the Redshift forum. Adrian and the devs have helped me big time, and I learned a lot by reading other people's threads. What I would love to see is the same thing rolled out across all products in the subscription: forum.maxon.net C4D -- New Release Notes -- Technical Support -- Bug Reports -- Wish list (with voting) -- etc Redshift -- New Release Notes -- Technical Support -- Bug Reports -- Wish list (with voting) -- etc Red Giant -- New Release Notes -- Technical Support -- Bug Reports -- Wish list (with voting) -- etc zBrush -- New Release No... ok, it's obvious how that list continues 🙂. This setup just seems like the logical way to do it, instead of scattering efforts across disconnected islands of knowledge. The apps are moving closer together (Magic Bullet in C4D, Redshift in zBrush, etc), and so should the communication around those apps.

Thanks for bringing this up, this capsule sounds super useful!

Yeah, I really wonder what their studio drivers are even for ... if not for this *exact* scenario?!

@FritzUnderstandable! Thank you for pointing out the downside. But shouldn't that also be a problem with Redshift on a dedicated GPU? RS really profits a lot from a dedcated GPU and the data transfer seems unproblematic? I'm no dev though, so I'll just take your word 🙂 @Mike AActually, having the 4090 dedicated for Redshift solved multiple problems for me: There's a nvidia Driver bug going on for a year, that doesn't free VRAM properly of the display card. Having a GPU dedicated to Redshift circumvents the problem altogether The 4090 gives me a _crazy_ fast IPR, almost realtime in most scenes ... and the viewport stays super responsive, because it's handled by the 2080. I can do full renders in the background and still work on lighter stuff in the foreground (Premiere, Photoshop, etc.) The effect of additional overall responsiveness of the system was totally suprising for me. So I'd like to keep the 4090 as the 'monster in the barn', but I hoped I could feed it Pyro as well 😄