Page 4 of 7

Re: OctaneRender® for 3ds max® v2.20

Posted: Thu Jan 29, 2015 12:58 pm
by darkline
Is poly limit fixed?
is poly limit fixed?
is poly limit fixed?

I ask 3 times because I never seem to get a response when I ask. I bought v2 last year and still I am using V1 because I have high poly scenes. If it is not fixed I think a refund is in order because nowhere did it say when I upgraded that my old scenes would not open in V2.

Sorry to be blunt but it's been 7 months and I cannot use it for the purpose I bought it for.

Even some sort of acknowledgement would help, are you working on this? Will it be fixed, is it low priority for you guys?

Re: OctaneRender® for 3ds max® v2.20

Posted: Thu Jan 29, 2015 2:47 pm
by Goldisart

Re: OctaneRender® for 3ds max® v2.20

Posted: Fri Jan 30, 2015 5:38 pm
by jp_vas
Hi
when using the "use production resolution" option, it doesnt work when locking "image aspect" option... at least for me..
regards

Re: OctaneRender® for 3ds max® v2.20

Posted: Mon Feb 02, 2015 10:03 am
by oguzbir
Hi Karba,
Does the multi uv channels feature could help us to provide W mapping for the hairs (in the future)? Or is it completely diffferent thing?

Re: OctaneRender® for 3ds max® v2.20

Posted: Tue Feb 03, 2015 3:12 pm
by darkline
oh by the way, is the poly limit fixed?

Re: OctaneRender® for 3ds max® v2.20

Posted: Tue Feb 03, 2015 3:33 pm
by gabrielefx
Hi Karba,

many issues in Vray translator found:

Please load the scene #8 of Archinteriors 27. Many planar lights aren't converted and some Vraymtls.
I tried with some old Vray scenes too. Some materials and lights aren't converted. With 1.18 is ok.

Octane issue:
If I load a scene created in Octane for Max 1.18 into Octane for Max 2.2 the planar lights that were invisible now are visible also if the visible option is off.

Octane for Rhino VS Octane for Max:
I don't understand why in Octane for Rhino I got the stereoscopic option. I can render side by side frames.
I need this option implemented in Max.

regards.

Re: OctaneRender® for 3ds max® v2.20

Posted: Tue Feb 03, 2015 3:39 pm
by oguzbir
Gabriele I noticed that error.

I must say. I didn't test this thoroughly But.
- It seems like translator has problems converting especially lights if they are in nested groups. (I mean groups in groups)
Ungrouping worked for me not all but in some cases.

- Also multiple clicking on the convert button sometimes works as well. In every click on the translator, another light is converted. Also there might be an issue where Vray lights in the scene are instanced.
You can try to make the instanced lights unique. Than instance them again by using scripts.
I might work for now.

And there is the visiblility problem as you mentioned.

As I said I'm not %100 sure of these. Hope it helps.

Re: OctaneRender® for 3ds max® v2.20

Posted: Tue Feb 03, 2015 3:53 pm
by gabrielefx
Hi Karba and Oguzbir

Octane for Max 1.18 translates perfectly that Vray scene.

Octane for Max 2.2 failed.

Tried now 1.18 with scene #8 Archinteriors 27

all lights and materials are translated as expected (except some vray special materials not adapted yet)

Re: OctaneRender® for 3ds max® v2.20

Posted: Thu Feb 05, 2015 8:44 am
by vfxman83
Hi Karba;

This version i don't like it there is a lot of bugs.

I decided to return old versions ?

When will you fix and update ?

Image

Re: OctaneRender® for 3ds max® v2.20

Posted: Thu Feb 05, 2015 10:27 am
by 3dgeeks
Yes, we have returned to 2.16 also, as the 2nd UV wasnt implemented for Max, and I wasnt sure i really liked the keep environment but no alpha.

Good work Karba though, its getting close to being fully featured.