comparison org/vision.org @ 274:dbecd276b51a

merged dylan's changes
author Robert McIntyre <rlm@mit.edu>
date Wed, 15 Feb 2012 06:58:26 -0700
parents c39b8b29a79e 12e6231eae8e
children 23aadf376e9d
comparison
equal deleted inserted replaced
273:c39b8b29a79e 274:dbecd276b51a
33 view of the simulated world. You can create as many of these as you 33 view of the simulated world. You can create as many of these as you
34 want. Every frame, the =RenderManager= iterates through each 34 want. Every frame, the =RenderManager= iterates through each
35 =ViewPort=, rendering the scene in the GPU. For each =ViewPort= there 35 =ViewPort=, rendering the scene in the GPU. For each =ViewPort= there
36 is a =FrameBuffer= which represents the rendered image in the GPU. 36 is a =FrameBuffer= which represents the rendered image in the GPU.
37 37
38 #+caption: =ViewPorts= are cameras in the world. During each frame, the =Rendermanager= records a snapshot of what each view is currently seeing. 38 #+caption: =ViewPorts= are cameras in the world. During each frame, the =Rendermanager= records a snapshot of what each view is currently seeing; these snapshots are =Framebuffer= objects.
39 #+ATTR_HTML: width="400" 39 #+ATTR_HTML: width="400"
40 [[../images/diagram_rendermanager.png]] 40 [[../images/diagram_rendermanager2.png]]
41 41
42 Each =ViewPort= can have any number of attached =SceneProcessor= 42 Each =ViewPort= can have any number of attached =SceneProcessor=
43 objects, which are called every time a new frame is rendered. A 43 objects, which are called every time a new frame is rendered. A
44 =SceneProcessor= recieves its =ViewPort's= =FrameBuffer= and can do 44 =SceneProcessor= recieves its =ViewPort's= =FrameBuffer= and can do
45 whatever it wants to the data. Often this consists of invoking GPU 45 whatever it wants to the data. Often this consists of invoking GPU