Bug reports
All  1-3  4-5

Previous
Next
 From:  Michael Gibson
3252.4 In reply to 3252.3 
Hi Tree, thanks for posting the file.

Over here, it seems that disabling apparent intersections actually solves the problem completely. And this is on a 6 year old machine with an old video card...

What degree of performance lag do you still see with it disabled?


It's going to be difficult for me to fix this for v2, I'm probably going to have to add it to my list to look into for v3. It's probably not feasible to really speed up the calculation itself, I'll need to figure out something else, like maybe not doing an apparent intersection on a curve that ends up doubling over itself so many times like this, or possibly doing it on a separate thread.

For now there are a variety of workarounds though - hide the helix, turn off apparent intersections, or disable snaps temporarily while working just in that area where the helix is at... You can also hold down Alt to temporarily disable snaps instead of using the toggle button in the UI.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
 From:  Tree (TREELOY)
3252.5 In reply to 3252.4 
Thanks Michael,

Yeah, I just put it in a different layer and hide it when I need to change something. Maybe the performance hit has something to do with the virtual machine (VMWare Fusion) running on my mac. I'll have to do further testing sometime later.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged
 

Reply to All Reply to All

 

 
 
Show messages: All  1-3  4-5