- Posts: 6
- Joined: Tue Apr 30, 2024 9:20 pm
- Real Name: Tristan Cobine
Hello all, I'm new to exploring Fusion, and I'm attempting what seems to be a pretty demanding effect from a tutorial I was trying to follow along with:
Youtube: Morbius Smoke Trails by Nomad R Productions (links not allowed)
I can assume since the default value of the particle generator is 100, it's perhaps pushing things a bit when the tutorial author sets it to 1000, lol. This definitely brings my machine grinding to a halt:
Dell XPS 15, 2023
Windows 11 Pro
32GB RAM
Nvidia 4070
I went and added a boatload of extra VRAM to Windows, but I don't think that helps very much. I reduced the particle count to as low as 200, but it still chokes my laptop to death. I can preview individual frames and make adjustments even though it takes a long time, but when I go to export the 600-frame clip, Resolve simply counts up the expected render time until it inevitably crashes.
I've uploaded a screenshot of my RAM usage as the laptop is trying to encode the file en route to crashing - it's spooling up gigantic amounts of memory. Is this just a really inefficient way to go about achieving this effect? Is it using Fusion improperly? Or is my laptop simply not up to the task? I'm super new to this kind of graphics-intensive work, so please forgive my ignorance, and any guidance would be greatly appreciated!
Kindly,
Tristan
Youtube: Morbius Smoke Trails by Nomad R Productions (links not allowed)
I can assume since the default value of the particle generator is 100, it's perhaps pushing things a bit when the tutorial author sets it to 1000, lol. This definitely brings my machine grinding to a halt:
Dell XPS 15, 2023
Windows 11 Pro
32GB RAM
Nvidia 4070
I went and added a boatload of extra VRAM to Windows, but I don't think that helps very much. I reduced the particle count to as low as 200, but it still chokes my laptop to death. I can preview individual frames and make adjustments even though it takes a long time, but when I go to export the 600-frame clip, Resolve simply counts up the expected render time until it inevitably crashes.
I've uploaded a screenshot of my RAM usage as the laptop is trying to encode the file en route to crashing - it's spooling up gigantic amounts of memory. Is this just a really inefficient way to go about achieving this effect? Is it using Fusion improperly? Or is my laptop simply not up to the task? I'm super new to this kind of graphics-intensive work, so please forgive my ignorance, and any guidance would be greatly appreciated!
Kindly,
Tristan
- Attachments
-
- Resolve RAM usage.png (437.33 KiB) Viewed 446 times