Grasshopper

algorithmic modeling for Rhino

Hi all,

I would like to know which are the main factors of making a definition slow down. I have been checking the definition with the profiler on but none of them is going above 1ms. I am wondering what else could be the problem.

Thanks in advance

M

Views: 601

Replies to This Discussion

Hi Maialen,

I have met some cases where it seems as if the lag comes from the graphic card's processor. This conclusion might be totally wrong but this is how it "feels" sometimes, with the definition completing calculations fast and then facing lags while zooming or orbiting in the rhino viewport.

In any case I think you can get more a accurate response if you upload the file in question.

Hi Nikos,

Thanks for your reply.

Here is the definition still going slow. If I change the patch for an edge surface it works fine but it doesn't create the right surface when the vertices aren't in the same plane, thats why i need to use the patch.

Thanks in advance,

M

Maialen you didn't upload any files.

Sorry, here is the file!

Thanks

Attachments:

I am sorry but I don't have any considerable lag with the definition. 

are you getting larger times?

edit---

forget this post, I just saw you had already tried this....

sorry for the back and forth in my replies but I must disagree:

edge surface follows the curves exactly, while patch seems to have trouble. Can you test it again?

[EdgeSrf]=green

[Curves]=yellow(-ish)

[Patch]=red

Hi Nikos,

You are right it's not the same using "Edge surface" or Patch.

-PATCH: I connect the curves plus the middle point (which IS NOT calculated with average)

              Besides I have some sayls with more than 4 edges.

-EDGE SURFACE: When the four vertices are in the same plane it should be the same solution as Patch.

I am still getting the patch really slow.

Thanks 

M

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service