Page 6 of 6
Re: OctaneRender® for 3ds max® v2.03
Posted: Thu Jul 24, 2014 4:36 pm
by cmatias
perro_abombao wrote:Hi!!! the port to max framebuffer button doesn´t work
Same for me on 3ds Max 2014 64 bits
Re: OctaneRender® for 3ds max® v2.03
Posted: Fri Jul 25, 2014 6:34 am
by acc24ex
how many of you people are using different versions of octane - in order to keep up with older projects and whatever..
- I'm keeping 1.2 version on my max 2014, and the 2.x something on 2013, and 2015 ..
- and I'm constantly shuffling those around - this seems to be the most practical way for me to maintain older versions, but after a while I get mixed up
- only saying because of a real need for a way to change to different versions, for whatever reasons - like I have project that I am still working on, one year later.. and don't want to change to the new kernel, because that means altering 20+ materials..
How about you?
Re: OctaneRender® for 3ds max® v2.03
Posted: Fri Jul 25, 2014 6:48 am
by mbetke
I don't have had any problems so far with older projects.
So I don't keep older versions. If a new version arrives I wait a day or so if people discover serious bugs and update straight to latest version.
It is easy to revert like I had to do with the 2.03 now because of the viewport bug. I render a lot of "5min renders" in 1280px resolution for clients. So I usually do it in the viewport which was a show stopper for 2.03.
Only thing which changed in terms of material was the inverted bumpmap which was fixed some months ago. Otherwise I use also material from my library which are older than one year.