Interesting intro to Pyro. 🙂 There are a few things, I don't agree a 100% on: turning all those things on in the Pyro Object will eat up VRAM memory and performance. I would only turn on what you absolutely have to (e.g. density and temperature for interactive look development (i.e. so that you can use the RS render preview)). For a simulation in the viewport only, you don't need to turn anything "on"; keep it "on for export" or "off". The sim will still work, but you cannot scrub back and forth in the timeline. Volume renders in RS, in particular with emissive light from other parts of the volume (e.g. flames) either get very noise or take very long to render. Using Optix noise reduction helps, but also make the renders sometimes look weird (a look I'm not a fan of). BTW: I find it interesting that Maxon beat Insydium to the punch in terms of GPU-based fire and smoke simulations, so Insydium will have to catch up. It'd be interesting to see who is faster, Maxon introducing "Hydro" (my name for a C4D fluid sim) or Insydium with GPU-based Exlposia. But what I'm really looking for in C4D is GPU-based hair simulation.
Thank you for leaving actual constructive criticism, I really appreciate it. So you're saying if I turning on things like pressure and stuff, even if it's not active in my pyro settings will eat up Vram? So I should only turn on the 3 things that are set to 'on export' to begin with for look dev? and maybe even wait to turn them on until I'm done adjusting my pyro and ready to adjust the materials?
@@effectatron "On export" means that the stuff will be cached to disk (as a VDB). "On" means that it will be cached in memory and therefore eat resources. "Off" means that the sim will not be cached in memory or to disk). So for developing the look of the sim in the viewport, you can turn everything off or keep what you finally want to cache to disk "on export". It will then not be held in memory. The drawback is that the you can only play the TL forward and not scrub back. (BTW: you can track VRAM usage with the performance tab in the windows task manager (if you are on a PC).) Only if you want to develop the look with the RS RenderView open (or need to be able to scrub the timeline), you need to turn the appropriate channels "on" so that RS/the timeline) can read the sim data. If you don't turn these channels on, the sim you see in the viewport only "lives" in the view port. Long story short: the main purpose of the Pyro Object (not the Pyro tag) is to decide where the sim data will live/be handled (only in viewport (i.e. in VRAM), also in the RS RenderView or on disk).
And one more thing: you only need the "velocity" channel if you want to render the volume with RS and motion blur. In my testing so far, it doesn't do much but increases render time significantly. So, for most pyrotechnical sims, density and temperature should be sufficient.
Excellent video. According to a Core4D thread there's reportedly a bug in this current version of C4D btw which has been affecting the smoke appearing as it should on initial implementation before you start adjusting any settings. Reinstalling C4D (and I did this myself by deleting my C4D 2023 folder and then just reinstalling it again via the Maxon app) apparently fixes it.
I think a tag for the emission properties of an object and a pyro object for controlling the global simulation is totally intuitive. How would you solve it instead?
Hi, great tutorial! I followed it step by step using C4D 2024 and the results are completely different. I tried but couldn't get it to look like yours :((((
One thing I can tell you about pyro...don't try to go too crazy with it. I locked up my system trying to simulate a cloner of rigid body spheres. VRAm maxed out and so did my system, which unfroze itself eventually but it looks like you need to be careful if you want to do something more than a couple of objects on fire.
Of course, it's amazing and mind blowing to be doing effects like this almost realtime. But Pyro will eat all of your Vram like a snack in a few seconds. That's not even an exaggeration. I'm going to need 24 gb of Vram if I really want to do anything serious with it
how can i limit the simulation to a container so it doesnt get infinitely big? currently it works similarly to adaptive container in fumeFx and phoenixFD, it grows those green brackets when needed and i dont want that
"well optimized" is highly subjective, but I would disagree with this sentiment. I've been pleasantly surprised with the excellent performance on my m1 Max having no issue swapping between my laptop and my 3090 rtx desktop in the same scene, with redshift volume renders set the same on both. Caching is also incredibly fast on the mac. No other vfx program I use (including more generally RS) has comparable performance between those two platforms. I've been moving away from C4d lately but these latest updates have encouraged me to begin using it more again. I do have 64gb of ram on my MacBook so maybe that helps, but I have been very surprised with how well it performs.
No idea personally. But from one perspective, Pyro doesn't cost anything extra. So there's that. But fire making wise, I honestly don't know, hopefully someone that has used it can help you, but pyro has only been out for two days so it's unlikely anyone knows yet.
Lol yea blender also has water! Blender is pretty awesome, but I've used blenders fire and it's not quite as fast and instantly great looking as Pyro so far, but both Def are awesome, blenders fire us pretty solid too, it's an awesome program. I'm just glad Pyro doesn't cost extra haha
![Оптимизация [00] Автоматический Сэмплинг](http://i.ytimg.com/vi/7iqZaqjBXmY/mqdefault.jpg)
![Оптимизация [00] Автоматический Сэмплинг](/img/tr.png)
Interesting intro to Pyro. 🙂
There are a few things, I don't agree a 100% on: turning all those things on in the Pyro Object will eat up VRAM memory and performance. I would only turn on what you absolutely have to (e.g. density and temperature for interactive look development (i.e. so that you can use the RS render preview)). For a simulation in the viewport only, you don't need to turn anything "on"; keep it "on for export" or "off". The sim will still work, but you cannot scrub back and forth in the timeline.
Volume renders in RS, in particular with emissive light from other parts of the volume (e.g. flames) either get very noise or take very long to render. Using Optix noise reduction helps, but also make the renders sometimes look weird (a look I'm not a fan of).
BTW: I find it interesting that Maxon beat Insydium to the punch in terms of GPU-based fire and smoke simulations, so Insydium will have to catch up. It'd be interesting to see who is faster, Maxon introducing "Hydro" (my name for a C4D fluid sim) or Insydium with GPU-based Exlposia.
But what I'm really looking for in C4D is GPU-based hair simulation.
Thank you for leaving actual constructive criticism, I really appreciate it. So you're saying if I turning on things like pressure and stuff, even if it's not active in my pyro settings will eat up Vram? So I should only turn on the 3 things that are set to 'on export' to begin with for look dev? and maybe even wait to turn them on until I'm done adjusting my pyro and ready to adjust the materials?
@@effectatron "On export" means that the stuff will be cached to disk (as a VDB). "On" means that it will be cached in memory and therefore eat resources. "Off" means that the sim will not be cached in memory or to disk).
So for developing the look of the sim in the viewport, you can turn everything off or keep what you finally want to cache to disk "on export". It will then not be held in memory.
The drawback is that the you can only play the TL forward and not scrub back. (BTW: you can track VRAM usage with the performance tab in the windows task manager (if you are on a PC).)
Only if you want to develop the look with the RS RenderView open (or need to be able to scrub the timeline), you need to turn the appropriate channels "on" so that RS/the timeline) can read the sim data. If you don't turn these channels on, the sim you see in the viewport only "lives" in the view port.
Long story short: the main purpose of the Pyro Object (not the Pyro tag) is to decide where the sim data will live/be handled (only in viewport (i.e. in VRAM), also in the RS RenderView or on disk).
And one more thing: you only need the "velocity" channel if you want to render the volume with RS and motion blur. In my testing so far, it doesn't do much but increases render time significantly. So, for most pyrotechnical sims, density and temperature should be sufficient.
@@C4DRS4U Thank you! Good info!
@@effectatron You're welcome. 🙂
Dude has the best C4D tutorials, saved me so many times!! Thanks for the very fast intro to pyro :)
Thank you so much! I can't wait to blow some stuff up with Pyro lol
I've been invested in X-Particles and Embergen for quite some time. The fact that this is now native in C4D is mind blowing.
I know right? Can't wait for water, surely it'll be soon.
Sad because I actually started learning blender for similar effects 😢
This channel is so fking underrated. I know 3D artists are overall but, this guy should be one of the top well known ones for sure.
Ha thanks!
Thank you veru much for the tutorial!❤🔥
Great jumpstart to Pyro!
Thanks to you!
Fab - thanks so much for sharing!
Thank you for watching!
Excellent video. According to a Core4D thread there's reportedly a bug in this current version of C4D btw which has been affecting the smoke appearing as it should on initial implementation before you start adjusting any settings. Reinstalling C4D (and I did this myself by deleting my C4D 2023 folder and then just reinstalling it again via the Maxon app) apparently fixes it.
loving your work :)
Thank you!
Thanks man you rock. Would love to talk further some day.
Great overview, thanks!
cool feature hope Maxon implement mouse hover explanation for each toggle
I would love that
Thanks!
No, thank you!
You are realy good tutor 👏👏
Thank you so much!
Thanks
hey thank you Ryan!!
@@effectatron Of course! You're content has always been LIT, even before pyro. haha
I think a tag for the emission properties of an object and a pyro object for controlling the global simulation is totally intuitive. How would you solve it instead?
Hi, great tutorial! I followed it step by step using C4D 2024 and the results are completely different. I tried but couldn't get it to look like yours :((((
One thing I can tell you about pyro...don't try to go too crazy with it. I locked up my system trying to simulate a cloner of rigid body spheres. VRAm maxed out and so did my system, which unfroze itself eventually but it looks like you need to be careful if you want to do something more than a couple of objects on fire.
Yeah, there's def a sweet spot for performance and look
need a super PC for that, M1 macbook is crashing a lot
I'm hoping Maxon is working on something like Pyro for liquids.
Hydro hopefully :)
Of course, it's amazing and mind blowing to be doing effects like this almost realtime. But Pyro will eat all of your Vram like a snack in a few seconds. That's not even an exaggeration. I'm going to need 24 gb of Vram if I really want to do anything serious with it
Please showmake a video for how to install forster plugin for C4D 2023.1 ???????
I wish I had it
how can i limit the simulation to a container so it doesnt get infinitely big? currently it works similarly to adaptive container in fumeFx and phoenixFD, it grows those green brackets when needed and i dont want that
Here is a video on that th-cam.com/video/_c-mARL7JNA/w-d-xo.html
can i ask your hardware specs on this vid? (cpu+gpu?)
is there a way you can make the smoke go in the z axis? Like say you want to make like a sky scene with a meteor in it.
Yes you can also use forces. Such as wind!
@@effectatron I'm salivating
@@vatop1304 same lol
Not very well optimized for M1 macs. But cool to have in c4d. houdini pyro sims seem better optimized for m1s at the moment.
"well optimized" is highly subjective, but I would disagree with this sentiment. I've been pleasantly surprised with the excellent performance on my m1 Max having no issue swapping between my laptop and my 3090 rtx desktop in the same scene, with redshift volume renders set the same on both. Caching is also incredibly fast on the mac.
No other vfx program I use (including more generally RS) has comparable performance between those two platforms. I've been moving away from C4d lately but these latest updates have encouraged me to begin using it more again.
I do have 64gb of ram on my MacBook so maybe that helps, but I have been very surprised with how well it performs.
Between Pyro and Turbulence FD.. which is better..,
No idea personally. But from one perspective, Pyro doesn't cost anything extra. So there's that. But fire making wise, I honestly don't know, hopefully someone that has used it can help you, but pyro has only been out for two days so it's unlikely anyone knows yet.
Welcome to blender 20 years ago, laughs in free
Lol yea blender also has water! Blender is pretty awesome, but I've used blenders fire and it's not quite as fast and instantly great looking as Pyro so far, but both Def are awesome, blenders fire us pretty solid too, it's an awesome program. I'm just glad Pyro doesn't cost extra haha
Blender users always acting like everyone else has never heard of blender lol. Blender? What's that? Is it free??
Can you render with standard render?
Standard? I'm not sure, probably physical renderer. I haven't used those since I've gotten redshift to be honest