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

Chunked LOD Merging between levels

2 posts in this topic

Hi all

I've implemented the first stage of my Chunked LOD terrain engine, which simply decides on when to split a tile into 4 sub-tiles based on the distance from the camera to the center of the tile, i.e:

[CODE]
void TerrainRenderer::RenderTile(const float& left, const float& right, const float& top, const float& bottom, const XMFLOAT4& colour, int& tilesRendered, int& tilesFrustumCulled)
{
// Calculate the centre of the quad
XMVECTOR centre = XMVectorSet((left + right) / 2.0f, 0.0f, (top + bottom) / 2.0f, 0.0f);
// We'll need the width and height of the cells
float width = right - left;
float height = bottom - top;
// Frustum culling removed for brevity
// Calculate the distance from the camera to the centre of this quad
XMVECTOR diff = Renderer::GetInstance()->GetCameraPosVec() - centre;
float distance = XMVector3Length(diff).m128_f32[0];
// Should we render here or split?
if (distance < (width * 2.0f))
{
// Too close, split into 4 sub-tiles
RenderTile(left, left + (width/2.0f), top, top + (height/2.0f), constColourRed, tilesRendered, tilesFrustumCulled); // Top left
RenderTile(left + (width/2.0f), right, top, top + (height/2.0f), constColourGreen, tilesRendered, tilesFrustumCulled); // Top right
RenderTile(left + (width/2.0f), right, top + (height/2.0f), bottom, constColourBlue, tilesRendered, tilesFrustumCulled); // Bottom right
RenderTile(left, left + (width/2.0f), top + (height/2.0f), bottom, constColourYellow, tilesRendered, tilesFrustumCulled); // Bottom left
}
else
{
// No need to split, render here
// Actual drawing code removed for brevity

tilesRendered++;
}
}
[/CODE]

This works fairly well, but the next step is to get the vertices to warp between levels so that there is no popping when a switch between levels occurs.

The original article by Thatcher Ulrich says:
[quote]At rendering time, we will compute a chunk's morph parameter, ensuring that the morph parameter is always 0 when the chunk is about to split and 1 when the chunk is about to merge.[/quote]

The problem is how do I calculate this?

Its simple to calculate when a tile is going to split, so that's fine. But how does a tile know when its close to merging?

Let me explain using a diagram:

[img]http://www.thesleats.com/ChLODMerge.png[/img]

The Green circle is the eye\camera, the red dots are the center of the tile, the numbers are the distance etc.

On the left image we can see a tile just before it splits. The distance from the eye to the center of the tile is 100.
On the right image the camera has moved one unit closer, which causes the tile to split into 4. The distance from the camera to the center of the bigger original tile (Shown in purple) is now 99, however the distances to the centers of the new smaller tiles are 86, 88, 105 and 108 (These are rough guesses, not actual calculated values).

So this means that the morph factor for each of the children should now be at (Or very close to) 1, but given that they all have different distances to the camera how do I make it so that they all have a value of 1 at this point?

If I were to calculate the morph factors using simple distance to the center of the tile based math then we'd get a pop in the morph value when the tiles split, as just before the split the distance will be 100, and just after we'll have 86, 88, 105 and 108, so there is a jump of -14, -12, 5 and 8 respectively.

Another way of explaining it is that whilst a tile knows how close it is to splitting, it doesn't know when it will merge (Only the parent tile knows that). Does this mean we have to pass this info down from the parent tile to its children?

It was a bit difficult to explain the problem so I hope it made sense?

Any help would be appreciated.

Thanks
Ben
0

Share this post


Link to post
Share on other sites
I think you are on correct path...
The morph parameter for split should be calculated using tile center.
The morph parameter for join should be calculated using parent tile center.
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