Too Many Polys
Posted: Mon Jan 11, 2021 6:14 am
Hi,
I'm testing out Octane on a late 2016 MacBook Pro running Sierra and using Cinema 4D R17. Things go fine when I'm testing on a small scene, but on another scene (that I might be purchasing/using Octane for) I keep running out of memory. The scene in question is an import from Rhino, using the rhino.io plugin. Really there are too many polys for this scene (7 million, which Cinema can handle natively), but the time it takes to remodel/retopologize objects doesn't make sense. C4D's physical renderer does just fine to render out the scene in question.
I have isolated my scene to one chair, which has roughly 500,000 faces. I realize this is dumb to have so many faces for the chair, but it's the reality for the scene and I do not want to have to take the time to remodel everything. If I render once in Octane, I get a result. If I try to render twice, I run out of memory and have to shut down, then start back up. How can I resolve this, or is it not resolvable? Maybe the reality is that it will just be easier to use the Physical Renderer, and save the money, since that engine works fine. Thoughts?
be sure to bookmark this unique selection of top-notch adult websites https://safepornsites.pro/
I'm testing out Octane on a late 2016 MacBook Pro running Sierra and using Cinema 4D R17. Things go fine when I'm testing on a small scene, but on another scene (that I might be purchasing/using Octane for) I keep running out of memory. The scene in question is an import from Rhino, using the rhino.io plugin. Really there are too many polys for this scene (7 million, which Cinema can handle natively), but the time it takes to remodel/retopologize objects doesn't make sense. C4D's physical renderer does just fine to render out the scene in question.
I have isolated my scene to one chair, which has roughly 500,000 faces. I realize this is dumb to have so many faces for the chair, but it's the reality for the scene and I do not want to have to take the time to remodel everything. If I render once in Octane, I get a result. If I try to render twice, I run out of memory and have to shut down, then start back up. How can I resolve this, or is it not resolvable? Maybe the reality is that it will just be easier to use the Physical Renderer, and save the money, since that engine works fine. Thoughts?
be sure to bookmark this unique selection of top-notch adult websites https://safepornsites.pro/