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

DrawIndexed : StartIndexLocation / IASetVertexBuffers : Offset

4 posts in this topic

Hi,

 

My renderer has this issue where I get an DEVICE_DRAW_INDEX_BUFFER_TOO_SMALL warning when using DrawIndexed(Instanced)().

 

I use 16 bit index buffers that refer to max 2^16 vertices chunks in a vertex buffer. Whenever I pass a BaseVertexLocation > 0 to DrawIndexed(), this warning is output. However, if I set StartIndexLocation to zero and instead pass an index buffer offset to IASetIndexBuffer(), the warning disappears. For both cases the rendered scene looks fine.

 

Any ideas what could be causing this?

 

0

Share this post


Link to post
Share on other sites
As far as I know, StartIndexLocation and Index Buffer Offset is almost the same thing. The difference is that the offset is in bytes so you have to take the index size (16 bit vs 32 bit) into account. They both accomplish the same thing, ie. defining where to start reading the indices. Both can be used in the same time or just one of them. Typically I define the location of the indices only with the byte offset.

The BaseVertexLocation however is another kind of offset. The MSDN says that "BaseVertexLocation is a value added to each index before reading a vertex from the vertex buffer." So this offset is changing the index which is used to access the vertex buffer.

The error message you get is related to the situation where your drawing call is "out of bounds" ie. trying to read indices outside of the index buffer.

Changing just BaseVertexLocation shouldn't give this error since it doesn't affect the starting point of reading or the amount of reading from the index buffer. However, messing with all the three values (BaseVertexLocation, StartIndexLocation, Index Buffer Offset) are a good source of errors and incorrect output.

You should look into the the program logic again and verify that you are reading the index buffer from desired location with the amount of indices that resides inside the buffer.

Enable Direct3d debugging and enable the break points so that you can halt the program at the point which creates the error.

Cheers! Edited by kauna
2

Share this post


Link to post
Share on other sites

You're right. I was led off course by the fact that using an offset in IASetIndexBuffer() doesn't generate an error, making me think it was something API related. It turns out there was a bug in my offset calculations.

 

I prefer to pass the offsets to DrawIndexed() as it involves less state changes when using the same index buffer.

1

Share this post


Link to post
Share on other sites

[quote name='eppo' timestamp='1357130387' post='5016666']
I prefer to pass the offsets to DrawIndexed() as it involves less state changes when using the same index buffer.
[/quote]

 

Putting it that way, I guess you are right. 

 

Cheers!

0

Share this post


Link to post
Share on other sites

Update: my offsets were correct after all.

 

There is a known bug in the D3D11 debug layer that generates the "Index buffer has not enough space!" warning when both the StartIndexLocation and BaseVertexLocation arguments to DrawIndexed() are non-zero.

1

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