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

data structure needed for frustum culling

6 posts in this topic

As my game is growing with hundreds of objects, performance issues are growing up. I'm doing 200 frustum intersection tests against object every frame. I thought a data structure would be good to reduce frustum tests.

 

I know about quadtree and octree and how they work. But, I just don't know how to implement it. Can anyone help me?

 

I'm doing terrain culling in hull shader (GPU based patch culling.)

10245285_860125380680484_1305655902_n.jp

Edited by newtechnology
0

Share this post


Link to post
Share on other sites

Well, but my idea is to subdivide terrain into octree (not for terrain culling) and then some how add objects list which lie in a specific node then do AABB-frustum test down tree to see if the object was visible. Any idea how to do this? or any other method (I don't understand the SIMD method properly)

Edited by newtechnology
0

Share this post


Link to post
Share on other sites
Hi. SIMD is a way of doing calculations, it's not a method for culling.
- you can optimize the obb or aabb cull function using SIMD
- besides this you could initially subdivide you world into sectors (big AABB's)'
then when you start culling objects, you check in which segment/AABB the camera is
- now you can just check the big AABB's which the camera is not in, and only cull objects in the sector if it's inside or intersecting the frustum
1

Share this post


Link to post
Share on other sites

Hi. SIMD is a way of doing calculations, it's not a method for culling.
- you can optimize the obb or aabb cull function using SIMD
- besides this you could initially subdivide you world into sectors (big AABB's)'
then when you start culling objects, you check in which segment/AABB the camera is
- now you can just check the big AABB's which the camera is not in, and only cull objects in the sector if it's inside or intersecting the frustum

I know that but I just don't know how to implement it.

 

EDIT: thanks for the sector idea, i'll try to implement it.

Edited by newtechnology
0

Share this post


Link to post
Share on other sites

Hey, my idea is as follows:

 

1. Divide world into 8 big sectors (AABB)
2. Load all objects on map
3. Check Intersection between object-AABB and all sectors-AABB (only once for static objects.)
4. Find out which world sector intersects object
5. Save that world sector into object's model structure 
6. Check intersection between all sectors and camera frustum (every frame)
7. save results into memory (which sectors are visible)
8. for all models, if its sector is visible, then move down to see if
object was visible (else skip because sector is not visible then its model is not visible, note: this time we are using the saved result
in memory i.e we are not doing intersection, it has been done already in step 6.)
9. If visible then draw else skip.
10. Goto step 6 (for next frame)
 
But I dunno how to implement it, yet I'll try. Anyone seeing a problem in this method? (I know a problem arises when objects are in between sectors, but in that case we would assume it has 2 sectors as its parent.)
 
(Just for understanding.)
IHXjiYK.png
 
 
(Also, sorry for bad painting skills.)
Edited by newtechnology
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