OctaneRender® for 3ds max® v1.0 RC1a[Test]

Mon Oct 29, 2012 2:58 am

Plankosmos wrote:Hey!

I made a test today with a fresh created scene. I still have the same problem as with the previous two versions: as soon as there are many instances in a scene,the export to the viewport is taking to long. I interrupted the last try after 30 minutes. (I created a scene with three differents shrubs. Therefore i used forest pack and converted the objects into instances via instanciate option, then i made them octane proxies.) Does anyone else have this problem too?

Also I have problems understanding the texture count. It always shows "64/4/32/4" no matter how many textures are in the scene. Is that a bug or am I just not understanding it?

Greetings

Fixed, wait for a new release.

Mon Oct 29, 2012 9:29 am

Thank you Karba, great news!

I am looking forward to the new release then!

Mon Oct 29, 2012 10:17 am

Re, i said that's running well after restarting max, in fact not all the time... I'm running out of system memory while "processing geometry" may be that's the point ? Sometime render work again after changing resolution and open an octane viewport, then re-set the final resolution and render.

edit : i've updated my system from 6gb ram to 12, so it doesn't run out of memory while processing geometry, but that's didn't change anything

.
Scene is taking less than 700mb, my two 580 are 1.5gb models.

I noticed too this : when max samples in an octane viewport are reach, there is no more updates, even if i change some material, viewport, etc. - until i raise a little the max sample so engine is restarting as usual.

Mon Oct 29, 2012 9:45 pm

3ds Max crashes when i rebuild the scene in the viewport render. I was using instances from MS. It works fine once i restarts max until the next time i want to rebuild.

Tue Oct 30, 2012 12:21 pm

larmannjan wrote:3ds Max crashes when i rebuild the scene in the viewport render. I was using instances from MS. It works fine once i restarts max until the next time i want to rebuild.

Memory leak?

Tue Oct 30, 2012 8:25 pm

I was testing if I can reduce my Gforce 480 GTX memory load by installing a radeon card to my system, mostly to run windows and other tasks. Octane 3D Max plugin is not working but the standalone is. Inside 3D max all I get is an empty black render with no geometry loaded. The render setup however recognizes the 480 as a CUDA device. Why is it that the standalone has no issues to render but the 3D Max plugin cant do anything?

Tue Oct 30, 2012 9:01 pm

freelancah wrote:I was testing if I can reduce my Gforce 480 GTX memory load by installing a radeon card to my system, mostly to run windows and other tasks. Octane 3D Max plugin is not working but the standalone is. Inside 3D max all I get is an empty black render with no geometry loaded. The render setup however recognizes the 480 as a CUDA device. Why is it that the standalone has no issues to render but the 3D Max plugin cant do anything?

Do you have just black screen, or checker?

Tue Oct 30, 2012 9:36 pm

Sorry meant to say checker. All the statistics on the screen indicated that nothing was loaded to the card.

Edit: Also using max 2013 and 480 gtx + radeon 6780. W7 too.

Tue Oct 30, 2012 9:37 pm

I have a simple question. How do I change the settings fro the viewport camera?

found it. under render set up

Tue Oct 30, 2012 9:40 pm

oudou wrote:Re, i said that's running well after restarting max, in fact not all the time... I'm running out of system memory while "processing geometry" may be that's the point ? Sometime render work again after changing resolution and open an octane viewport, then re-set the final resolution and render.

edit : i've updated my system from 6gb ram to 12, so it doesn't run out of memory while processing geometry, but that's didn't change anything .
Scene is taking less than 700mb, my two 580 are 1.5gb models.

I noticed too this : when max samples in an octane viewport are reach, there is no more updates, even if i change some material, viewport, etc. - until i raise a little the max sample so engine is restarting as usual.

edit : seem there is none of these problems with max 2013, yeah !
before i was under max 2012, i have vray, final render and unwrella for plugins only on max2012 - some vray object was converted in my scene, and some uses of unwrella to in this scene too. May be it's unimportant, i prefer tell you more than necessary...

reedit ^^ : fake hope, the ultra fast noisy animation bug is still there sometimes with 2013 (but octane viewport is running correctly)