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

Artifacts on Intel HD Hardware

4 posts in this topic

Hi everyone!

 

I'm experiencing strange rendering artifacts when running my program on Intel graphics hardware. According

to Google that's not unusual, so I'm hoping you guys have some advice for me smile.png

 

See the attached image. I have a NVIDIA Optimus laptop setup. On the right side you see the output

of the dedicated NVIDIA GPU, which i consider to be correct. On the left side you see the output of the

Intel HD 3000 onboard GPU, using the most recent drivers, showing some kind of white stripes, which

flimmer when moving the object or the camera. I think this looks like z-fighting.

 

I'm doing pretty basic multiple pass lighting, with this setup:

Pass No.  DepthMask DepthFunc

0              TRUE          LESS

1              FALSE        EQUAL

>1            FALSE        EQUAL

The problem does not show up if I render only one pass.

 

I tried to eliminate the most likely reasons for z-fighting:

On both GPUs the depth buffer is 24bit in size. (checked using glGet*(GL_DEPTH_BITS)

and QGLFormat::depthBufferSize())

In my projection matrix, I set [zNear, zFar] to reasonable values, eg. [0.1, 100], [1, 40].

Playing around with glPolygonOffset didn't solve the problem.

 

The white stripes are still visible, when I draw the mesh in solid black, by setting the lighting

color to black.

When I disable blending, the stripes become black and the problem remains the same.

 

So basically, I have no idea what to do smile.png Do you guys have any advice or idea

what might be the problem?

 

1

Share this post


Link to post
Share on other sites

That definitely looks like depth fighting.

 

Are you sure the depth buffer is *actually* 24-bit? Potentially the driver could be giving you a lower bit-depth than you requested.

1

Share this post


Link to post
Share on other sites

Yup, it's almost certainly Z-fighting.

 

I'd advise forgetting about polygon offset for starters; it's not intended as a general-purpose solution to Z-fighting, and the specification allows it's effects to be implementation-specific - in other words, it's fairly useless.

 

Instead, have a look at how you're drawing - specifically how you're transforming - the polygons that fight.  Do they share the same geometry as other scene polygons?  Are you using ftransform for one set but matrix multiplication for another?  Or fixed pipeline for one set but programmable for another?  Because OpenGL isn't a pixel-exact specification, and because you may be using paths where invariance isn't guaranteed, it's entirely possible that the Intel behaviour is actually within spec (i.e. not a bug) but just undesirable nonetheless.

 

Ultimately the solution of last resort may be to adjust your source geometry so that this kind of thing doesn't happen.

2

Share this post


Link to post
Share on other sites

Yeah, was going to say the same what mhagain just said, are you transforming the vertices the same way in all lighting passes?

 

Also, if there are actually overlapping polygons in the same model, it may lead to double-lighting artifacts in light passes.

Edited by AgentC
1

Share this post


Link to post
Share on other sites

Hey guys, great tips!

 

You were right about the vertices being transformed differently in different passes.

Here is what caused the z-fighting:

Pass0:
gl_Position = uProjection * uTransform * aPosition;
 
Pass1:
vec3 worldPos = (uTransform * aPosition).xyz;
// ...
gl_Position = uProjection * vec4(worldPos, 1.0);

 

Simply using the same expression for gl_Position in every pass

solves the problem:

(at least in my case, I think it depends on compiler optimizations)

Pass0:
 
vec3 worldPos = (uTransform * aPosition).xyz;
gl_Position = uProjection * vec4(worldPos, 1.0);

 

It's even simpler than that. The following code solves the problem

as well and is a great example for non-associativity of floating 

point arithmetic:

(glsl multiplication is left-associative)

Pass0:
gl_Position = uProjection * (uTransform * aPosition);

 

Cool :) Thank you guys very much!!!

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