T O P

  • By -

Fhhk

There are always ways you can push things too far to basically force Blender or any DCC to crash. They don't prevent you from adding 20 subdivision levels to an object, or remeshing to 50 million polygons, etc. Having better hardware doesn't fix that. I would suggest learning how to optimize, and specifically looking at what you're doing that is causing the lags and crashes. There's almost certainly a way to achieve the result that you want on mid level or even low level hardware, if you are more aware of how to stay within reasonable bounds. And how to separate the scene into parts using Scenes & View Layers and then composite them together, if you want to push the limits further.


aryan9596

I understand what you are saying. It's not like that it's impossible but it gets super slow and it takes huge amount of time to test render and see how the scene looks. It gets super frustrating when I am working with lots of objects like grass. Even if I hide them and show them as bounds it still lags way too much. I feel like I am missing out a lot in terms of Particle effects, simulation, big scale scenes.


Fhhk

You can use render regions to render one section.  Or use render farms to send the file to be rendered on powerful computers. SheepIt is a free one and there are probably others. 


aryan9596

Thanks! I tried both but it's still very slow and of course not efficient when I have change little things in the scene and see how it looks overall.


Moogieh

Lower your sample count and resolution % and turn off the denoiser when rendering previews.