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

why the gl_ClipDistance[] doesn't work?

8 posts in this topic

I just can't understand why the gl_ClipDistance doesn't work. The result is the same as I didn't set the gl_ClipDistance.

I had set glEnable(GL_CLIP_DISTANCE0+2) by application.

the vertex shader is like this:

#version 410

uniform mat4 mvpMatrix;
//.......some other uniforms here
in vec2 vVertex;
uniform vec4 clip_plane=vec4(1.0,1.0,0.0,0.85);
uniform vec4 clip_sphere=vec4(0.0,0.0,0.0,10.0);

void main(void)
{
//........some other code,include vec2 worldPos
vec4 worldPosition=vec4(worldPos.x,height,worldPos.y,1.0);
gl_ClipDistance[0]=dot(worldPosition,clip_plane);
gl_ClipDistance[1]=length(worldPosition.xyz/worldPosition.w-clip_sphere.xyz)-clip_sphere.w;
gl_Position = mvpMatrix * position;
}
0

Share this post


Link to post
Share on other sites

Clipping works perfectly, but you have to enable it. ;)

 

By setting glEnable(GL_CLIP_DISTANCE0+2), you have enabled gl_ClipDistance[2], not 0 and 1.

Also, I'm not sure whether your math is correct or not. It depends on your algorithm.

 

Just to know, if gl_ClipDistance[x] > 0.0, the vertex is visible, if it is <= 0.0, it is clipped.

 

1

Share this post


Link to post
Share on other sites
&nbsp;

Clipping works perfectly, but you have to enable it. ;)
&nbsp;
By setting&nbsp;glEnable(GL_CLIP_DISTANCE0+2), you have enabled&nbsp;gl_ClipDistance[2], not 0 and 1.
Also, I'm not sure whether your math is correct or not. It depends on your algorithm.
&nbsp;
Just to know, if&nbsp;gl_ClipDistance[x] &gt; 0.0, the vertex is visible, if it is &lt;= 0.0, it is clipped.

&nbsp;
Thank you! I tried "glEnable(GL_CLIP_DISTANCE0) ;glEnable(GL_CLIP_DISTANCE1) ;",but it still didn't work. I guess maybe something else is not right.
0

Share this post


Link to post
Share on other sites

Then your code is wrong, as I presumed.

There is no need for multiple clip-distances. Set just gl_ClipDistance[0].

And, in order to prove that it works, set gl_ClipDistance[0] = -1.0;

If your model disappears, clipping works. :)

0

Share this post


Link to post
Share on other sites
&nbsp;

Then your code is wrong, as I presumed.
There is no need for multiple clip-distances. Set just&nbsp;gl_ClipDistance[0].
And, in order to prove that it works, set&nbsp;gl_ClipDistance[0] = -1.0;
If your model disappears, clipping works. :)

&nbsp;
I set "gl_ClipDistance[0] = -1.0;" as you saied, but what make me confused is that the result is not changed, my model didn't disappear.
0

Share this post


Link to post
Share on other sites

 

I set "gl_ClipDistance[0] = -1.0;" as you saied, but what make me confused is that the result is not changed, my model didn't disappear.

 

I hope you have couplet it with glEnable(GL_CLIP_DISTANCE0); in the host application, and the shader is actually executing.

 

Maybe you should read a little bit about the topic. There is a lot of material in all OpenGL related books:

  • OpenGL SuperBible 5th Ed. – pg.528
  • OpenGL SuperBible 6th Ed. – pg.276-281.
  • OpenGL Programming Guide 8th Ed. – pg.238
  • OpenGL Shading Language 3rd Ed – pg.112, 286
     
0

Share this post


Link to post
Share on other sites

I hope you have couplet it with&nbsp;glEnable(GL_CLIP_DISTANCE0); in the host application, and the shader is actually executing.

Maybe you should read a little bit about the topic. There is a lot of material in all OpenGL related books:

  • OpenGL SuperBible 5th Ed. – pg.528
  • OpenGL SuperBible 6th Ed. – pg.276-281.
  • OpenGL Programming Guide 8th Ed. – pg.238
  • OpenGL Shading Language 3rd Ed – pg.112, 286
     

actually,I had read related content in OpenGL SuperBible 5th Ed,OpenGL SuperBible 6th Ed and OpenGL Shading Language 3rd Ed. And I set “glEnable(GL_CLIP_DISTANCE0)” in the application of course.

Edited by yan_qingsong
0

Share this post


Link to post
Share on other sites
The problem is solved.The code is right. GPU is the key. When I change the AMD card to NVIDIA card, the code works well.
0

Share this post


Link to post
Share on other sites

The problem is solved.The code is right. GPU is the key. When I change the AMD card to NVIDIA card, the code works well.

That, however, is no solution. A third of your customers has an AMD card, so your code must work on these.

 

The phenomenon "works on nVidia, doesn't on AMD" usually comes from the fact that AMD's GLSL implementation is rather rigidly following the specification, whereas nVidia passes GLSL through their Cg compiler, which is a bit more relaxed and allows things that are actually not allowed if you are really strict about the spec (which isn't as good as it sounds, actually that's rather bad -- it should complain when something isn't quite right).

 

Be sure (absolutely positive!) that you do not see any warnings in your shader log, and run your shader code through the reference compiler. Only if the reference compiler does not emit an error or a warning (and I'm almost sure it will!) you might consider the problem "solved" (but then, you should file a driver bug report, since after all if your shader is correct, then it must execute correctly, too).

Edited by samoth
1

Share this post


Link to post
Share on other sites

@samoth
You are right. When I compile the vertexshader using the reference compiler,it emit a warning. The warning says that version 410 is not yet complete. how to solve this problem?

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