Re: This is what I meant by AE integration

[Christopher]

What does the FX Tree lack compared to AE / Nuke ? Christopher Jason S Sunday, April 07, 2013 8:02 PM Personally I do most of my 2D comps in Nuke, (only mostly because of the rather short bug/feature section of my post) So the previously discussed (if only) points that have been made about not needing Nuke -if only- there would be a *bit* of efforts made on it, were quite valid. But for me when I need to have tranparency mapped grids with comps on them (or on other models in space), I use the FXTree. When I need to PROCEDURALLY TREAT TEXTURES  (all the time) I use the FXTree Fo quick previews and testing I use the FXTree (import passes) When I use SI, I use the FX Tree ( as many more than what magazines may portray ) Historically, many people have always (quietly) used the FXTree. Christopher Sunday, April 07, 2013 7:50 PM Do you use the FXTree Guillaume, actively ? Some on the list grew with FXTree while others do there work in a compositing program.  Whatever rocks your boat, I suppose.  Christopher Guillaume Laforge Sunday, April 07, 2013 7:04 PM > How many people on this list use FXTree for Active work ? Just people using XSI and doing rendering related stuff and knowing the FxTree :). Christopher Sunday, April 07, 2013 6:25 PM Gullaume - There are two meaning to 'dead' Dead as in it's not actively used and Dead as it's removed from the product. Dead as in Walking Dead :) How many people on this list use FXTree for Active work ? Christopher Guillaume Laforge Sunday, April 07, 2013 6:18 PM The FxTree is not dead of course. Every components of XSI can be improved at any time by the Softimage team. Improved by adding feature to the existing code or improved by creating a new version of the component (like when ICE replaced the old particle system). FxTree will be dead the day it will be removed from the product.  Simple as that. Every other statements are just pure speculation. Period :). Guillaume