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

GPU normal vector generation for high precision planetary terrain

4 posts in this topic

I generate procedural planets pretty much entirely using compute shaders. (CPU manages a modified quad tree for LOD calculations)
The compute shader outputs vertex data on a per terrain patch basis, which is stored in buffers.
Normal vectors are calculated during this stage by using a sobel operator on the generated position data:

[source lang="cpp"]// Only operate on non-padded threads
if((GroupThreadID.x > 0) && (GroupThreadID.x < PaddedX - 1) && (GroupThreadID.y > 0) && (GroupThreadID.y < PaddedY - 1))
{
// Generate normal vectors
float3 C = VertexPosition;
float3 T = GetSharedPosition(GroupThreadID.x, GroupThreadID.y + 1);
float3 TR = GetSharedPosition(GroupThreadID.x + 1, GroupThreadID.y + 1);
float3 R = GetSharedPosition(GroupThreadID.x + 1, GroupThreadID.y);
float3 BR = GetSharedPosition(GroupThreadID.x + 1, GroupThreadID.y - 1);
float3 B = GetSharedPosition(GroupThreadID.x, GroupThreadID.y - 1);
float3 BL = GetSharedPosition(GroupThreadID.x - 1, GroupThreadID.y - 1);
float3 L = GetSharedPosition(GroupThreadID.x - 1, GroupThreadID.y);
float3 TL = GetSharedPosition(GroupThreadID.x - 1, GroupThreadID.y + 1);

float3 v1 = normalize((TR + 2.0*R + BR) * 0.25 - C);
float3 v2 = normalize((TL + 2.0*T + TR) * 0.25 - C);
float3 v3 = normalize((TL + 2.0*L + BL) * 0.25 - C);
float3 v4 = normalize((BL + 2.0*B + BR) * 0.25 - C);

float3 N1 = cross(v1, v2);
float3 N2 = cross(v3, v4);
Normal = (N1 + N2) * 0.5;

// Write Normal to Shared Memory
SharedMemory[GroupIndex].Normal = Normal;
}[/source]

This works very well in most situations.
Unfortunately, once I get to very high LOD levels, floating point precision causes quite a few issues.

In order to illustrate the problem I make the compute shader generate a sphere of radius 1.
I then use the following code to display the error rate of the generated normal vectors:
[source lang="cpp"]float3 NormalError = abs(Normal - normalize(PositionWS)) * 10.0;[/source]

LOD 16 - First signs of errors, no visual artifacts
[img]http://i.imgur.com/bPtfZ.jpg[/img]


LOD 20 - First visual artifacts. Can be masked with normal mapping or some perlin noise.
[img]http://i.imgur.com/kShNl.jpg[/img]


LOD 24 (highest lod): Visual artifacts are visible all over the terrain.

[img]http://i.imgur.com/QhehH.jpg[/img]


At this LOD, vertices are only 0.0000000596 units apart from each other, hence the problem with my current method for generating normal vectors.

I understand that I'm pushing the limits of floating point precision here, and not having that high of a terrain resolution isn't that big of an issue, but I was wondering if anyone had any ideas on how to squeeze out a little more detail?

Cheers,
Hyu
0

Share this post


Link to post
Share on other sites
Have you considered changing both the model size/co-ordinates and the zoom level when switching LOD levels? Essentially it would be the same as how many tile based systems occasionally re-centre the current tiles around 0,0 to maintain floating point precision. You want your model to have coordinates in a particular range, e.g. -1000 to 1000, so just renormalise them to suit.
1

Share this post


Link to post
Share on other sites
To some extend, yes.
But the base algorithm generating the terrain generates vertices for a [-1, 1] cube, which are then mapped to a unit sphere.
All of this is done entirely on the gpu, which means single precision.
I can scale and translate these vertices of course, which improves normal vector generation.
But the trade-off is that I introduce some jitter in the vertex positions, which will influence the normal vectors.
It is fine most of the time, but in some situations it creates easily recognizable patterns.

I've also experimented with using partial double precision, but support for this is unfortunately still very limited.
0

Share this post


Link to post
Share on other sites
My main advice is unchanged, but if you want to squeeze a little extra out, remember that you're throwing away a lot of bits of precision by making everything size 1 or less. Try making the cube -10,000 to 10,000 and the sphere size 10,000. You might get a little extra precision at the low end.
1

Share this post


Link to post
Share on other sites
I think that is indeed the best way to go about it.
I'll need to make some modifications to my cube to sphere mapping formula, but that shouldn't be too difficult.

Thank you for your advice!
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