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

Chunked LOD and Dual Contouring Help.

2 posts in this topic

Hello!

 

So in my work right now, I've been working on destructible voxel terrain. I've gotten it down to a minecraft-like model, where there are chunks of fixed size and the viewing of the world is optimized (render near-to-far, etc). I have used 3D noise, created complex terrain, and have a firm grasp on procedurally creating terrain with noise. However, I want to take the next step now, and move on to using deal contouring and a chunked LOD system.

 

So my issues lie here: How would I go about this? Let me first say that I understand generally how these algorithms work. I know that dual contouring checks the edges of grid cells that change from in to out of the surface, and I know that chunked LOD takes into account how far away a chunk is from the viewer's chunk. I've also seen source code but...I think I'm just having trouble taking the step between general knowledge and full understanding down to implementation. 

 

My main guiding questions are this: How do you know when to change level of detail? Does this LOD change in every (or most near chunks) chunk as you move? If so, how does this happen in real time?

 

My end goal is having destructible terrain with viewing distances much like real-life. I know this is possible, as I have seen at least a couple implementations, but I still can't bridge the gap. Any help??

Thanks,

ST

1

Share this post


Link to post
Share on other sites

Just to feed this topic a bit.

 

When you say destructible terrain, what do you mean? (Explosions n. stuff?)

 

About the LOD:

  • Find Dinstance btw. Camera and Chunk (center) (This is incredible fast)
  • If Distance >= 50, use lod #3
  • If Distance < 50 , Distance > 25, use lod #2
  • If Distance <= 25, use lod #1

And when changing Lods, simply set a flag to use another buffer.

 

You can develop this model much further, but this is basically just to give you a start point.

 

Good Luck!

 

-MIGI0027

1

Share this post


Link to post
Share on other sites


Just to feed this topic a bit.
 
When you say destructible terrain, what do you mean? (Explosions n. stuff?)

 

So by destructible terrain, I mean like minecraft -- you can blow it up, model your own stuff, gun-shots can damage (depending on how small a voxel can get for me) and so on.

 


About the LOD:
Find Dinstance btw. Camera and Chunk (center) (This is incredible fast)
If Distance >= 50, use lod #3
If Distance < 50 , Distance > 25, use lod #2
If Distance <= 25, use lod #1
And when changing Lods, simply set a flag to use another buffer.
 
You can develop this model much further, but this is basically just to give you a start point.

 

Thank You! By different buffers, are you saying I should keep in memory different buffers for different LOD Meshes? Won't that take up a lot of memory, especially when I also need to keep all voxel data that is close to the viewer in memory as well? (basically all voxel data that has the potential for an update from the user's actions within a certain distance must be held in RAM for easy access and fast mesh updates).

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