OctaneRender® for 3ds max® v3.0a10 - 3.4 [OBSOLETE]

Sub forum for plugin releases
Forum rules
Any bugs related to this plugin should be reported to the Bug Reports sub-forum.
Bugs related to Octane itself should be posted into the Standalone Support sub-forum.
Locked
User avatar
JimStar
OctaneRender Team
Posts: 3812
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

Plugin's version string consists of two parts - version of Octane core integrated into this version of plugin, and the version of the plugin itself.
Format: v<Octane engine version> - <plugin version>

This is the alpha release, so any issues are expected. Please report the bugs here. For feature requests and other conversations - please use other threads or create a new ones...

Currently the only work on implementing a support of new features that still popping up in all the new 3.X rendering engine releases and bugfixing of already implemented ones will be going on for this plugin. If I will have time in between of this and the other urgent projects I work on - I will be adding some new features of the plugin itself...

Changes of the 3.4 version
  • Fixed bug: lack of SPP indication in region render mode.
  • Implemented workaround for the issue with 2017 image buffer.
If you need, see the changelog of 3.0 alpha 10 rendering engine here:
viewtopic.php?f=33&t=53732

You can read about new features of OctaneRender™ 3.00 here:
viewtopic.php?f=33&t=51679
These features are supposed to work in the plugin starting with first alpha version. If something does not for you - you can report it here.

Previous versions changelog (since major 3.0 release):

Code: Select all

Changes of the 3.3 version
- Implemented Standart Blend material conversion.
- Fixed animation rendering bug.
- Uninstaller now leaves tbb.dll in place.

Changes of the 3.2 version
- Fixed a bug with some nodes interconnections.
- Fixed the lack of "Render elements" tab in render settings of 3ds Max 2017.

Changes of the 3.1 version
- New 3.0 alpha 10 engine.
- Implemented a support of 3ds Max 2017.
- Implemented an opportunity to set up custom channel-IDs of VDB file in Octane OpenVDB object. Leave them empty to use defaults.
- Implemented "3ds Max gamma hack" checkbox feature to workaround the lack of separate gamma setup for render viewport in 3ds Max. Usable only if you need to use camera curves applied on Octane level. Don't use it for linear workflow.
- Added "Minimum" and "Size" fields to baking camera properties.
- Implemented the opportunity to use F-Stop in camera instead of Aperture.
- Improved auto file naming for deep image saved after final render is finished.
- Fixed transform bug in image textures.
- Fixed bug: wrong medium "invert absorption" value after conversion.
- Fixed bug: ortho views rendered incorrectly in final render mode.
- A couple of minor 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 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.

Or the 2-stage converter.


OctaneRender for 3ds Max 3.0a10 - 3.4

For network slave and daemon please download standalone installer here:
viewtopic.php?f=33&t=53732


Please, if you decided to post here:

- Please only report a bugs here. For feature requests and other conversations - please use other threads or create a new ones.
- Give a meaningful description about what you think is wrong and how to reproduce it (in addition to screenshots if any). I can't solve the "one screenshot" rebuses without any meaningful description...
- If you use Google-translator to post here - check please what you got before posting it, and edit it before posting. Ask your friends to check it if you don't speak English. These threads have got overfilled by Google-translator balderdash that is impossible to understand.
- Don't post here the reports about how Octane rendering engine works - use the Octane Standalone forum sections for that.
- If you like to discuss something about the plugin - create a separate thread, don't flood in these testing threads please.
- If you see your post silently deleted from here - you have violated some of above TEST-versions threads rules. These threads need to be kept clean - because they are directly used as the source for fixing and improving the plugin.
User avatar
cmatias
Licensed Customer
Posts: 61
Joined: Fri Dec 28, 2012 8:52 am
Location: France
Contact:

Hi.
Thank you for this new alpha release.
I had the same strange memory behavior than the previous version at the very first start of OctaneRender Viewport , with the memory usage (motherboard RAM).
1. fresh install of the plugin
2. scene load in 3DS Max 2016
3. First click on "open Octanerender viewport"
4. left free Computer RAM is fulfilled by 3DSMAX
5. Octane viewport opens after (around) 25 seconds with "Warning Render Failed !"
6. closing the octane viewport release the used ram.
7. Opening the Octane viewport again works fine with no delay and the render is ok.

I did some screen captures :
octane_maxv3.0a10-3.4[ALPHA]_first_render_ram_and_Fail.jpg
Regards.
Carlos Matias
________________________
3ds Max 2016 on windows 10 / Intel Core i7 3930K / RAM 32GB / 1 x 980 Ti / 1 x 780 Ti / nVidia drivers 365.10
User avatar
JimStar
OctaneRender Team
Posts: 3812
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

cmatias
Can you give me this scene?
User avatar
JimStar
OctaneRender Team
Posts: 3812
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

Thank you!
Your scene triggers some issues in Octane core... The standalone team will look into this.
User avatar
JimStar
OctaneRender Team
Posts: 3812
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

Next version HERE.
Locked

Return to “Releases”