OTOY Forums

darkline wrote:I have a big error with 3dsmax 2013 (64bit).

I've got a scene which I can load into the octane viewport fine, it's a large scene. But when I go to render a sequence properly it just hangs, never gets past 'processing geometry'. Render resolution is identical. Any thoughts?

I will make release 1.10 soon. Probably it will fix your issue.

Thanks Karba, I've got back a few version at the moment to see if it will resolve.

gabrielefx wrote:@Karba

when you think to fix the memory issue in animations?

I have a short deadline.

I donno if my systems suffer of this issue, I want to be sure that there aren't any problems launching render sequences.

Anyone here tested Backburner?

I can't reproduce memory leak in animation. I had rendered a lof of animations without this issue.

hi Karba, would it be possible to make a close file like vray proxy mesh in the future??i mean the coming next release??

I just lost all my changes i made to a scene.
There is still a memory leak somewhere. Max still keeps running out of memory while working with Octane.
I'm on a tight deadline here and stuff like that makes things a bit difficult to handle. I have a large scene and I can only refresh Octane view 2-3 times when all my ram is gone. The scene itself takes 1.8 gigs of memory, but after 2-3 times of rendering it with Octane it's over 8 gigs.
My workflow atm is, that I have to save and restart Max after 3 Octane renderings.

This needs to be fixed asap!

Suv

Hi Suvakas

If I work with large scenes (for example an apartment with different rooms full filled of furnitures) and I do several adjustments with Octane after closing Max it will crash.
This issue always happens.
Remember that I use all my 4 GTX580 for the realtime render (I will see what happens with my new system with 4 GTX680)
I think that Nitrous driver interferes with Octane kernel and when we quit Max it will crash
If I work with simple scenes there are no problems.

How many ram have your system? Mine 24GB

BTW Max often crashes itself (Max 2012 64)

I think it's something about the "refresh" button on Octane view. Or i don't know.. it's up to Karba to investigate.
If I don't use the refresh button (the one with green arrow on it) and close Octane view before re-rendering, then Max doesn't crash so offten.

@gabriele
I have 12 gigs of ram. But the scene I'm working with at the moment isn't so heavy. It takes less than 2 gigs of memory if I use Mentalray.

suvakas wrote:I just lost all my changes i made to a scene.
There is still a memory leak somewhere. Max still keeps running out of memory while working with Octane.
I'm on a tight deadline here and stuff like that makes things a bit difficult to handle. I have a large scene and I can only refresh Octane view 2-3 times when all my ram is gone. The scene itself takes 1.8 gigs of memory, but after 2-3 times of rendering it with Octane it's over 8 gigs.
My workflow atm is, that I have to save and restart Max after 3 Octane renderings.

This needs to be fixed asap!

Suv

Can I have your scene?
[email protected]

If it is possible, try to remove as many object as possible which don't cause memory leak.

Well sadly it's a commercial scene and I'm not allowed to share it.
I'll try to reproduce the issue with some basic teapot scene when I get some free time.

Suv

issue:

assign an rgb spectrum texture to the texture environment slot has no realtime effect changing rgb values.