Author Topic: Scene Parsing + Ram usage  (Read 5184 times)

2014-04-04, 05:27:47

jjduncs

  • Active Users
  • **
  • Posts: 102
    • View Profile
    • thevisualworkshop
My scene is taking 1 minute 20 seconds to parse the scene. Most of this time the frame buffer and max window are frozen.

Its not a extremely complex scene.. its about 10 different Laubwerk trees with custom corona mats scattered a few hundred times with forest pro 4.15.

The ram usage seems to go steadily up over the 1 min 20s to peak at 15.5gb (I have 16gb Ram).. then drops to about 14.5gb when rendering begins.

Im not sure if its normal, as i dont usually check ram usage when just in max, but having the scene open in max alone is taking up 10gb ram as the only program running. . without rendering.

I guess im just wondering if this slow parsing time and ram usage is normal or if there is something i can do to fix this.

Thanks,

Josh


2014-04-04, 05:59:07
Reply #1

jjduncs

  • Active Users
  • **
  • Posts: 102
    • View Profile
    • thevisualworkshop
I'm actually thinking this could have something to do with how Laubwerk handles the geometry. Laubwerk could be generating the higher poly trees each time i hit render, and taking a long time to do so (i have them set to low poly display in viewprt).

Anyone have experience with this plugin and corona?

2014-04-04, 12:03:34
Reply #2

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
You probably run out of memory, try decreasing internal VFB resolution to 1
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2014-04-04, 17:28:23
Reply #3

borisquezadaa

  • Active Users
  • **
  • Posts: 614
    • View Profile
Wild guess is when reach near 16gb starts to dump todisk and crashes. Laubwerk trees are VERY heavy to render. Maybe converting to proxys could improve.
What i do with Corona My Corona post of random stuff rendering
WARNING: English.dll still loading...

2014-04-04, 18:25:50
Reply #4

jjduncs

  • Active Users
  • **
  • Posts: 102
    • View Profile
    • thevisualworkshop
Yeah i think its actually just Laubwerk trees eating my ram.

Will substitute in some evermotion ones and see how it goes..

Do you suggest making these proxies or will scattering them with forest do this for me?

2014-04-04, 18:44:15
Reply #5

borisquezadaa

  • Active Users
  • **
  • Posts: 614
    • View Profile
I would scatter one or 2 variations of the tree converted to corona proxy with some random rotation and scale. It proves to be better way of doing it than scatter geometry or even instances of geometry (at least for my pc specs).
That way i was able to render a whole mountain with trees on a humble 8GB ram pc once.
What i do with Corona My Corona post of random stuff rendering
WARNING: English.dll still loading...

2014-04-04, 18:56:09
Reply #6

Alex Abarca

  • Active Users
  • **
  • Posts: 459
  • Corona Certified Instructor
    • View Profile
    • Instagram
I proxy trees and then use corona scatter. I also Instance all my copies and it works Ok.

2014-04-04, 19:41:38
Reply #7

nehale

  • Active Users
  • **
  • Posts: 283
    • View Profile
Is there a difference in ram usage between corona proxy and the proxies made by forest pack or multi scatter. Never got the chance to test this theory
I had a girlfriend once.....her name was Vray

2014-04-05, 17:50:54
Reply #8

jjduncs

  • Active Users
  • **
  • Posts: 102
    • View Profile
    • thevisualworkshop
Yeah I will have to have a look at the difference.

But it does seem odd that only about 5 unique trees eat up all my ram (16gb) when scattered with forest, which should in theory be fairly ram efficient.

« Last Edit: 2014-04-05, 17:58:30 by jjduncs »