• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
beebs1

XNA Render Targets

5 posts in this topic

Hiya

I've just switched to XNA, and I had a couple of questions I was hoping someone can help with :)

Could anyone explain the relationship between eDRAM and render targets on the Xbox 360? Each render target must have some VRAM assigned for the texture data. When you bind a render target with DiscardContents, this texture isn't copied into eDRAM (since this would be slow?) but the texture data is cleared to purple to show this. I guess PreserveContents would cause the texture to be copied, although this would probably be very slow.

Is this correct? At what point is the render target in eDRAM copied back to the texture store in VRAM?

Also, could anyone tell me how depth/stencil buffers are handled on the 360? If I create a render target with a depth buffer attached, where does the buffer live? Does it have a backing store in VRAM?

Thanks for any help!

Cheers
Jim Edited by Telios
0

Share this post


Link to post
Share on other sites

The render target data in EDRAM is copied back to regular memory when you resolve the render target. That is, when you switch to another render target or back to the back buffer.

 

The depth/stencil buffer lives in EDRAM with the render target*, so this takes up part of your 10MB limit (4 bytes per pixel). It never gets copied back to regular memory.

 

*I believe there is also HiZ/HiStencil that has a small but of special memory on the GPU, separate from EDRAM.

1

Share this post


Link to post
Share on other sites

Thanks for the quick reply!

 

Just to clarify - are depth/stencil buffers shared in any way in EDRAM? For example, if I create a second render target with a depth/stencil attached, is this depth buffer a separate area of memory or is it shared with the backbuffer's depth?

 

I'm trying to avoid tiling so it would be useful to know how much EDRAM I'm using.

 

Thanks again.

0

Share this post


Link to post
Share on other sites

You have to remember that a 360 uses tiled rendering as a full 720p target(1280*720*24 = 21MiB) will not fit in 10MiB EDRAM so it will always tile.

-1

Share this post


Link to post
Share on other sites

The backbuffer can be thought of as just another render target. In that, I mean that it doesn't take up any space in EDRAM if you've currently set another render target to be active. EDRAM is just used for the render target that is currently active. So all you need to do to determine if tiling is triggered is to calculate how much memory your render target + depth buffer requires.

 

So, for a 1280x720 Color render target with a depth/stencil buffer, you have: (1280*720 * 4) + (1280 * 720 * 4) = 7372800 bytes = 7.03MB. So that fits comfortably in EDRAM (NightCreature83's calculation is incorrect - a Color render target is 4 bytes per pixel, not 24).  If you're using multiple render targets (say for deferred rendering), then 2 of those plus a depth buffer gives you 10.54MB, which means you'll end up tiling.

 

FWIW, I've rarely noticed any performance degradation from tiling. I'm sure it could happen if your performance bottleneck is vertex processing, but I think in most cases it's not a big deal.

 

Note that you can also visually see the tiling if you write a shader that uses the VPOS semantic. VPOS, which gives the current pixel position, "resets" for each tile. So you can write a test shader that can show exactly where the tile boundaries are.

Edited by phil_t
1

Share this post


Link to post
Share on other sites
Exactly what I was looking for, thanks very much! Edited by Telios
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0