Maxwell Render | Official public forum

Since the animation capability has been disabled for now, I cannot test this. But I was wondering if the new plugin has fixed the memory bleed problem we had with the older one?

Anybody?

We're working on animation right now. Since the plug-in has been rewritten from scratch, the problem won't carry over (if it's a plug-in problem). If it's a Max problem (caches not being flushed, that sort of thing) we'll of course try to find a workaround before releasing a version with animation support.

I guess it was a plugin related problem. afaik it didn't use to happen with any other pre 1.x plugin version (problem was not animation per sé: each time you exported an mxs max just wouldn't free the memory it used, either you were exporting a sequence or not), and sure it doesn't happen when rendering with any other third party renderer.

edit:
I guess this memory leak stuff can be tested even without animation capabilities, it should just take to export a well sized mxs a couple of times.

can't do it myself without 64 bit plugin.. Michael?

I guess this memory leak stuff can be tested even without animation capabilities, it should just take to export a well sized mxs a couple of times.

We've tested that already and didn't see any problems. We were thinking about interactions with Max when it requests an animation to be rendered.

Mihnea Balta wrote: We've tested that already and didn't see any problems. We were thinking about interactions with Max when it requests an animation to be rendered.

sounds cool. it may be gone for good then

Yipee!