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

Noticable seams when blending textures

4 posts in this topic

For my terrain I have 4 available textures which I am choosing/blending based on the pixels coordinates and the surface normal. For example I can choose to use a rocky texture for steep slopes, grass for low elevation, snow for high elevation, etc.

Right now I am testing the function just blending two textures.When the texture normal.y is less than 0.95 I use the grass texture. When the texture noramal is greater than 0.99 I use the stone texture. When in-between, I linearly interpolate between the two. 

Here are the driving functions:

float myInterp(float x1, float y1, float x2, float y2, float x)
{
	float m=(y2-y1)/(x2-x1);
	float b=y1-m*x1;

	return (m*x+b);
}

vec4 ComputeTexture(vec2 TexCoord, sampler2D rock, sampler2D grass, sampler2D stony_grass, sampler2D stone)
{
	 vec3 _Normal = normalize(Normal);

	if (_Normal.y <= 0.950f)
	 {
		
		return texture(grass, TexCoord);
	 }

	 if (_Normal.y <= 0.99f)
	 {
		float weight=myInterp(0.95f,1.0f,0.99,0,_Normal.y);

		vec4 color= ( texture(grass, TexCoord)*weight + texture(stone, TexCoord)*(1-weight));
		color.a=1.0f;
		return color;
	 }
	 
	 return texture(stone, TexCoord);

}

Here is the result:

texture_seams_zpsu2bg5dpi.png

Notice the seams just outside and running parallel to the stone paths. I've observed the seams seem to occur for far away pixels and disappear when viewed up close.

My textures files are seamless textures, and as is shown in the code, the texture coordinates are the same, it is only the choice of texture that is changing (and the blend weights).

I made sure all textures are of the same resolution, file type, and their sizes are powers of 2.

 Any idea what could be causing this?

1

Share this post


Link to post
Share on other sites
Although it makes no sense to me, the seams appear where you switch to use either one or two textures (but the math is correct).

Did you try to load both textures in any case and blend them by a clamped weight?
Maybe clamp between [0.01, 0.99] to force two textures. Just to see if it makes a difference.
1

Share this post


Link to post
Share on other sites

Thanks for the response, JoeJ.

Based on your response, I tried the following (I didn't do any clamping though)

 

vec4 ComputeTexture(vec2 TexCoord, sampler2D rock, sampler2D grass, sampler2D stony_grass, sampler2D stone)
{
	 vec3 _Normal = normalize(Normal);

	 float grass_weight=1.0f;
	 float stone_weight=0.0f;

	 if (_Normal.y <= 0.950f)
	 {
		
		 grass_weight=1.0f;
		 stone_weight=0.0f;
	 }
	 else if (_Normal.y <= 0.99f)
	 {
		grass_weight=myInterp(0.95f,1.0f,0.99,0,_Normal.y);
		stone_weight=(1.0f-grass_weight);
		
	 }
	 else
	 {
		grass_weight=0.0f;
		stone_weight=1.0f;
	 }

	 vec4 color=grass_weight*texture(grass,TexCoord)+stone_weight*texture(stone,TexCoord);
	 color.a=1.0f;

	 return color;


}

That fixes the seams! I really don't know why though... haha

0

Share this post


Link to post
Share on other sites
No clue either, but i guess there is something different with the textures then. (mip maps or anisotropic filter, ...?)
May be worth to figure out, reading textures for nothing may have some cost.

But in case reading both is ok, you can still remove a lot of branches:

ec4 ComputeTexture(vec2 TexCoord, sampler2D rock, sampler2D grass, sampler2D stony_grass, sampler2D stone)
{
	 vec3 _Normal = normalize(Normal);

	 float weight=myInterp(0.95f,1.0f,0.99,0,_Normal.y);
	weight = clamp(weight, 0.0, 1.0);

	 vec4 color = weight*texture(grass,TexCoord) + (1.0-weight)*texture(stone,TexCoord);
	 //color.a=1.0f;

	 return color;


}
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