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

context->UpdateSubresource(constant buffer) - how does it work?

4 posts in this topic

I'm new to Direct3D 11, transitioning from DX9.

 

Question: How do context->UpdateSubresource and shaders work together? I.e., how does the context know where in the shader to stuff the subresource?

 

Background:

 

I have several shaders with contant buffers using this #include:

//--------------------------------------------------------------------------------------
// Constant Buffer Variables
//--------------------------------------------------------------------------------------
cbuffer cbNeverChanges : register(b0)
{
    float4 lightDir;
};

cbuffer cbChangeOnResize : register(b1)
{
    matrix Projection;
};

cbuffer cbChangesEveryFrame : register(b2)
{
    matrix View;
    matrix World;
    float4 vMeshColor;
};

I created 3 buffers, all from the same D3D11_BUFFER_DESC, changing only the ByteWidth, one to match in size each of the buffers in the shader. I update the corresponding buffer on resize, and per frame, as necessary. For example, when the window is resized, I update the context (buffer resize), followed by:

 

    // Re-initialize the projection matrix
    g_Projection = XMMatrixPerspectiveFovLH(XM_PIDIV4, width / (FLOAT)height, 0.01f, 100.0f);

    CBChangeOnResize cbChangesOnResize;
    cbChangesOnResize.mProjection = XMMatrixTranspose(g_Projection);
    g_pImmediateContext->UpdateSubresource(g_pCBChangeOnResize, 0, NULL, &cbChangesOnResize, 0, 0);


Everything works. So I'm curious - when a shader is set, how do the appropriate buffers in the GPU get set from those context subresources?

 

Other than the size of the structure (e.g., CBChangeOnResize above), there appears to be no information for the context to map a particular subresource to a particular buffer in the GPU. How does it work?

 

 

0

Share this post


Link to post
Share on other sites

UpdateSubresource is for updating the contents of a buffer, not for binding it. What you're looking for is ID3D11DeviceContext::PSSetConstantBuffers and the VS/GS/HS/DS equivalents. Are you using something that hides that part (Effects11)?

Edited by Mona2000
2

Share this post


Link to post
Share on other sites

What you're looking for is ID3D11DeviceContext::PSSetConstantBuffers

Ah! Indeed, that explains it well. Thanks!

 


Are you using something that hides that part (Effects11)?

Hah, no, just didn't think to look at the rendering routine I wrote. blink.png It's there, bigger than life. Hey, "you can't fix stupid."

        g_pImmediateContext->VSSetConstantBuffers(0, 1, &g_pCBNeverChanges);
        g_pImmediateContext->VSSetConstantBuffers(1, 1, &g_pCBChangeOnResize);
        g_pImmediateContext->VSSetConstantBuffers(2, 1, &g_pCBChangesEveryFrame);
Edited by Buckeye
0

Share this post


Link to post
Share on other sites

Thanks, SeanMiddleditch! Changed my code and that works fine. I "stole" the original (separate calls) from sample code. Those calls are made for each set of shaders in the render loop, so it'll save a few cycles.

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