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


  • Content count

  • Joined

  • Last visited

Community Reputation

126 Neutral

About JBurnside

  • Rank
  1. You can certainly do whatever math you want in a pixel shader, but you can't change what pixel is being defined at that point in the pipeline. The math I posted for the vertex shader would work in a pixel shader if you have the right data, but the pixel being processed has already been defined.
  2. If I understand you correctly, you are in a vertex shader that likely has a world space position as input and you are trying to output the appropriate position. To do this you will need to do something like the following: float4 someVertexShaderFunc(float3 worldPos) : SV_POSITION { [indent=1]float4 outPos = mul(float4(worldPos, 1), m_WVP);[/indent] [indent=1]...[/indent] [indent=1]return outPos;[/indent] }
  3. [color=#4A4A4A][background=rgb(241, 241, 241)]Hello,[/background][/color] [color=#4A4A4A] I have been converting a rendering system from using DX9 to DX11. At this point, everything I am currently testing is visually working. Unfortunately I am getting a DX API warning, "D3D11: WARNING: ID3D11DeviceContext::DrawIndexed: Index buffer has not enough space! [ EXECUTION WARNING #359: DEVICE_DRAW_INDEX_BUFFER_TOO_SMALL ]"[/color] [color=#4A4A4A] I have found that getting this warning depends on the meshes I am loading, and what order they are loaded in. If I load meshes, A, B, C in that order I get the issue when I render B or C. Mesh A appears to be the cause as anything loaded after it will cause a call to DrawIndexed to give that warning. From the warning I would think I am somehow requesting to draw using more indices than our present, but this does not appear to be the case. All three meshes use the same index and vertex buffers. If I load mesh A's vertices but not indices the issue remains, but if I load mesh A's indices but not vertices the issue goes away.[/color] [color=#4A4A4A] I am setting the vertex and index buffers to be used for rendering per shader, then per object calling DrawIndexed using a start vertex and start index. Here are some snippets of the rendering code:[/color] [color=#4A4A4A] Per shader - [/color][color=#4A4A4A] ...[/color][color=#4A4A4A] [indent=1]UINT stride = sizeof(VERTEX_POSNORMTANTEX);[/indent] [indent=1]UINT offset = 0;[/indent] [indent=1]ID3D11Buffer *const vertexBufferPtr = [/indent] [indent=1]VertexBufferManager::GetReference().GetPosNormTanTexBuffer().GetVertexBuffer();[/indent] [indent=1]Renderer::theContextPtr->IASetVertexBuffers(0, 1, &vertexBufferPtr, &stride, &offset);[/indent][/color][color=#4A4A4A] Renderer::theContextPtr->IASetIndexBuffer(IndexBuffer::GetReference().GetIndices(), DXGI_FORMAT_R32_UINT, 0);[/color][color=#4A4A4A] ...[/color][color=#4A4A4A] Per Object - [/color][color=#4A4A4A] // Assuming we are using triangle lists for now[/color][color=#4A4A4A] Renderer::theContextPtr->DrawIndexed(mesh.GetPrimitiveCount() * 3, mesh.GetStartIndex(), mesh.GetStartVertex());[/color] [color=#4A4A4A] I have found a work around but it does not seem like a good way to do things as it requires setting the index buffer per object. The following code will get rid of the issue:[/color] [color=#4A4A4A] Per Object -[/color][color=#4A4A4A] ... [/color][color=#4A4A4A] Renderer::theContextPtr->IASetIndexBuffer(IndexBuffer::GetReference().GetIndices(), DXGI_FORMAT_R32_UINT, mesh.GetStartIndex() * 4);[/color][color=#4A4A4A] ...[/color][color=#4A4A4A] // Assuming we are using triangle lists for now[/color][color=#4A4A4A] Renderer::theContextPtr->DrawIndexed(mesh.GetPrimitiveCount() * 3, 0, mesh.GetStartVertex());[/color][color=#4A4A4A] ...[/color] [color=#4A4A4A] Mesh A is some test geometry that I have been using for years with OGL, DX9 and now DX11 projects, so I feel it is unlikely, but not impossible, that there is something wrong with the data. I can recreate the issue with some other meshes that worked with the DX9 version as well. All my vertices and indices are copied into vector containers until I am down loading then I create the index and vertex buffers based on this data.[/color] [color=#4A4A4A] I have discovered that I can hard code the "mesh.GetPrimitiveCount()" to return 0, so nothing is drawn and I still get the warning.[/color] [color=#4A4A4A] Here are the snippets of how I create my index buffer: For each load - UINT IndexBuffer::AddIndices(UINT startVert, const UINT *_indices, UINT _numIndices) { [indent=1]// Test if this buffer has already been finalized[/indent] [indent=1]assert(!indexBufferPtr);[/indent] [indent=1]size_t ret = indices.size();[/indent] [indent=1] // Implement a solution for the Renderer Lab[/indent] [indent=1]for(size_t i = 0; i < _numIndices; ++i)[/indent] [indent=1]indices.push_back(_indices[i]);// + startVert);[/indent] [indent=1]return (UINT)ret;[/indent] } The return is the StartIndexLocation for this particular mesh. When I am done loading assets - void IndexBuffer::Finalize() { [indent=1]D3D11_BUFFER_DESC ibd;[/indent] [indent=1]ibd.Usage = D3D11_USAGE_IMMUTABLE;[/indent] [indent=1]ibd.ByteWidth = sizeof(UINT) * (UINT)indices.size();[/indent] [indent=1]ibd.BindFlags = D3D11_BIND_INDEX_BUFFER;[/indent] [indent=1]ibd.CPUAccessFlags = 0;[/indent] [indent=1]ibd.MiscFlags = 0;[/indent] [indent=1]ibd.StructureByteStride = 0;[/indent] [indent=1]D3D11_SUBRESOURCE_DATA iinitData;[/indent] [indent=1]iinitData.pSysMem = &indices[0];[/indent] [indent=1]HR(Renderer::theDevicePtr->CreateBuffer(&ibd, &iinitData, &indexBufferPtr));[/indent] [indent=1]// Do not need to keep a local copy of indices[/indent] [indent=1]testSize = indices.size();[/indent] [indent=1]indices.clear();[/indent] } I have a vertex buffer class that works the same way except for being a template to handle different input layouts. An instance of the vertex buffer class is made for each unique vertex layout. In my example mesh A, B and C all use the same vertex buffer.[/color]