Menu

#5 Updating mesh after moving points is slow

open
None
1
2006-03-01
2005-12-17
Anonymous
No

If you update one point, the corresponding mesh will be
recalculated several times. Each result is drawn on the
screen, which causes a noticable delay and may stall
the mouse movement. Sometimes a noticable mesh
deformation kicks in several seconds after moving one
point.

Discussion

  • A Mennucc

    A Mennucc - 2006-02-28
    • assigned_to: nobody --> mennucc
     
  • A Mennucc

    A Mennucc - 2006-03-01
    • priority: 5 --> 1
     
  • A Mennucc

    A Mennucc - 2006-03-01

    Logged In: YES
    user_id=79281

    Use a faster PC :-)

    Jokes apart, the mesh smoothing is a slow affair; for this
    reason, it runs as a "idle process" in GTK: on my PC (that
    runs Linux and is rated 1600Mhz) the mouse never stalls;
    (but I noticed that it seems to stall in Windows sometimes).

    The reason why the changes seem to "kick in" is that I DO
    NOT write every change to the screen! I indeed chose to
    refresh seldom... if I refresh often, it becomes even slower.

    If your meshes are not too distorted, you may use a faster
    smoother: in the menus in the main window, set
    "settins/image for mesh smoothing" to "elastic".

    BTW both the smoother and the refresh policy may be
    optimized a lot ...

     

Log in to post a comment.

MongoDB Logo MongoDB