• 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
Tim Coolman

Use Multiple Render Targets for Differing Primitive Projections?

5 posts in this topic

I have a point list of vertices(D3D11_PRIMITIVE_TOPOLOGY_POINTLIST) that I wish to render to two render targets. I was hoping I'd be able to set both render targets simultaneously using OMSetRenderTargets. However, my situation is unique in that I want each point (Vertex) to be projected differently onto the two render targets.

If I'm understanding the use of multiple render targets correctly, you can only specify different output COLORS for each render target from the Pixel Shader using the SV_Target semantic - using an index suffix to specify the render target (SV_Target0, SV_Target1). But by this stage in the pipeline, the projection position of the pixel has already been determined.

It appears that the SV_Position semantic doesn't give you the same option to specify multiple projection positions for a vertex from the Vertex Shader. Is that correct?

Can anyone think of another way I could do pull this off? Or will I need to perform two separate draw calls on this set of vertices?

Thanks in advance for any help and suggestions.

Tim
0

Share this post


Link to post
Share on other sites
You can do this with a geometry shader and render target array index. Check out for example the CubeMapGS sample in the Direct3D 10 samples in the DX SDK.
0

Share this post


Link to post
Share on other sites
[quote name='Erik Rufelt' timestamp='1352155985' post='4997774']
You can do this with a geometry shader and render target array index. Check out for example the CubeMapGS sample in the Direct3D 10 samples in the DX SDK.
[/quote]

Thanks for the suggestion. I looked this over, but it will not work for me as my render targets are not an array type (and can't be as they are different dimensions). Any other ideas?
0

Share this post


Link to post
Share on other sites
You might be out of luck then, unfortunately.
From [url="http://msdn.microsoft.com/en-us/library/windows/desktop/ff476464%28v=vs.85%29.aspx"]http://msdn.microsoft.com/en-us/library/windows/desktop/ff476464%28v=vs.85%29.aspx[/url]:
[quote]
The pixel shader must be able to simultaneously render to at least eight separate render targets. All of these render targets must access the same type of resource: Buffer, Texture1D, Texture1DArray, Texture2D, Texture2DArray, Texture3D, or TextureCube. All render targets must have the same size in all dimensions (width and height, and depth for 3D or array size for *Array types). If render targets use multisample anti-aliasing, all bound render targets and depth buffer must be the same form of multisample resource (that is, the sample counts must be the same). Each render target can have a different data format. These render target formats are not required to have identical bit-per-element counts.
[/quote]
0

Share this post


Link to post
Share on other sites
[quote name='Erik Rufelt' timestamp='1352222002' post='4998102']
You might be out of luck then, unfortunately.
[/quote]

No problem. I can do it in two separate draw calls, I was just wondering if I could improve efficiency since the input data is exactly the same. Thanks for the info!
0

Share this post


Link to post
Share on other sites
If your drawing code is as efficient as it can be, not using Geometry Shader won't slow down a much. GS may help you to reduce the draw calls, but the overall efficiency gain may be close to 0.

Cheers!
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