Sign in to follow this  

OpenGL Dealing with 2D coords as ints

Recommended Posts


I have written a very rudimentary D3D11 renderer and am now working with SFML (OpenGL). I am only interested in 2D games at the moment so I was just rendering quads to the screen in D3D and would like to do the same thing with GL in SFML.

However, I have one big problem. In order to work directly with the hardware I have to be in floating point coordinates, which is not only inconvenient for me, but is causing some bleed in my program. For example, I have a texture atlas with a single black pixel, surrounded by some blue pixel blocks representing buttons. I want to use that single black pixel and scale it up 1920x1080 times and use it as a black background. But when i do so I get some bleeding and there is a gradation of blue on my screen. I have a feeling this is due to floating point inaccuracy.

I need my games to be pixel accurate and I was wondering how I could do this in GL/D3D without having to resort to floating point numbers. At the same time, I don't only want to be able to run my game in 1920x1080 but at any resolution that the user wants in windowed mode. I am a bit lost as to how I would represent this with ints, as I don't want my character to move farther on the screen in windowed mode than in full screen, because if I say move 30 pixels left, 30 pixels is a lot in a 200x200 window but not much in a 1920x1080 fullscreen mode.

Does anyone know how to do this or am I stuck using the basic graphics package in SFML. I spent significant time learning D3D and basic 3D graphics principles and to be honest I don't want to sink anymore time there right now. I am not interested in 3D at all and am a bit peeved that I have to learn all this 3D stuff just to get a 2D game running very efficiently on the 3D hardware. Does anyone have an idea?


-Dave Ottley

Share this post

Link to post
Share on other sites
Talking about the bleeding problem - I don't think this is really a floating point accuracy issue, it's a texture sampling issue.

You want scaling, so that means you won't be able to do 1 to 1 texel to pixel mapping no matter how hard you try. This means you're going to be bilinear filtering on your textures. With texture atlases you need to add a border around each of images so that the bilinear filtering doesn't accidentally pull in any adjacent images. An alternative is to modify your UVs so that the UV rectangle is squeezed inwards by half a texel on all sides, but that'll cut off a little of your image slightly so you won't always get away with it.

If you need mipmaps for your atlases then that can be extra tricky, and you'll generally need larger borders, possibly some custom mipmap generation that discourages bleeding across atlas tiles or some atlas generation rule that encourages atlas tiles to align with power of two grid lines so that there's less bleeding in your lower mips. Edited by C0lumbo

Share this post

Link to post
Share on other sites
[quote name='KingofNoobs' timestamp='1355405731' post='5010199']
Could I deal in floats but use some math magic to make the top left of the screen 0.f,0.f and the bottom right 1920.f,1080f?

That's straightforward enough, I think. Assuming you're using shaders in OpenGL, you to use a projection matrix like the one documented here: [url=""][/url]. If you're using fixed function OpenGL, then you can just use the glOrtho function directly.

The problem is that you might need to think about how to deal with different aspect ratios. Sometimes working to a 14:9 virtual resolution is best, then cut off bits or black bar it to cope with 4:3 and 16:9 - depends on your game really. Edited by C0lumbo

Share this post

Link to post
Share on other sites
well i posted this before, but i think you need something like [url=""]this[/url] for directx.

Share this post

Link to post
Share on other sites

A few questions:
1) [quote name='C0lumbo' timestamp='1355413236' post='5010249']
Talking about the bleeding problem - I don't think this is really a floating point accuracy issue, it's a texture sampling issue.
[/quote] How can I sample my textures pixel accurately? I mean, one pixel of black should be enough to blow up to any resolution and fill the background with black, with no bleeding at all, am I correct? Or am I missing something?

2) [quote name='C0lumbo' timestamp='1355413236' post='5010249']
This means you're going to be bilinear filtering on your textures.
[/quote] What is bilinear filtering?

3) [quote name='C0lumbo' timestamp='1355413236' post='5010249']
With texture atlases you need to add a border around each of images so that the bilinear filtering doesn't accidentally pull in any adjacent images.
[/quote] How many pixels thick should the border be, and in what color should the border be?

4) [quote name='C0lumbo' timestamp='1355413236' post='5010249']
An alternative is to modify your UVs so that the UV rectangle is squeezed inwards by half a texel on all sides
[/quote] What does "Modify the UV mean?"

As a side note, I have switched over to using SFML so that rendering can be simple while I master other programming and game design concepts, but I noticed that if I place something at, for example, location (0, 1000) then it goes outside my screen if I have, say, a (800, 600) resolution. Is there any way in SFML to have the coordinates scale with the window, i.e. a y-coord of 1000 (or whatever, I really don't care) would always be just near the bottom of the screen just as it would in 1920x1080?

Thanks for all your help.

Share this post

Link to post
Share on other sites
[quote name='KingofNoobs' timestamp='1355577116' post='5010930']
What is bilinear filtering?
That alone makes me not want to help you. You do own a computer [url=""]connected to the Internet[/url], don't you?

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
    • Total Posts
  • 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. 
      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!
    • 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.
  • Popular Now