direct3D render to surface

i am new to this

do i see it right
if i have a 3d cube (6 sides) and want to have some 3d object on the sides
i would need 7 render targets ?!

one rendering the cube it self
and for each side an other one

or do i render 1 side after the other in to the same render target
storing the results in some bitmap and then rendering the cube and texturing
it

how heavy (gpu wice) would by to render something like
a cube on each side a cube on each side a cube
so this would by 216 renderings
the scenes it self wouldnt by to complex max 500 vertices
but more 50-100 each
or do i render 1 side after the other in to the same render target
storing the results in some bitmap and then rendering the cube and texturing
it


This.

If each side of the cube is showing the same image, than you'd only need to render twice.

- Once to render the 3d image onto a texture
- Again to use that texture when you render the cube onto the display.

how heavy (gpu wice) would by to render something like
a cube on each side a cube on each side a cube
so this would by 216 renderings


That's kind of a difficult question to answer because it's kind of arbitrary.

Assuming your display is the same res as the texture you're rendering to (ie, you are rendering cubes to a 100x100 texture... then using that texture to render cubes on another 100x100 texture... then using that to render on a 100x100 display).

You basically add 1x of rendering time to each step.

So if rendering a cube takes ~1 ms.
Rendering a cube texture, then a cube display would take ~2 ms
Rendering a cube texture, then another cube texture, then a cube display would take ~3 ms.


But this is highly speculative and subjective. The hardware you're using might be more (or less) efficient at rendering to textures than it is to rendering to the display.
thx
Topic archived. No new replies allowed.