Sign in to follow this  
Amitola85

OpenGL Particle Flicker in the distance

Recommended Posts

I read the FAQ on Z-Fighting, but am unable to alter the Z-near / Z-far planes to adjust the issue (for good reasons). Also, 24-bit double-buffering appears to already be in use. I've landed in this mess of a project. For a brief description: There is map over which a plane flies. The map renders fine. There are also little 'Targets' on the map, which are drawn seperately from the map. They are small, and they move. At a distance they flicker, that is: in one frame they are drawn, in the next they are not (somewhat randomly). I must eliminate this flicker. The project will be used to run simulations of spotting those Targets, and flickering (of course) immediately draws the eye's attention, which would make any results from the simulations useless, since in real life things don't just disappear and reapper at random. I am fairly new to OpenGL, and am learning as much as possible, but I can't seem to find anything to help me out on this problem. Unfortunately we have no OpenGL expert around to help (Academic Research....). Anyone have any advice on eliminating, or at least drastically reducing the flicker that is occurring? Once the Targets get close enough to the camera the flicker effectively stops. As I already said, I've tweaked the Znear and Zfar planes as much as possible, but it's only helped some. Thanks for any help!

Share this post


Link to post
Share on other sites
Quote:
Original post by Glaiel_Gamer
i am new to openGL too, but try mipmapping
If the problem is z-fighting, which it certainly sounds like, mipmapping won't help. That only affects the texture quality. It is a good suggestion to use mipmapping with textures that will be seen from varying distances though, so if the map and targets are textured I would use mipmapping.

If you haven't read it yet, check out Learning to Love Your Z-buffer to get a better understanding of how the depth buffer works and how the near and far planes relate to it.

You may be able to get good results using glPolygonOffset. It needs to be enabled with one of the GL_POLYGON_OFFSET_* contants. See glEnable for more info on those. It is a pain to find good values for it however so I would avoid if it at all possible.

You shouldn't need to use polygon offset though if you have reasonable near and far plane values, so I'm curious why you can't adjust them anymore. Is it because the airplane and targets are too far apart? If that's the case you should be able to scale the world so that they are within a closer range so that you can use better values for the near and far planes.

EDIT: Another possible solution is to render with two separate frustums. The basic idea is you set the near and far planes so that they contain the farther away objects (the map and targets), render them, clear the depth buffer (important!), set the near and far plane values so that they contain the nearer objects (the airplane), then render that.

Share this post


Link to post
Share on other sites
Thanks for the suggestions. I don't think mipmapping will help any, since no textures are being applied to the Targets.

I'll read through the Z-buffer information you linked to; once I understand it better I may be able to tweak things more. I can't change the values now, since the plane is being shown from a chase perspective (so it's about 1 meter from the camera), flying at an altitude of 50-500 meters, and the camera is pointing at an angle of about 30 (Deg) from horizontal. So you see things out to the horizon.

I think the idea of rendering with two seperate frustrums sounds pretty promising, if I don't figure something better out from the readings.

Once again, thanks for the help. I'll try to remember to post a solution if I find one.

Share this post


Link to post
Share on other sites
Actually... Thinking about it a little more, I may be able to ignore the fact that we're in a chase view, since I won't need it for the purpose of my simulations (I'll just need to remember to change back the zNear value before someone else uses the code...)

I'll try some more tinkering...

Share this post


Link to post
Share on other sites
I've moved the near clipping plane out; but it doesn't seem to affect the ficker at all.

Even when the Targets are just about to come inside the clipping plane (ie they are very close to it, but still in front of it) they still flicker. Maybe the problem is something different?

[edit]
So, umm.. I think the problem may actually just be that at the distance, the Targets only fill 1 or 2 pixels; so sometimes it decides that the pixel will be the Target color, and sometimes it decides the pixel will be the ground color. So there may not be a real solution to my flicker problem... maybe anti-aliasing on the Targets, so they get blurred over a couple of pixels?
[\edit]

[Edited by - Amitola85 on March 15, 2006 5:55:12 PM]

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
I'm going to throw out the term 'Subpixel Accuracy'
because I think it may be relevant, Quake used to to avoid wierd jaggy skippy lines.
I have no idea how it works though, but hey, you never know...

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  

  • Announcements

  • Forum Statistics

    • Total Topics
      628379
    • Total Posts
      2982344
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now