Feather is stored relative to the main point position, so 0,0,0 means no
feather.
On Wed, 27 Jan 2016 04:19:39 -0500, Frank Harrison
<fr...@thefoundry.co.uk> wrote:
Works AOK for me on OSX on Nuke 9.0v6 and 8.0v6.
Feather curves which aren't pulled out (they are co-locational with the
main-curve) are treated specially sometimes to improve performance.
On 27 January 2016 at 07:40, Jordan O <jorxs...@gmail.com> wrote:
Hey fellow TDs,
I had a colleague alert me that a script that worked on Nuke 8 has
broken with Nuke 9. (Yes, I realize nuke 10 is about to be released...)
Does this work for you?
a) create a rotopaint node, draw a random closed shape in your viewer,
and extend feathers on all points.
run this code with it selected:
rootLayer = nuke.selectedNode()['curves'].rootLayer
shape = rootLayer[0]
print shape[0].center.getPosition(nuke.frame())
# Result: { 678, 423.6, 0 }
print shape[0].featherCenter.getPosition(nuke.frame())
# Result: { 0,0,0 }
What gives? Is featherCenter broken in Nuke9? Seems like an obvious
bug, maybe I'm missing something.
cheers,
Jordan
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
--Frank Harrison
Senior Nuke Software Engineer
The Foundry
Tel: +44 (0)20 7968 6828 - Fax: +44 (0)20 7930 8906Web:
www.thefoundry.co.uk
Email: frank.harri...@thefoundry.co.uk
--
Using Opera's mail client: http://www.opera.com/mail/
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
