Le mardi 6 novembre 2018 09:57:50 UTC-5, Neil Roche a écrit : > I would guess that the curveFromSurfaceIso node will work like a parametric > curve irrespective of whether parametric is set on or off as you have the min > and max U values at 0 and 1 and it has no concept of where to draw any cvs > inbetween. Once you have created the curve by connecting the outputCurve to > the curve.create attribute you now have a curve with 4 cvs so with parametric > off it will function as expected and the locator will move as the cvs are > stretched apart from each other, differently to the motion path with the > curveFromSurfaceIso input. That's my guess anyway. > > > > On Monday, 5 November 2018 18:35:09 UTC, vince touache wrote:Le lundi 5 > novembre 2018 13:28:25 UTC-5, Neil Roche a écrit : > > > Hi, > > > > > > > > > Because of a weird bug in Maya when you set parametric length on a motion > > path you need to set the opposite; > > > > > > > > > cmds.setAttr(mp + '.fractionMode', True) > > > > > > > > > actually turns parametric off. > > > > > > > > > So you need to do > > > > > > > > > cmds.setAttr(mp + '.fractionMode', not True) or cmds.setAttr(mp + > > '.fractionMode', False) > > > > > > > > > > > > To get your code snippet to work. > > > > > > > > > Cheers, > > > > > > > > > Neil > > > > Hi Neil, > > thanks for the answer. Indeed, as you flagged, parametric attribute is the > 'GUI' name, and fractionMode is the core name, parametric==not fractionMode. > > In my example, I explicitely set the fractionMode to True, on purpose, > because this is the behavior I need (i.e. not parametric). > > But my thoughts are more about "what happens in a nurbsCurve node, to change > the output of my curveIso ?" > > > > In other words, I would expect to have the same result in > curveFromSurfaceIso.outputSurface and in nurbsCurve.worldSpace. I don't. > > Any idea of what the nurbsCurve is implicitely doing to my > curveFromSurfaceIso.outputSurface ?
Interesting. that's the best guess I came up with so far too ! A bit like some datas not being computed, maybe for optimisation purpose, unless they are explicitely required, which happens when we plug the nurbsCurve. off topic, this situation reminds me a bit of Young's interference experiment (https://en.wikipedia.org/wiki/Young%27s_interference_experiment) where the signal is both a wave and a particle until we force it to choose one ^^ here, the data is can be different things, depending on what we plug after ^^ -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/0eff12d7-c4a6-4ffc-ba8d-0dceaadca56f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
