Sign in to follow this  
Lutz

OpenGL Strange texture artifact

Recommended Posts

Hey! Yesterday I wanted to fix the texture transitions in my planet rendering program. I knew it's a bit tricky, so for debugging reasons I gave my textures a red border (so really the image has this border, it's not an opengl texture border). When I map the textures to the planet, it looks like that: Note the blocky artifacts near the red lines (which is the texture transition zones). (No, these are no JPEG-artifacts;-) ) And my texture image definitely does not have this artifacts. It still keeps happening when I disable mipmapping, linear max-filtering AND texture compression. If I take a texture which is completely white with a red border, there are NO artifacts. However, to me it looks like texture compression artifacts. But even if I haven't specified texture compression in my program it still happens, so I find it quite strange. So I have some questions: 1) Could it be texture compression artifacts? 2) Can OpenGL enable texture compression although I didn't tell it to? 3) How can I ask OpenGL whether the textures are compressed? Any suggestions? I have an Athlon 1400Mhz with an ATI 9800Pro (128MB), 256 MB RAM, the screen is 800x600x32BPP, the textures are 256x256x24BPP.

Share this post


Link to post
Share on other sites
Maybe something like glEnable(GL_CLAMP); may solve the problem.

OpenGL 'loops' textures, unless you tell it shouldn't.

Still, your screenshot shows quite large artifacts, while not clamping only produces small ones. So, maybe is something else..

Share this post


Link to post
Share on other sites
It's not the clamping.
My texture coordinates are in the range 1/(2N)...1-(1/2N), where N=256 is the texture size, so that pixels on the very boundary of the polygon map to the center of the boundary texel (i.e. the red border texel).

Share this post


Link to post
Share on other sites
Quote:
Original post by Lutz
It still keeps happening when I disable mipmapping, linear max-filtering AND texture compression.

If I take a texture which is completely white with a red border, there are NO artifacts.


This is very strange.How do you load your textures?

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Depending on video card settings, the texture may be compressed even if you don't explicitly ask for it to be programatically. I know my radeon 8500 has a 'texture quality' setting which seems to lower the size and/or compress textures more than programs request. Such a driver setting may be the cause of your problem

-Extrarius

Share this post


Link to post
Share on other sites
Extrarius:
Ah, interesting, that's what I expected.
How can you ask OpenGL whether a texture is compressed?
And how can you make it NOT compress textures?

okonomiyaki:
Yes, the red line is just one pixel.

I tried linear max filters and nearest neighbour max filters, both showed artifacts, with and without mipmapping.

Before I put the red lines in, I figured out how to make the texture transitions continuous (even when zooming in). The solution (I believe) is to use the same border texels for the involved textures, i.e.

|--------------| |--------------|
| a| |a |
| Texture 1 b| |b Texture 2 |
| c| |c |
|--------------| |--------------|

(a,b,c are some border colors)
Then, if you draw triangles with textures 1 and 2 side by side, the transition should be continuous (if you don't mess with the texture coordinates...).

However, the transition was NOT continuous and I figured out that the problem must be that the border colors do not coincide (indeed, you saw that). So I just set the border colors to red (to make sure that the problem was not my texture generation routine making the border colors different), so I KNEW the border colors are the same (at least in the BMP file) and I saw those artifacts.

So the bottom line: Without the red line you don't really see such blocky artifacts but the transition is not continuous since the border colors don't coincide. I guess the reason is a compression algorithm which does not create visible artifacts without the red line, but changes the colors slightly so that the transition is no longer continuous.

Texture compression would explain why you really see those artifacts only you put the red line in: The texture just can't be compressed very well anymore, so the compression becomes lossy. Like when you try to compress a fractal image with JPEG, you'll get huge artifacts. When you JPEG a smooth image, you don't see artifacts.


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
      628401
    • Total Posts
      2982452
  • 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