# Modify Tessellation shader to make equilateral triangles?

This topic is 1867 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Continued from: http://www.gamedev.n...with-triangles/

Details:
I'm in the proccess of procedural planet generation; so far I'm doing the sphere work.
Currently my sphere is a subdivided icosahedron. (20 sides all equilateral triangles)

Before, when I was subdividing using a software algorithm, one triangle would be
split into four children across the midpoints forming something close to a
sierpinski triangle every iteration...like this: http://puu.sh/1xFIx

As you can see, each triangle subdivided created more and more equilateral triangles.

But now that I am using the GPU to tessellate in HLSL, the result is definately not
what I am looking for: http://puu.sh/1xFx7

Questions:
Is there anything I can do in the Hull and Domain shaders to change the tessellation
so that it subdivides into sets of equilateral triangles like the first image?

Should I be using the geometry shader for something like this? If so, would it be
slower then the tessellator?

Thanks for the time Edited by Dr. Krunklehorn

##### Share on other sites
*Bump* nearly 250 views and 0 replies. =T

##### Share on other sites
I think I speak in the name of some of the other nearly 249 people when I say that I don't have a good answer to your question.

I have done dynamic refinement of triangle meshes before, and one has to be careful to make sure that you don't introduce gaps between triangles where you refined one and not its neighbor. The naive method that divides a triangle into four by subdividing the sides in half would suffer from this. The method of dividing the longest side as long as that side seems too long doesn't suffer from this problem, and it could be what's resulting in the pattern you don't like (I think it looks kind of cool, actually).

##### Share on other sites
My thought was why do you require equilateral triangles to be generated?

##### Share on other sites

I think I speak in the name of some of the other nearly 249 people when I say that I don't have a good answer to your question.

Ah okay that's fine. I was hoping someone else had come across a similar problem with the default tessellation pattern in DX11.

I've done a ton of research since I first posted this question. Articles, PDF's, white papers, tech demos etc. have all helped me
get a better understanding of what the domain shader actually see's and what I have to work with in it.

I'm going to see if I can find a way to do this in the domain shader. (cracks are a fix-later problem) If I can't, that's fine too. I

What I'd like to be sure of is the performance difference though. If I were to mimic the tessellation shader in the geometry
shader, would the geometry shader method operate slow-er enough to call it a big deal?

My thought was why do you require equilateral triangles to be generated?

If I was to subdivide a cube into more and more quads then map that to a radius, the result has an ugly distortion around
the corners. Using equilateral triangles from an icosahedron base nearly solves this problem because it is the highest
order platonic solid you can make. I.E: it is the best "base" to start from if you want to avoid that corner distortion side
effect of the cube method.

##### Share on other sites

I've done a ton of research since I first posted this question. Articles, PDF's, white papers, tech demos etc. have all helped me
get a better understanding of what the domain shader actually see's and what I have to work with in it.

I'm going to see if I can find a way to do this in the domain shader. (cracks are a fix-later problem) If I can't, that's fine too. I

What I'd like to be sure of is the performance difference though. If I were to mimic the tessellation shader in the geometry
shader, would the geometry shader method operate slow-er enough to call it a big deal?

Have you inspected this PDF?

http://developer.dow...essellation.pdf http://developer.dow...essellation.pdf

You could get what you want (terrain height) if you use displacement mapping and keep the equilateral tessellation.

EDIT: Also check out this video --- are these the kinds of triangles you want to end up with? [media]
[/media]

http://recreationstudios.blogspot.com/2010/03/simple-tessellation-example.html Edited by Steve_Segreto

##### Share on other sites
are these the kinds of triangles you want to end up with?

That's actually a perfect demonstration of what I am trying to avoid. The method shown in that video is exactly
why cube based spheres get distorted.

Notice the vertex density on the top of the sphere, compared to the vertex density around what would be
the corner of the original cube.

Already there is a big difference: the triangles on top of the sphere are stretched out and the ones near the
original corner point are very small and clustered.

Now if the camera in my planet application was to fly around on ground level, the effect of this distortion
would be easily noticeable. A mountain range around a clustered corner is going to look much better
then a mountain range around the stretched areas on top.

Equilateral triangles is the solution here. They stay the same size all the way around the sphere.