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

Which edge is which when tessellating?

6 posts in this topic

Ok, so I have 10 control points for a 3 order bezier triangle. It is arbitrary which points are which, I know who they are and how to use them, but there is no obvious relation to these points from the edges to tessellate. In my hull shader, I decide how much to tessellate each of the three edges, but how do I know which edge is edge zero, one, two etc?

 

For example, if cp[0], cp[1] and cp[2] are the control points to my bezier triangle corners, how do I decide how much to tessellate each edge based on the screen size of the edge?

0

Share this post


Link to post
Share on other sites

You know the orientation of the control points relative to one another, and you know the world transformation that they are being transformed with, so you should have the information that you need.  If you are currently doing the transformation in the domain shader, then you may have to move that back to the hull shader.  Then you can transform each control point, and then using whatever metric you want you can adjust the tessellation accordingly.

 

In general this is better than doing the transformation in the domain shader, since it is running after the amplification from tessellation.  Always try to push the computation upstream if possible!

1

Share this post


Link to post
Share on other sites

Here is my current hull shader:

PatchConstants PatchHS(InputPatch<VertexOutput,10> cp, uint patchID : SV_PrimitiveID)
{
	PatchConstants pt;

	pt.EdgeTess[0] = 6;
	pt.EdgeTess[1] = 6;
	pt.EdgeTess[2] = 6;
	pt.InsideTess = 6;

	return pt;
}

 

How do I know which cp's are associated with pt.EdgeTess[0]? I have to make sure that shared edges are tessellated the same way. My shader pipeline currently supports two forms of triangle input sets, one pointing up and the other pointing down. After translating them with my matrices, they could be oriented any old way. If one of my edges on my triangle is short on the screen, how do I know which element in the EdgeTess array to decrease?

0

Share this post


Link to post
Share on other sites

In general this is better than doing the transformation in the domain shader, since it is running after the amplification from tessellation.  Always try to push the computation upstream if possible!

 

In my case, the domain shader is calculating patch surface normals according to world space. If transform my control points to screen space in the hull shader, I wouldn't be able to calculate normals any more, because at that point all the geometry is co-planar correct?

Edited by cephalo
0

Share this post


Link to post
Share on other sites

Ok, I have discovered that by setting one of my tessellation factors to 3, I can find out by visual experimentation which edge is which. It appears to be a stable association that is NOT dependent on the view space. In my case, the edge from cp[0] to cp[1] is edge index 2, edge cp[1] to cp[2] is edge index 0 and edge cp[2] to cp[0] is edge index 1. In my case, they also seem to line up by accident so I don't have to worry about mismatched shared edges.

 

Strange. Is there any way to predict this without experimentation? There must be some rule it would seem.

0

Share this post


Link to post
Share on other sites

Here is my current hull shader:

PatchConstants PatchHS(InputPatch<VertexOutput,10> cp, uint patchID : SV_PrimitiveID)
{
	PatchConstants pt;

	pt.EdgeTess[0] = 6;
	pt.EdgeTess[1] = 6;
	pt.EdgeTess[2] = 6;
	pt.InsideTess = 6;

	return pt;
}

 

How do I know which cp's are associated with pt.EdgeTess[0]? I have to make sure that shared edges are tessellated the same way. My shader pipeline currently supports two forms of triangle input sets, one pointing up and the other pointing down. After translating them with my matrices, they could be oriented any old way. If one of my edges on my triangle is short on the screen, how do I know which element in the EdgeTess array to decrease?

It actually doesn't matter (I know - that isn't intuitive...).  As long as neighboring patches share the same control points, and the control point to tessellation factor algorithm will produce the same output for the given input control points, then the order doesn't make any difference. 

 

But for the same reason you are having trouble to understand it, it would be impossible to have a standard notation to say which control point goes where since it depends on the primitive topology, the number of control points, and so on.  I believe there is a way to identify where a control point is located within a control patch, but I don't think there is one for the oriented control patches.

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