OctaneRender® for 3ds max® v1.22a[Test]

[Karba]

This build can be unstable. Don't use it for major projects.

Changes since 1.22

• Random crashes fix.
• Broken info channel kernel fix
• Broken film index fix;

Changes since 1.17

• Image Texture Transforms (scale, rotation, translation).
• Image Texture border modes (Wrap, Mirror, Black, White, Clamp)
• Internal mapping (Planar, Box, Cylindrical, Spherical, Perspective)
• Object Properties (general visibility, camera visibility, shadows casting)
• Optimization of BRDF models
• New Node System (affects performance and stability only, no visible changes)

DOWNLOAD

We have 4 separate archives available for download, for Autodesk® 3ds max® 2010, 2011, 2012 and 2013. For 2014 use files from 2013.
Each archive contains the manual and installation text file, and both 32bit and x64 versions of the plugin,
so you only need to download one archive for your 3ds max® version from the following download links:


3ds max® 2010: http://www.refractivesoftware.com/plugi ... v1.22a.zip (50MB ZIP File)
3ds max® 2011: http://www.refractivesoftware.com/plugi ... v1.22a.zip (50MB ZIP File)
3ds max® 2012: http://www.refractivesoftware.com/plugi ... v1.22a.zip (50MB ZIP File)
3ds max® 2013: http://www.refractivesoftware.com/plugi ... v1.22a.zip (50MB ZIP File)


Yours,
The OctaneRender® Team.

[Elvissuperstar007]

Bug HDRS matte shadow 1.22a

[Karba]

Bug HDRS matte shadow 1.22a

Switch off cast shadow properties on matte object.

[mikinik]

Karba, thanks!

[[email protected]]

Object visibility options!!!!! THANK YOU THANK YOU THANK YOU!!!!!!

[cfrank78]

Hello Karba!

Played with 1.22 and 1.22a for some hours now. AWESOME! Have not had ONE crash! Wow!

Only thing i found out, live DB materials can not be downloaded and be used. Is this normal?

Also In the 1.22 C4D (test)version is in the octane camera tag now native camera motion blur implemented. Will this be implemented in the max version too?

Thanks for your awesome work!

Kind regards Chris!

[oguzbir]

Karba hi,
First thank you for the new release.
I'm writing a maxscript to smooth the way we manage object visibility.
It's almost done and wrapping the code. I'm going to release it soon.

I'd like to add the feature to turn on/off "Moveable proxy" setting right within my script.
Currently the button just opens Octane Object Properties, via

Code: Select all

actionMan.executeAction 982383860 "2398"

And I cannot debug how to turn that directly.
I'm thinking it would be great it we can reach it via single click.

Would you be wiling to port it maxscript.
I'm not a coder just a novice maxscripter. I know you also stated you don't do maxscript.
But I guess it would be somehow easy to let us have access to it.
Cause we can access some other Octane classes like camera or lights.

Best,

[suvakas]

It can be done already. I wrote a script a while ago that does it. I'll try to find the line for you.

Suv

[edit]
Here you go. This line enables Octane proxy (set to false to disable). It's a standard "user defined" object property and yes, it has a typo - "proy" not "proxy". To read the value use getUserProp().

Code: Select all

setUserProp node "octane_movable_proy" true

[bicket]

Karba hi,
First thank you for the new release.
I'm writing a maxscript to smooth the way we manage object visibility.
It's almost done and wrapping the code. I'm going to release it soon.

I'd like to add the feature to turn on/off "Moveable proxy" setting right within my script.
Currently the button just opens Octane Object Properties, via

Code: Select all

actionMan.executeAction 982383860 "2398"

And I cannot debug how to turn that directly.
I'm thinking it would be great it we can reach it via single click.

Would you be wiling to port it maxscript.
I'm not a coder just a novice maxscripter. I know you also stated you don't do maxscript.
But I guess it would be somehow easy to let us have access to it.
Cause we can access some other Octane classes like camera or lights.

Best,

Hi oguzbir
I don't see any "Visible to reflect" feature in 1.22

[bicket]

Karba

I found something strange in the scale transform (compared to 1.20)