[Vis5d-users] Re: Bug in "vis5d_verylarge_mode" ?

Below is an excerpt from a very-large-mode animation script for 4.3 where
vis5d_set_timestep and vis5d_make_timestep_graphics are used to accomplish
what I think it is you're having trouble with.

don

proc next_frame {ctx time doit} {
        global doSave doStereo baseName frame extName format totalFrames
dirName

        vis5d_set_timestep $ctx $time

# Don't create or render the bulk of the geometry in test mode

        rendermode $ctx $doit
        if {$doit} {
                vis5d_make_timestep_graphics $ctx $time
        }

Subject: Bug in "vis5d_verylarge_mode" ?


>   Hi
>
>   Im using the vis5D API to draw isosurfaces and colored isosurfaces, when
>  I use the API vis5d_set_isosurface_color_var_and_owner, Vis5D draws all
>  the frames, instead of drawing only the n-th frame.
>
>   To solve this problem I use the API "vis5d_verylarge_mode 0 VIS5D_ON"
and
>  it works fine, because when I call
vis5d_set_isosurface_color_var_and_owner
>  it only draws the desired frame; the problem is when I want to draw  the
>  next frame ((n+1)-th frame), it does nothing...
>  (Vis5D thinks the values are in memory ?)
>
>   I also tried the API vis5d_destroy_data_context
>   and vis5d_destroy_display_context but without sucess.
>
>   Does anybody have the same problem? Is this a bug, or Im using it in the
>   wrong way?
>
>
>   Thank you very much for your attention
>
>   Jose Melo
>
>
> >
>
>