• 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
StanIAm

RWStructuredBuffer read and write ?

4 posts in this topic

Hello I have a little question about the UAVs in directx. I read some explanations about UAVs but there are always 2 types of buffers for input and output in the examples. For my implementation I need a buffer that is only used in the shaders, so I use a pixel or compute shader to write to this buffer and in an other shader I want to read this data from it...so there is no need to manipulate the buffer in my c++ code.

The problem is I saw in the tutorials that there are used 2 types of buffers, the StructuredBuffer as a ShaderResource and a RWStructuredBuffer as a UAV ( for output). My question is : why they use 2 buffers ?? Isn't it possible to create in  my c++ code the UAV -> set it to the pixelshader and that write in my first shader to it and then read it in my second pixel shader ??

 

Something like:

//Create UAV
ID3D11UnorderedAccessView* uav = ....
...
 m_pImmediateContext->PSSetUnorderedAccessViews( 0, 1, &m_destDataGPUBufferView, 
                                                    NULL );

Shader one:

struct VPL {
  float3 pos;
  float3 norm;
  float3 flux;
};

RWStructuredBuffer<VPL> buffer : register( u0 );

...

buffer[0].pos = float3(0.1f,0.5f,0.4f);



Shader two:
RWStructuredBuffer<VPL> buffer : register( u0 );

float3 pos = buffer[0].pos;

0

Share this post


Link to post
Share on other sites

It's a bad name from DirectX, RWStructuredBuffer output and you set a StructuredBuffer to read.

Pixel shader can't bind a UAV, it has not a PSSetUnorderedAccessViews, pixel shader output to a texture.

It's important to notice that a SRV and a UAV must not be binded same time.

Edited by Alundra
0

Share this post


Link to post
Share on other sites

You can certainly read from a RWStructuredBuffer if you want to. In some cases it might make sense to read from one buffer and then write to the same buffer, but in many cases you want to read from one buffer and then write to a different one. This might be because the output structure is different from the input format, or the shader needs to write to a different location than it's reading from. In the latter case you don't want to have one thread writing to an element that a different thread is reading from, since this will lead to race conditions. So the simplest way to handle it is to read from one buffer as a StructuredBuffer, and then write to another as a RWStructuredBuffer.

 

It's a bad name from DirectX, RWStructuredBuffer output and you set a StructuredBuffer to read.

Pixel shader can't bind a UAV, it has not a PSSetUnorderedAccessViews, pixel shader output to a texture.

It's important to notice that a SRV and a UAV must not be binded same time.

 

I'm not sure if you're implying that a RWStructuredBuffer can't be read from, since that's not the case as I explained above. Also you certainly can bind a UAV to a pixel shader, however it's done through ID3D11DeviceContext::OMSetRenderTargetsAndUnorderedAccessViews.

1

Share this post


Link to post
Share on other sites

And as of DX 11.1 (or DX 11.2?) you can also bind UAVs to ALL other shader stages (vertex, hull, ...). When I was looking into this, however, I found a great lack of examples of how to do this exactly. I mean examples of C++ and HLSL showing both SRVs, RTVs and UAVs of all kinds together in a pixel shader. But I guess you'll figure out according to the debug layer error messages :)

1

Share this post


Link to post
Share on other sites
Also you certainly can bind a UAV to a pixel shader, however it's done through ID3D11DeviceContext::OMSetRenderTargetsAndUnorderedAccessViews.

Didn't knew that, thanks for the info.

And as of DX 11.1 (or DX 11.2?) you can also bind UAVs to ALL other shader stages (vertex, hull, ...).

It's good, like that all is on the same way, no need to find another way to do the same thing, nice update.

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