OctaneRender® for 3ds max® v3.0a9 - 3.0 [OBSOLETE]

[JimStar]

Plugin's version number 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 very first 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...


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 this first alpha version. If something does not for you - you can report it here.


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.0a9 - 3.0

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


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.

[bicket]

Hi Jim Thanks

I think texture 2d transformation scale doesn't work.

[Goldisart]

not updated values maps in the viewport

https://www.youtube.com/watch?v=44JObai ... e=youtu.be

[remKa]

Hello JimStar, thank you for your work.

I'm working on a VR scene with a camera cube map and there is a hhhuuge speed improvment : from 9h to 6h30 of rendertime.

Some issues :

- 1 the gamma setting in the camera imager doesn't respond, it seems that it stucked to gamma = 1. Changing this setting doesn't have any impact (tonemapping is ON), it worked on v2 but not on v3

- 2 with a specular material with scattering, the conversion is wrong, color is reversed by default

- 3 scattering doesn't work with diffuse material

- 4 HDRI rotation doesn't work

- 5 When you have a render region, material modification does not refresh, you have to close OR's Viewport and launch it again


Thank you in advance

[oguzbir]

Thanks Jim for this release,

Here are the bugs I spotted.
- 2D Transformation in RGB image node does not change the texture at all.
Also same applies for HDRI images in environment. Cant rotate hdri.
Edit:________________________________________________
- I was able to make it work.But couldn't able to produce god rays with it. But it seems like it's working Can't make Environment medium work in both Hdri or Daylight scenarios
Edit:________________________________________________
- Using region render in octane viewport stalls the render if perspective viewpoint is changed. Panned or rotated the view
Edit: -Can't find a way to render Volumes. VDB

As another request I would appreciate if you can prepare a sticky locked Gamma topic. And explain in plain words.
- That which workflow makes identical output as pre-2.13 version 'where max gamma was introduced"
- And which workflow is the correct one from now on.
That would be really great. I got confused every time I read your old posts and comparing it with other users comments

[Goldisart]

+1

[oguzbir]

+1

What is this I cant understand?

[RobSteady]

As another request I would appreciate if you can prepare a sticky locked Gamma topic. And explain in plain words.
- That which workflow makes identical output as pre-2.13 version 'where max gamma was introduced"
- And which workflow is the correct one from now on.
That would be really great. I got confused every time I read your old posts and comparing it with other users comments

What about a downloadable sample scene with reference settings?

+1

What is this I cant understand?

"PatOctane" should be "Path Term Power"

[oguzbir]

"PatOctane" should be "Path Term Power"

This is correctly written in max 2014. didn't update max 2016 .Will test soon

[paoloverona]

I'm just testing out the V3 version with a simple scene (Evermotion scene converted for the V2.25 of Octane). two things:
- really good the speed in the new version, 5min 01sec Vs 6min 58 sec (no parameter like "parallel samples" or "max tile" or "coherent ratio" was changed)
- sligthly different light result between two version (renderV3.jpg and renderV2.jpg), but the really strange thing is that if I render every single light source (environment, table light and ceiling lights), there is no difference between the two version of Octane
...where could be the problem then?