OTOY Forums

3dgeeks wrote:If not on the fly, could the Vray convert Tool be re-purposed into an Octane to Octane utility?

Are you ever reading what was written here?..

JimStar wrote:The only opportunity here - is to have complicated external standalone "two-stage" convertor application working with two scenes, opened in different 3ds Max processes having different Octane plugin versions loaded. If some of you need it - they can try to write it. This is a huge amount of work which I can't spend on this.

found in this release = not saved svoystva ways to bitmap files after saving *.max file. Please correct ( лично у меня исчезают HDRI карты окружения)

As you say JimStar, this is a TEST zone and no one can complain about broken compatibility.

Thanks a lot for your job and for your patience.

I have found another bug:

The Alpha image map can't work because the file format is "Alpha Image " and that can't be changed.

ka-ra wrote:The Alpha image map can't work because the file format is "Alpha Image " and that can't be changed.

Could you please describe more in detail what is not working?

I also put a lot of work into own material files and custom materials for third party model libraries to be able to assemble scenes qucikly which affects my working time and calculations. I earn money with my work. No student stuff or hobbyist work. This means I have limited time for projects and do not model each chair and table on my own. How Octane works now it is just perfect feature wise.

Does it mean I would have to touch up hundreds of models in my library again to make them work with further Octane Versions?
Do I need all data twice for pre-2.0 scenes and post-2.0 to have objects looking right?
I didn't understand this point clearly.

I'd like to know what are the benefits of this release in the long term.
Plugins?
I hope that Otoy will develop all the necessary tools for Octane without wait for external plugins.
Example:
do we need a plugin to draw lights with target point? No. This must be included.

regards

There is still a bug in the color corector node. As I posted in previous releas post.


somethings hapens when you try to offset the color from green (0.255.0) to magenta (255.0.255) Then it loos it´s color. see image

Best
Daniel

If Maxscript works with this new JimStar release (so that you can assign properties of Octane material from script), then its possible to write a converter from old to new Octane material using Maxscript. It's a bit of work though and would need some spare time.

Suv

suvakas wrote:If Maxscript works with this new JimStar release (so that you can assign properties of Octane material from script), then its possible to write a converter from old to new Octane material using Maxscript. It's a bit of work though and would need some spare time.

Suv

I don't think so if i understand what Jimstar said correctly.
the "old" octane material is a dead end due to the lack of maxscript support for getting/setting parameters.
you can't convert "old" octane materials to other type(vray, mr, and vice versa) via maxscript, that's why this test version was developed.

the most possible way for now is to convert them manually i think.