Frame not cleared when all geometries suddenly culled
Reported by lindsay.kay (at xeolabs) | October 22nd, 2010 @ 12:40 PM | in V0.7.9
Render a frame with visible geometries, then render a second frame with all geometries culled (ie. out of view frustum) and the image from the previous frame remains because the frame is not cleared. The reason is that the state change for clearing the framebuffer is always bound to a geometry - if there is no geometry then the state persists.
Comments and changes to this ticket
-
lindsay.kay (at xeolabs) October 23rd, 2010 @ 02:09 AM
- Milestone set to V0.7.9
- Tag set to state sorting
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
SceneJS provides easy access to WebGL through a simple and declarative JavaScript API. The SceneJS API is functional, which enables its scene definitions to be really compact and expressive, while hooking into other JavaScript code just that little bit more smoothly.