algorithmic modeling for Rhino
I am having some issues with the IsoCurve node. I have an older file that takes a point as an input (using x,y, as u,v with z as 0) and returns both the U & V iso curves. In a new file under 0.8.0066, the old node is still there (labeled as old) and works just fine, but when I add a new IsoCurve node and feed it a point (the same point) it fails to return the V iso curve (U iso curve is ok). I've double checked the domain and the point contains valid UV coordinates... Is this just a bug with the newer IsoCurve node?
In a related matter, how were isoCurve Nodes designed in regards to input points? Is feeding them a 3d point is the correct way to use them? I couldn't find a way to create a simple 2 pair coordinate...
Thanks,
tom
Tags:
Tom, I'm having the exact same problem. Also Isotrim makes the same mistake: it seems it will multiply the total V-length with the value you provide...
Suppose it's a bug. It's reported now.
Sorry I can't be of more help...
Pim.
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by