Page 1 of 2

OctaneRender® for 3ds max® v2.23.2 - 2.7 [OBSOLETE]

Posted: Thu Sep 03, 2015 11:15 pm
by JimStar
Changes of the 2.7 version
  • Fixed bug: crash when closing the scene during Octane live-session active.
  • Fixed bug: live-session refresh stop after drag&drop of the material or texture.
  • Fixed bug: render elements regression, rendered black in final render mode.
  • Fixed bug: IFL support regression.
  • Implemented the full support of IFL format, including comments and frames-count numbers for each file. Now you can use the full format like this:

    Code: Select all

    ; Anything after a semicolon is a comment, and is ignored.
    sand.jpg 20
    pebble.png
    stone.tif 40	
    boulder.tif 25
  • Minor fixes and improvements...

Changes of the 2.6 version
  • Implemented the native 3ds Max BitmapTex support as the alternative input for Octane Image textures. You can use the Viewport Canvas now to draw "on the fly" on the Octane textures.
  • Minor fixes and improvements...
Changes of the 2.5 version
  • Fixed the GPU setup dialog issues.
  • Fixed the bug: current batch render view animation rendering did not stop completely after cancelling.
Changes of the 2.4 version
  • Fixed the minor bug: the newly implemented textures previews did not refresh in material editor in some cases.
Changes of the 2.3 version
  • Added "Export Octane material" button to Octane materials properties rollout in material editor. So, now you can export some specific material, even just some subtree of full material's setup.
  • Added "Enable texture" parameter to Octane sun.
  • Added "Enable displacement" parameter to Octane render settings.
  • Implemented Octane textures previews in material editor. You need to refresh the previews cache in material editor to get existing "black squares" disappear.
  • Implemented the support of 3ds Max orthographic views.
    Important thing to notice: Octane camera can be thought as some "physical thing" that always has the position. The ortho-views' "cameras" in 3ds Max are just like "infinite frustrums" and always return (0, 0, 0) as "camera" position. So, if such a "camera" (after becoming Octane ortho camera) appears to be right in the center of the scene (or even worse in the center of some object) - you might see some objects "clipped". To avoid this please use the new "Ortho view shift" parameter in Octane's general camera settings. This parameter shifts the ortho-view camera position (along the view direction) away from the Max's (0, 0, 0) position to the needed distance. You can set this parameter to always have Octane's ortho-view cameras positions outside of the whole scene. Don't set this value toooo big "just in case" - as this may cause precision errors.
  • Implemented support of orthographic mode for Octane camera nodes. See new "Orthographic" checkbox in Octane camera rollout.
  • Fixed Octane's native "Focal depth" parameter not working for Octane camera nodes.
  • Minor fixes and improvements...
Changes of the 2.2 version
  • Minor fixes and improvements... No new features, working on making this branch stable...
Changes of the 2.1 version
  • Fixed the bug: the assignment to the complex Octane node parameters from MaxScript did not work. Now you can use MaxScript constructions like

    Code: Select all

    sceneMaterials.Some____Glossy_material.diffuse_tex = RGBSpectrum_Texture()
  • Fixed the render-settings dialog spinners bug.
  • Fixed the issue when some materials did not load from LiveDB.
  • Made the Octane image textures' filepath buttons to have the standard assets menu.
  • Minor fixes and improvements...
Changes of the 2.0 version
  • Implemented the MaxScript support for Octane render settings.
    Big refactoring has been made to achieve this (together with refactoring described in bullet #4), the Octane scene data format has been changed significantly enough to not be able to have the old scenes converted "on the fly". So the scenes made in previous Octane plugin versions will be incompatible with plugin versions starting from this major 2.0 version. Don't switch the current critical projects to this version.
  • Any changes of Octane parameters from inside MaxScript are instantly reflected in UI of rendersettings dialog (if opened).
  • Changed the "filename" parameter type of Octane nodes: now it has the same standard "filepath" type as the same parameters in other 3ds Max native nodes and can be easily accessed from MaxScript.
  • Fully refactored the Octane nodes' parameter ID generation algorithm: the new algorithm allows to easily extend Octane nodes inside 3ds Max by additional plugin-specific parameters in future. Thanks to this change the next feature is already implemented:
  • Added the camera mapping support to Octane image textures. See the new "Camera mapped" checkbox in Octane image textures properties.
  • Octane GPU config now can be stored with scene and accessed from MaxScript.
  • Minor fixes of Octane viewport.
  • "Elements Active" checkbox in render-elements settings is now respected by Octane.
  • Fixed one more Octane proxy preview scaling issue: in the case the scene unit scale was adopted from loaded file having proxies in it.
  • Other fixes and improvements...

DOWNLOAD
THIS MAJOR VERSION'S SCENE FORMAT IS NOT COMPATIBLE WITH PRE-2.0 PLUGIN VERSIONS! DON'T SWITCH THE CURRENT CRITICAL PROJECTS TO THIS AND LATER RELEASES!!!
Read the changelog of this 2.X branch and discussions in previous threads of 2.X versions.
You can use the materials export/import to/from LocalDB to transfer the materials between 1.X branch versions and current versions.

OctaneRender for 3ds Max 2.23.2 - 2.7 (13.2MB autoinstaller file)
OctaneRender for 3ds Max 2.23.2 - 2.7 DEMO (11.7MB autoinstaller file)

For network slave and daemon please download standalone installer here:
http://render.otoy.com/forum/viewtopic.php?f=24&t=46125


Yours,
The OctaneRender® Team.

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Fri Sep 04, 2015 6:58 am
by raylab
Thanks for the ifl support!

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Fri Sep 04, 2015 8:18 am
by raylab
Now that we have BitmapTex support, would it be possible to support the substance map in 3ds max? Thanks!

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Fri Sep 04, 2015 9:38 am
by oguzbir
Thanks a million for the fixes mate.

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Fri Sep 04, 2015 10:18 am
by Jorgensen
hi js

a big thanks for fixing the crash when activating "lock resolution".

jorgensen

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Fri Sep 04, 2015 10:43 am
by Jorgensen
oh well, it still crashes when selecting "lock resolution".....

workround
- disable main card in render setup > devices
- activate "lock resolution" a couple of times
- then reactivate the device

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Fri Sep 04, 2015 11:44 am
by matttrebor
The link with HDR light studio 5 is still broken.
The HDR temp map is not loaded in the rgb bitmap slot ( or standard bitmap map).

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Sat Sep 05, 2015 6:03 pm
by nagboy
Apparently the octane render window closes if you open the 3dsmax render pane.

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Sun Sep 06, 2015 12:17 pm
by Elvissuperstar007
I try to choose a new shader, everything freezes

3ds max 2014-16
OctaneRender for 3ds max v2.23.2 - 1.9
OctaneRender for 3ds max v2.23.2 - 2.7 [TEST]

Re: OctaneRender® for 3ds max® v2.23.2 - 2.7 [TEST]

Posted: Sun Sep 06, 2015 3:47 pm
by mikinik
Elvissuperstar007, I do not have this problem. material is replaced properly.