Jump to content
  • Advertisement
Sign in to follow this  
vonsatan

Strange issues with flickering triangles

This topic is 3559 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

So I have this issue that only appears on nVidia cards..... and seems to be related to the way multiple frames are drawn (capturing one frame in PIX doesn't exhibit the issue) On a solid mesh, some trangles randomly flicker on and off, like they are being culled somewhere (but the depth buffer appears to still be written to).... this only happens on shaders that use ps_3_0.... I'm at a bit of a loss .... anyone experienced anything similar?

Share this post


Link to post
Share on other sites
Advertisement
Sounds like Z-buffer precision issues to me. What format is your depth buffer, and what are your near and far clip planes set to in your projection matrix? You want the near clip plane as far as possible (And definitely non-zero, ideally 0.1f or further), and the far clip as close as possible (No higher than around 1000.0f for a 16-bit depth buffer).

Share this post


Link to post
Share on other sites
thanks for the reply...

hoever, highly unlikely to be depth buffer precision problem, the problem occurs on entire polygons(any size) ....throughout the scene. (also, the problem disappears when a replayed in a PIX capture frame) And changing the near/far planes doesn't help.

so strange...... introducing an artificial CPU stall between frames removes the problem... but this is obviously an unworkable solution :P


/annoyed

Share this post


Link to post
Share on other sites
You could be overwriting a portion of a vertex buffer which is currently in use. This would explain the randomness, also why an artificial stall makes the problem go away.

Share this post


Link to post
Share on other sites
I had the same problem.

Introducing an artificial CPU stall between frames removed the problem for me as well but that would never work for my project since it was already going way to slow. I never figured it out and just upgraded to DX10 since there was no way to fix it. Now I found another bug in DX10 that creates a memory leak, I don't like being one of the only people to find huge bugs in DX...

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!