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

DX11
DX11 - Instancing - The choice of method

6 posts in this topic

Hello guys!

 

As you know, Directx has a feature called 'Instancing', which is quite wonderful actually. But how to use it properly is an entirely different chapter. And that's why I'm here.

 

Imagine Crysis or some other game where high level of vegetation is needed, as grass, and you need to render that. What I would do, and what I actually do:

 

When creating the scene:

 

When Creating the scene:

  • Add all instances of grass
  • Split all instances into different patches
  • Create Instance Buffers

When Rendering the scene:

  • Do some range testing and frustum culling for all patches, and all valid are added to a list.
  • Render each individual element in the list

 

Now that method works fine for me when using static non destroyable or creatable objects, but imagine if one object has to be created? Do I recalculate the respective buffer for the bullets location.

 

Also in the Crysis Sandbox, or CryEngine 3 SDK, when placing/painting vegetation over the terrain, they appear lightning fast! If you have time, how does produceal vegetation work in a nutshell?

 

But what if we are simulating a space ship, IN SPACE! Where the space is almost unlimited, and then the player shoots, I can't have buffers for an unlimited space! (I could create buffers dynamically for where I am, but I'm not sure if that's efficient).

 

So, now, I ask you, what, if it exists, is the most efficient way of handeling instances of an object?

 

Thank You, again...

1

Share this post


Link to post
Share on other sites

Do I recalculate the respective buffer for the bullets location.
 
i don't quite follow, how'd you get from instancing vegetation to drawing bullets? 
 
some cry3 specific thing i assume.
 
generally speaking, you'll have a model in buffers (vertex and index), and transforms for each instance in another buffer.
 
for modifiable vegetation, simply recalculate part or all of the transform buffer when required. you may also be able to do some indexing trick to only draw a range of instances in the transform buffer, and include/exclude vegetation that way.
 
although i'm not that well versed in dx11, i think you could also pass in flags in a constant buffer that could be used to determine which instances to draw.
 
it my also be possible to use some reserved value for a variable in the instance buffer that indicates "don't draw this instance".
 
it also may be possible to pass in some sort of "instance buffer" as well as the "transform buffer". the instance buffer would have a flag for each instance or perhaps work with indexes. not sure how many input buffers of what type you can use in dx11.
 
in the long run, recalculating the transform buffer, passing constant buffers, reserved values, an instance buffer (if supported), and drawing index ranges are all just different ways of telling directx which plants to draw.
 
me personally, i'd probably just recalculate the transform buffer as needed. i do a similar thing in my current title. vegetation is modifiable. terrain is drawn in chunks which are generated as needed from the various data structures that describe whats in the world. Any immobile object created in the world (a hut, landmark, storage pit, temporary shelter, or bedding) means the plants there should not be drawn. so whenever an immobile world object is created or destroyed, its "chunk" gets regenerated to add or remove the plants as needed.
 
when i generate a chunk, i basically do my own instancing to create the ground mesh for each ground texture tile. the "model" is a simple quad. a "pattern map" says which quads in the chunk's ground mesh use a given tile texture. for each quad that uses a given texture, the "model" is transformed to the correct x,z location in the chunk, procedurally height mapped in y, and added to a VB and IB. there's a VB and IB for each ground tile texture in the chunk. when its time to draw, i just set the ground texture and draw the VB for that texture, as the VB is already "pre-instanced" so to speak.
 
i still don't get the part about bullets and buffers though...    
2

Share this post


Link to post
Share on other sites

With the bullets, i mean this:

 

(Just an example)

 

Imagine thousands of spaceships, shooting lasers (or something) all the time, I would imagine that I would instance all bullets, wouldn't I? In that case I don't really see how I would split up each bullet up into a chunk, as they could go anywhere...

 

But Thanks!

1

Share this post


Link to post
Share on other sites

Procedural generation of vegetation typically means that you don't have to know / create all the instances before you need them. That is, when the vegetation block is close enough you can calculate what kind of foliage / vegetation should occupy the area. 

 

That means that you'll need to update your buffers dynamically. You should however split the problem a bit. Instancing and how to handle vegetation are two separate problems. 

 

