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

Best way to create bounding boxes

6 posts in this topic

I have a CubeChunk class which creates indices and vertices for each "Cube" in my chunk. What I want to do is create a bounding box for each of these cubes, so what I'm wondering is what is the best way to do this? Should I create a separate list for each chunk and store the bounding boxes in that? Or should I call a CreateBoundingBox method each time the cube is created or drawn?

For Example 

for (int x = 0; x < 50; x++)
            {
                for (int z = 0; z < 50; z++)
                {
                    for (int y = 0; y <= map[x, z]; y++)
                    {

                        if (y >= 1)
                        {
                            SetUpIndicesAndVertices(x, map[x, z] - y, z, vertices, indices);
                            cubes.Add(new Cube.Stone(device, new Vector3(x, map[x, z] - y, z), stone));
                              CreateBoundingBox(some kind of vector3 values here);
                        }

                        else
                        {
                            SetUpIndicesAndVertices(x, map[x, z] - y, z, vertices, indices);
                            cubes.Add(new Cube.Grass(device, new Vector3(x, map[x, z] - y, z), grass));
                              CreateBoundingBox(some kind of vector3 values here);
                        }
                    }
                }

Or I could replace the line with cubeBB.Add(new BoundingBox(some vector3 crap here). Which one would make more sense to use? 

0

Share this post


Link to post
Share on other sites

Just curious why you need a separate bounding box for each cube? Wouldn't each cube already be its own bounding box?

0

Share this post


Link to post
Share on other sites

To test collision between mouse and cube, or player and cube. I didn't know I could just use the cube as its own bounding box though. How would I do that?

0

Share this post


Link to post
Share on other sites

If I understand correctly, you want to take your "Cube", which is your own custom box, and make an official XNA BoundingBox out of it. I think you should make a Cube Intersect method, and locally construct the BoundingBox inside of that method for the intersection test. It's better than having it hang around in memory. A local struct shouldn't cost much to create.

0

Share this post


Link to post
Share on other sites

So what you're saying is to create the BoundingBox of the cube at the point of intersection with the mouse or player? I guess that could work. It would save a lot of unnecessary bounding boxes in the memory. Although I didn't think c# had an issue with things hanging around in memory but who knows :P

0

Share this post


Link to post
Share on other sites

So what you're saying is to create the BoundingBox of the cube at the point of intersection with the mouse or player? I guess that could work. It would save a lot of unnecessary bounding boxes in the memory. Although I didn't think c# had an issue with things hanging around in memory but who knows tongue.png

 

An optimization over this would be instead of creating a new cube to test collision, set aside a number of already created bounding boxes in a circular queue and reuse. Update the appropriate fields and properties of the BB to match the cube and send to the collision tester. This will save you many allocations per collision frame. If you plan to target a mobile device this will help to reduce garbage collections which could affect your framerate.

0

Share this post


Link to post
Share on other sites

What I was thinking is that I could have something like this:

 

x, x, x, x, x,

x, x, x, x, x,

x, x, o, x, x,

x, x, x, x, x,

x, x, x, x, x,

 

Where the x's are equal to 2 cubes and 0 is the player. The 5x5 space would be like a bounding box for the player which moves with the player and allows the player to only mine or build within that 5x5 box. I would definitely decrease the amount of bounding boxes needed, but I wouldn't even know how to start coding it.

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