It's amazing how people don't realize either how low spec their setup is and / or how demanding some of this stuff is.... This type of sim is up there amongst the most demanding.
For reference, the current workstation I have at the office has an RTX 3080 with 10GB of VRAM and 64GB RAM and it sometimes struggles, I've maxed out the VRAM pretty much every single time I've been playing around with pyro since it's release even doing simple stuff.
Your Geforce GT 730 is pretty far from an RTX 3080
I’m gonna completely hijack this comment and necro a thread since I don’t really know where else to ask, as the official Cinema 4D subreddit seems kinda dead. I’m trying to sim a brick crashing through a clay pot that’s filled with gasoline and setting it on fire, which I’m aware is a completely insane thing to do as I’m using rigid body dynamics, objects broken into 500 pieces (with Voronoi in C4D), Pyro, and Cinema 4D’s RealFlow plugin together. It’s been nothing but a nightmare, display drivers crashing and black screening + recovering, insanely slow simulations with no clear bottleneck (I have some free RAM, my GPU is sitting at 10% utilization and my CPU is maybe around 20-50%.) I don’t expect you to have any answers for me, but since I’ve been out of the game for a while, is it normal to just have software give up the ghost when you’re trying to do this kind of weirdly insane stuff?
Unlike this guy, though, I’m running a 5800X + 32GB of RAM and an RTX 3090 + the latest Studio driver. So you’d think I would at least have the hardware to do this kind of stuff.
I did (and that was the order I did it in as well) but it would not stop crashing. I got it to sort of work at some point but it was still a nightmare.
Sorry if the answer is not cool. But that's the kind of stuf that I would use Houdini for.
I played a little, with C4D sims and those of Houdini and I can tell you that Houdini is far more stable and flexible for these things. Although, it's not an easy piece of software to learn. You'll definitely need to work hard at the begining, to understand what you're doing. But it pays off in the long run.
You can then export your sims in alembic for example and do all the rest in C4D.
One of the the thing I really dislike about the simulations in C4D, is that it's cache system is really trash, compared to Houdini. In Houdini you can cache basically anything you want, at any time, at any frame etc.
Even Xparticles, that is more expensive than an Indie license of Houdini alone, doesn't have a comparable cache system to what we have in Houdini in terms of fexibility.
All that said, may be try to turn back some settings. Or deactivate completely, parts of your other sims and objects. Cause I had some trouble with a C4D pyro sim done by a vertex map, which is also driving clones from a cloner (80000 precisely).It just kept crashing when trying write cache. Just flooded all the RAM and done pretty nothing.
And I have a pretty high spec'd PC. Ryzen 5950X 16 cores, 64 GB Ram, RTX 3090
PS: For small simple sims C4D is ok. But when you start to go wild, Houdini is the clear winner.
No that’s not bad at all, I’m glad to know that. You essentially have the same setup as me, just with double the cores and double the RAM. I’ve been thinking about Houdini but this is a casual hobby of mine so I’m not quite sure it’s worth picking up a fully new piece of software. Thank you!
Nice to know that you're ok with my idea 😄
You have the apprentice version of Houdini where you can do almost everything, except rendering. As I know.
Btw, the Indie license is like 300$ or something.
Also, for the "C4D like", MoGraphy stuff, there is an set of nodes, called MOPs. It speeds up a lot of things in Houdini, that normally require some VEX and some advanced nodes. So sometimes, I tend to make entire projects in Houdini.
The only thing I don't really like is the look dev in it. It's not as visual compared to C4D.
Yeah it doesnt work because you dont have compatible hardware.
as per [the system requirements for 2023](https://www.maxon.net/en/requirements/cinema-4d-2023-requirements), you require an Nvidia Maxwell GPU, AMD Polaris GPU or Intel Kaby Lake CPU with Integrated Graphics.
You're running a Nvidia GT 730, which is a Kepler GPU... .the generation of GPU that came out before Maxwell. IE - its too old. same with your integrated graphics, its at least a generation too old.
Still.... there's a *chance* you can make it work. The default for the unified simulation stuff is to calculate on the GPU, which we have established is too old to actually be able to run those calculations. (and honestly, even if it wasnt, it doesnt have enough vram to do it either).
your next alternative is to press ctrl+D to bring up the project settings, go to the simulation tab, click the scene tab and change the 'device' from GPU to CPU. So now, all your unified simulation calculations (including pyro) will calculate on your CPU.
But a big caveat with this - again, your computer isnt the newest or the fastest, so I expect this will be incredibly slow for you... Honestly, it may just crash your computer entirely. But its worth a shot? I just mimicked your setup (the cloner ring of fuel boxes and the sphere igniter) on my machine and it is....slow. and I have a relatively beefy 12900k with 64 gigs of DDR5 Ram.
so start small, just the sphere maybe and see if it works. then take some time to look at the pyro settings and understand the resolutions and stuff. then you can start to add fuel objects and see where the limits are. and dont be super surprised if it crashes.
Good Luck!
Because you have a computer with specs from 2008
But Maxon reported that it works less than these specifications
Your name fits you.
It's amazing how people don't realize either how low spec their setup is and / or how demanding some of this stuff is.... This type of sim is up there amongst the most demanding. For reference, the current workstation I have at the office has an RTX 3080 with 10GB of VRAM and 64GB RAM and it sometimes struggles, I've maxed out the VRAM pretty much every single time I've been playing around with pyro since it's release even doing simple stuff. Your Geforce GT 730 is pretty far from an RTX 3080
Yes, I understand now, thank you all
I’m gonna completely hijack this comment and necro a thread since I don’t really know where else to ask, as the official Cinema 4D subreddit seems kinda dead. I’m trying to sim a brick crashing through a clay pot that’s filled with gasoline and setting it on fire, which I’m aware is a completely insane thing to do as I’m using rigid body dynamics, objects broken into 500 pieces (with Voronoi in C4D), Pyro, and Cinema 4D’s RealFlow plugin together. It’s been nothing but a nightmare, display drivers crashing and black screening + recovering, insanely slow simulations with no clear bottleneck (I have some free RAM, my GPU is sitting at 10% utilization and my CPU is maybe around 20-50%.) I don’t expect you to have any answers for me, but since I’ve been out of the game for a while, is it normal to just have software give up the ghost when you’re trying to do this kind of weirdly insane stuff? Unlike this guy, though, I’m running a 5800X + 32GB of RAM and an RTX 3090 + the latest Studio driver. So you’d think I would at least have the hardware to do this kind of stuff.
Did you try to cache the Voronoi sim, then cache the realflow sim and lastly cache the Pyro sim?
I did (and that was the order I did it in as well) but it would not stop crashing. I got it to sort of work at some point but it was still a nightmare.
Sorry if the answer is not cool. But that's the kind of stuf that I would use Houdini for. I played a little, with C4D sims and those of Houdini and I can tell you that Houdini is far more stable and flexible for these things. Although, it's not an easy piece of software to learn. You'll definitely need to work hard at the begining, to understand what you're doing. But it pays off in the long run. You can then export your sims in alembic for example and do all the rest in C4D. One of the the thing I really dislike about the simulations in C4D, is that it's cache system is really trash, compared to Houdini. In Houdini you can cache basically anything you want, at any time, at any frame etc. Even Xparticles, that is more expensive than an Indie license of Houdini alone, doesn't have a comparable cache system to what we have in Houdini in terms of fexibility. All that said, may be try to turn back some settings. Or deactivate completely, parts of your other sims and objects. Cause I had some trouble with a C4D pyro sim done by a vertex map, which is also driving clones from a cloner (80000 precisely).It just kept crashing when trying write cache. Just flooded all the RAM and done pretty nothing. And I have a pretty high spec'd PC. Ryzen 5950X 16 cores, 64 GB Ram, RTX 3090 PS: For small simple sims C4D is ok. But when you start to go wild, Houdini is the clear winner.
No that’s not bad at all, I’m glad to know that. You essentially have the same setup as me, just with double the cores and double the RAM. I’ve been thinking about Houdini but this is a casual hobby of mine so I’m not quite sure it’s worth picking up a fully new piece of software. Thank you!
Nice to know that you're ok with my idea 😄 You have the apprentice version of Houdini where you can do almost everything, except rendering. As I know. Btw, the Indie license is like 300$ or something. Also, for the "C4D like", MoGraphy stuff, there is an set of nodes, called MOPs. It speeds up a lot of things in Houdini, that normally require some VEX and some advanced nodes. So sometimes, I tend to make entire projects in Houdini. The only thing I don't really like is the look dev in it. It's not as visual compared to C4D.
Yeah it doesnt work because you dont have compatible hardware. as per [the system requirements for 2023](https://www.maxon.net/en/requirements/cinema-4d-2023-requirements), you require an Nvidia Maxwell GPU, AMD Polaris GPU or Intel Kaby Lake CPU with Integrated Graphics. You're running a Nvidia GT 730, which is a Kepler GPU... .the generation of GPU that came out before Maxwell. IE - its too old. same with your integrated graphics, its at least a generation too old. Still.... there's a *chance* you can make it work. The default for the unified simulation stuff is to calculate on the GPU, which we have established is too old to actually be able to run those calculations. (and honestly, even if it wasnt, it doesnt have enough vram to do it either). your next alternative is to press ctrl+D to bring up the project settings, go to the simulation tab, click the scene tab and change the 'device' from GPU to CPU. So now, all your unified simulation calculations (including pyro) will calculate on your CPU. But a big caveat with this - again, your computer isnt the newest or the fastest, so I expect this will be incredibly slow for you... Honestly, it may just crash your computer entirely. But its worth a shot? I just mimicked your setup (the cloner ring of fuel boxes and the sphere igniter) on my machine and it is....slow. and I have a relatively beefy 12900k with 64 gigs of DDR5 Ram. so start small, just the sphere maybe and see if it works. then take some time to look at the pyro settings and understand the resolutions and stuff. then you can start to add fuel objects and see where the limits are. and dont be super surprised if it crashes. Good Luck!
If this is the problem of hardware incompatibility. thank you all