Instancing just enables you to draw multiple meshes with same / similar parameters in one draw call. How you update / organize your data is a different matter.

 

I'm copying my instance data every frame from main memory to a generic float4 buffer object. Typically this means something like 1-3 megabytes of data per frame depending on the amount of instances and data required by one instance. The data transfer isn't a bottleneck if implemented correctly. This kind of arrangement allows me to cull objects pretty well (foliage and such in bigger blocks) and have exactly one draw call per mesh.

 

Cheers!

Edited by kauna
2

Share this post


Link to post
Share on other sites

note that if your vegetation doesn't change often, you can use static VB's and IB's. if it changes every frame or you recalculate every frame, then you'll want to go dynamic. so you can probably use static for vegetation, and dynamic for bullets. you'll have a VB and IB for your bullet or grass clump. then you'll have an instance buffer of world transforms for each instance you want to draw. the whole idea is to reduce the number of times you bind the instance buffer to a minimum. think of it this way: binding is bad. different binds have different costs: textures are highest (?).  then VB's, then IB's, then constant buffers. apparently the hit for constant buffers isn't that bad. can't recall if binding dynamic vs static buffers is more costly (i think so). all this info is available in the docs.

1

Share this post


Link to post
Share on other sites

With the bullets, i mean this:

 

(Just an example)

 

Imagine thousands of spaceships, shooting lasers (or something) all the time, I would imagine that I would instance all bullets, wouldn't I? In that case I don't really see how I would split up each bullet up into a chunk, as they could go anywhere...

 

But Thanks!

You are dealing with the problem of what objects worth drawing, One solution is keeping a buffer large enough only to draw the bullets near the camera and dynamically insert / remove the elements. You can specify the number of instances inside the buffer.

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

  • Similar Content

    • By lonewolff
      Hi Guys,
      I am just wondering if it is possible to acquire the address of the backbuffer if an API (based on DX11) only exposes the 'device' and 'context' pointers?
      Any advice would be greatly appreciated
    • By MarcusAseth
      bool InitDirect3D::Init() { if (!D3DApp::Init()) { return false; } //Additional Initialization //Disable Alt+Enter Fullscreen Toggle shortkey IDXGIFactory* factory; CreateDXGIFactory(__uuidof(IDXGIFactory), reinterpret_cast<void**>(&factory)); factory->MakeWindowAssociation(mhWindow, DXGI_MWA_NO_WINDOW_CHANGES); factory->Release(); return true; }  
      As stated on the title and displayed on the code above, regardless of it Alt+Enter still takes effect...
      I recall something from the book during the swapChain creation, where in order to create it one has to use the same factory used to create the ID3D11Device, therefore I tested and indeed using that same factory indeed it work.
      How is that one particular factory related to my window and how come the MakeWindowAssociation won't take effect with a newly created factory?
      Also what's even the point of being able to create this Factories if they won't work,?(except from that one associated with the ID3D11Device) 
    • By ProfL
      Can anyone recommend a wrapper for Direct3D 11 that is similarly simple to use as SFML? I don't need all the image formats etc. BUT I want a simple way to open a window, allocate a texture, buffer, shader.
    • By lucky6969b
      Q1:
      Since there is no more fixed pipeline rendering in DX11, for every part of rendering in DX11, do I need to create a brand-new vertex shader and pixel shader... or at least I have to find one relevant online. If you work on skinned meshes and other effects originally worked in DX9 fixed pipeline, do I have to rework everything by now?
       
      Q2:
      For assimp, if it originally was designed for DX9, like it is coupled to a DX9 device for creating meshes and materials etc. Do I have to add in the DX11 device in the assimp, or can I just leave the assimp to remain in DX9 and after the meshes are loaded, I just convert the vertex buffers and index buffers into DX11 buffers?
      Thanks
      Jack
    • By MarcusAseth
      This header is mentioned in the book I'm reading but there is no documentation on msdn... Is it like an... outdated and abandoned header?
      If so, what's the current default/recomended library for handling errors with directX?
  • Popular Now