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

Inverse fog, Ugly interpolation

4 posts in this topic

I tried to do something like inverse fog, where the closer the points are to you the more fog they get. But its not good, I can see the triangles of the surface.

 

I also tried it with a surface that looks like a spider web and you stand in the middle, ...but there I could see the horizontal lines. On the picture Ive changed the contrast so in the game is not as visible, but still ugly enough.

 

Ive tried it with higher surface resolution, it didnt really help. Is there a workaround for this or is this just the way interpolation works?

 

surface.png

0

Share this post


Link to post
Share on other sites

It looks like the fog values are being calculated per vertex. If you have control of the vertex/pixel shaders then you could try changing it so that the distance from the eye position is calculated on the vertex shader (as this will interpolate linearly quite well), and then the fog equation is applied on a per pixel basis.

 

If you're using some technology that doesn't let you control the shaders then it might be trickier, you'll probably end up having more triangles, or a fog that blends in more gently so the artifacts are not so visible.

1

Share this post


Link to post
Share on other sites

Thanks! Actually, Im trying to create a water surface where the fog level(alpha component, originally) depends on the angle at which you can see the surface(the vertices).

 

This is a simplified shader, but it produces the same thing:

#version 330 core

layout(location = 0) in vec3 vertex_pos;
layout(location = 1) in vec3 vertex_color;

uniform mat4    V_rot;
uniform mat4    V_tran;
uniform mat4    P;

out vec4   color_VOUT;

void main(){

    vec4    pos_TRAN_ONLY =     V_tran * vec4( vertex_pos, 1);    
    float   pos_dist =          length( pos_TRAN_ONLY.xyz);

    float   alpha_level = 1 - abs( pos_TRAN_ONLY.z) / pos_dist;     //1 - sin( alpha)

    color_VOUT =    vec4( vertex_color, 1);    
    color_VOUT.r =  alpha_level;                                    //set the RED component, so its more visible.

    gl_Position = P * (V_rot * pos_TRAN_ONLY);

}

Sorry, I dont get why setting the distance instead of the color would be interpolated better.

 

...now as Im thinking, it can be that the color (which depends on the distance) is interpolated linearly on a given line of a triangle, but the distance from the camera is not linear. or something like that.

 

Edit:

The fragment shader doesnt do anything now, just sets the output color.

Edited by Aliii
0

Share this post


Link to post
Share on other sites

When you pass data from your vertex shader to your pixel shader, the GPU will interpolate values linearly. In many cases (e.g. interpolating UV coordinates), this linear interpolation is correct. However, for other functions, the linear interpolation will introduce some errors. Calculations done on the vertex shader are much cheaper and part of writing shaders well is balancing the performance versus accuracy of doing calculations per vertex.

 

I suggested passing distance from camera to the pixel shader and doing the remaining calculations on the pixel shader. This is because the distance from camera is a big part of the fog calculation and it's pretty linear (although not perfectly so, imagine the case where you're standing on a very large triangle). If you really needed complete accuracy you could pass the vertex positions through to the pixel shader and do the entire calculation per pixel.

1

Share this post


Link to post
Share on other sites


I suggested passing distance from camera to the pixel shader and doing the remaining calculations on the pixel shader. This is because the distance from camera is a big part of the fog calculation and it's pretty linear (although not perfectly so, imagine the case where you're standing on a very large triangle). If you really needed complete accuracy you could pass the vertex positions through to the pixel shader and do the entire calculation per pixel.

 

Thanks! It worked out perfectly.

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