That makes sense. I would bet that is what is happening. To answer your
questions:
Yes, if I zoom out the area fills back in. Also, if I rotate the scene,
the objects nearest the POV are clipped.
I am creating a few boxes, and a sphere.
I have version 3.0 (Linux) installed now, but I was having the same
problem with version 2.1.9
Relative to the view, I suppose the scene would be "deep". I am testing
the rigid-body dynamics, so I have a few boxes in the center of the
scene, and a sphere comes from behind the viewer, crashes into the
boxes, then bounces, rolls back towards the viewer, then past the viewer
and keeps rolling far behind the viewer. "scene.autocenter" is set to
zero.
Perhaps the ball is moving too far from the scene, and this somehow
affects the clipping plane?
> Message: 2
> Subject: Re: [Visualpython-users] Rendering problem - memory leak?
> From: Jonathan Brandmeyer <jbr...@ea...>
> To: "Vis...@li..." <Vis...@li...>
> Date: Tue, 03 Aug 2004 17:22:26 -0400
>
> On Tue, 2004-08-03 at 17:02, Isaac W Hanson wrote:
> > I am using vpython with the rigid-body simulation package pyode. After
> > the simulation runs for about a minute, I begin to notice the objects
> > rendered in the gtkgl window begin to disappear, starting at the camera
> > position and progressing along the Z axis. It's as if the program has
> > run out of memory and is beginning to overwrite the memory allocated to
> > the gtkgl image. Rather than leaving a "black space" in the image, the
> > problem seems to create a "transparent hole" in the rendering (like a
> > cut-away view).
>
> It sounds like the near clipping plane is moving forward into the scene
> (it shouldn't do that).
>
> If you zoom out, does the area appear to fill back in again?
> Which VPython objects are being created by your program?
> Which version of VPython do you have installed?
> What is the overall shape of the scene that is created? Is it wide,
> tall, or deep relative to the view?
>
> > I am not sure this is a problem with vpython itself,
>
> It probably is.
>
> > because the problem
> > only progresses as I continually update the position and orientation of
> > the visual objects (in a loop). Once the loop is over, the problem
> > ceases to get worse.
> >
> > Has anybody experienced a similar problem? Any words of wisdom?
>
> -Jonathan
|
