Page 2 of 2
Re: octaneimager
Posted: Thu Jan 12, 2017 5:05 pm
by Jolbertoquini
Goldorak wrote:Hi,
I've been posting on other threads regarding the near term roadmap. Once headless rendering is completed (which is being worked on now, and will be fully supported on or before 3.1), we'll have a stable framework and API for OctaneImager extensions going forward. That is why this feature was set for 3.1. The imager extensions such as ICEFX have been ready for a while, and some of them have even been implemented entirely in Octane OSL node (toon shading for example).
Hi Goldorak,
So we could have on Octane now ?
hehe Yes I'm really excited with this new options like the ICEFX
Best,
JO
Re: octaneimager
Posted: Fri Jan 13, 2017 2:41 am
by gah5118
I'd like to learn more about ICEFX... where can I find information on it?
Re: octaneimager
Posted: Fri Jan 13, 2017 5:22 pm
by pegot
+1
What does the ICEFX acronym stand for? I’d like to learn more about this as well but a Google search only brings up stuff on some kind of stock trading system or trader agent software?
Re: octaneimager
Posted: Fri Jan 13, 2017 9:37 pm
by Goldorak
It's our in house library of effects we will ship for OctaneImager (which itself is a generic framework for 1st and 3rd part post effects, utilities (denoising) and filters for Octane.
Re: octaneimager
Posted: Sun Apr 02, 2017 4:14 pm
by ramone163
Any news about ICEFX?
Re: octaneimager
Posted: Sun Apr 02, 2017 5:43 pm
by Goldorak
Module system required for Octane imager is being worked on for 3.07. Hopefully that makes it into the 3.07 release which we will be shifting to once 3.06 is final.
Re: octaneimager
Posted: Thu Aug 03, 2017 6:25 am
by ramone163
Any news about ICEFX? Maybe you can show something and how long to wait?
Goldorak wrote:Hi,
I've been posting on other threads regarding the near term roadmap. Once headless rendering is completed (which is being worked on now, and will be fully supported on or before 3.1), we'll have a stable framework and API for OctaneImager extensions going forward. That is why this feature was set for 3.1. The imager extensions such as ICEFX have been ready for a while, and some of them have even been implemented entirely in Octane OSL node (toon shading for example).