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

Passing vertex information to compute shader

2 posts in this topic

Hi all

I am currently attempting to create a ray tracer using the GPU with the intention of extending it to a path tracer once I get a basic ray tracer working for a project of mine.


As both algorithms require performing intersection tests against all known geometry in the scene, this means that I will need a single buffer containing the triangle/vertex information for every piece of geometry in a given scene as I expect repeated render calls for individual pieces of geometry will be very slow. This is fine for scenes with a low amount of triangles but my intention is to render fairly complex scenes later, which could potentially contain thousands of triangles so this is my first concern: Is there a set limit to the amount of data I can pass in a single buffer to the GPU or is it solely limited to the amount of RAM available on the GPU?


My second question is how do I actually go about passing the data to the compute shader? I have only ever used vertex/pixel shaders before which obviously make use of the standard rasterization pipeline : IE the input assembler and buffers containing the vertices (and indices) with the D3D11_BIND_VERTEX_BUFFER (and D3D11_BIND_INDEX_BUFFER) flags. As the application will only use the compute shader and a different method of drawing graphics, I'm not sure if I can use these specific buffers or if I should be using a structured buffer instead with a struct matching the vertex information, as I've heard that there are conflicts with specifying a buffer with both the D3D11_BIND_VERTEX_BUFFER and the D3D11_BIND_UNORDERED_ACCESS flags but I could be mistaken.

Any information or help would be greatly appreciated. Thank you
0

Share this post


Link to post
Share on other sites

I don't think there's a limit, aside from how much memory that the driver can allocate. For reading a buffer in a compute shader you're probably going to want to use a structured buffer. Unfortunately D3D11 has a silly restriction that you can't create a buffer with both D3D11_BIND_VERTEX_BUFFER and D3D11_BIND_SHADER_RESOURCE, so if you want to read from a buffer in a shader then it can't be a vertex buffer. However if you create the buffer as a structured buffer and you need to rasterize it with the graphics pipeline, you can always just directly read from the buffer a shader resource view in your vertex shader using SV_VertexID.

2

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