Luis, I thought I just replied to this, but I think it really did get lost in Google space. Nice work (again) if the post shows up twice.
I think I was attacking the gradient issue in the same way you described above, and back in the day I was able get some some reasonable results. You can take a look here if you're interested. If the file is too old and generates errors I can update it if necessary. http://designreform.net/forum/index.php/topic,709.0.html taz On Oct 31, 6:00 am, fraguada <[EMAIL PROTECTED]> wrote: > David, > > Thank you. We are having a lot of fun with this. Trying to get the > tool ready to apply on some upcoming work. > > Gradient control...absolutely! This is an issue I have with > generally, whether in RhinoScript or here...the sorting here is > something I do in Rhinoscript that I have never bothered to fix, but > really should. Right now, it just splits into 5 lists...takes the > highest and lowest value from the data set and makes 5 intervals. But > this is probably not the best way, because, what if the data is not > very accurate and there are some verrrry high values, the distribution > would be very wide. So I need to work in a little standard deviation > to maybe control the interval range and also number of intervals. > We'll see! > > luis > > On Oct 30, 9:39 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > Hi Luis, > > > That's beautiful! It looks like you could go with some gradient > > controls as well :) > > > The next version of Grasshopper will have Nurbs->Mesh tools, which > > includes all meshing settings Rhino offers. I also added a special > > Surface->Mesh component which creates a very simple quad-grid (with > > options for trim behaviour) which can be either uv-aligned or > > 'equalized'. > > > -- > > David Rutten > > Robert McNeel & Associates > > > On Oct 30, 12:31 am, fraguada <[EMAIL PROTECTED]> wrote: > > > > Hello all, > > > > I've posted some samples of mesh vertex coloring. You can find it > > > here:http://www.livearchitecture.net/?p=741 > > > > Included are a few videos of the visualization mesh in action. Still > > > not quite ready for prime time. The data sorting is now split to 5 > > > ranges that adapt according to the subdivision of the surface. This > > > is all sorted and fed back to a master list that feeds it to the > > > mesh. The meshing is not as nice as what Rhino does with the > > > rendermeshes, for example, there is no recursive subdivision of the > > > mesh for higher curvatures, but maybe this is something that can be > > > worked in later. Meshing was very similar to some of the quad and tri > > > panel sorting definitions out there, just in this case instead of > > > sorting points, it is sorting face vertex number info. Colors are set > > > through five color swatches, but it could be set up to do it > > > differently. > > > > This work was in collaboration with CarloMaria Ciampoli and myself.