Sign in to follow this  

OpenGL Quality of a sprite based game

Recommended Posts

Hey guys. I'm almost done writing a framework for a game. Making a 2D game, I've read some material on the web and realized two options I have are making it sprite based or doing it in 2D projection in OpenGL, since I'm targeting windows, android and iOS. I've decided to go with sprites for the initial version but I'm a bit worried of the graphics quality that can be achieved with sprites. I'm sure there are nice examples of sprite games that look awesome, but there's a buzz in my mind about it. "Sure you can achieve awesome looks with sprites" you would say, but my definition of awesome might differ from yours. I picked sprites over OpenGL because of animation simplicity and actually simplicity overall. I want to start small and not get caught in something I can't get out of, since I'm doing the whole game myself. So... What should I expect from sprites regarding quality(looks)?



Share this post

Link to post
Share on other sites

A: Yes it can look good, and second, B: what exactly are you trying to make? and C: what other alternative are you thinking about? I'm asking so we can compare for your particular situation,


The quality depends, of course, on drawing skills. But also about the chosen style and consistency of the graphical content. When chosing sprites, don't expect to make photo-realistic graphics. For cartoonish graphics though, it can work out really well. In facts, making your world, characters and animations look cartoonish, is easier to achieve with sprites. Because the shapes are more curvy / organic compared with polygon objects, and you have more freedom with the animations. Not that its impossible to do with 3D, but that requires high skills.


Speaking of skills, when chosing 3D, the overall difficulty to make things look *good* is higher. So unless you have plenty of time to create a "next-gen" engine + the artists that can make the content, a 3D engine will quickly look outdated when people compare it to Crysis, Unreal, or whatever we got. This is less of a problem when going for 2D. At least... if you can pick a specific, consistent style. And since you also aim for mobile devices, you can't make too complex 3D stuff anyway.



As for the technical aspect to make things look good, consider lighting as one of the most important factors. In 3D, there are a lot of options to simulate somewhat realistic lighting. Shadowmaps, geometric shapes, normal/specular mapping, (baked) GI, and so on. With sprites, this is a bit harder to achieve because your scene is literally flat, and thus lacking information you would need for proper lighting. Although a cartoonish style may not need realistic "correct" lighting, you still may need some tricks to get it look cool instead of flat and dull.


This is probably the reason why platform games are often semi-3D. Using a mixture of 3D shapes and sprites. Don't forget you can still use OpenGL for a 2D looking game. But as said, making a 3D engine requires more work in general. So if you don't really need it...




Share this post

Link to post
Share on other sites

There are games out there that have very high definition sprites, take a look at the sprites from Skullgirls and Shank for example.




Both games use 2D sprites

Share this post

Link to post
Share on other sites

@Rick: Hey there. Well, alternatives I was considering was OpenGL and just making a 2D projection from above. It's a tower defense game. Indeed it should have a cartoonish look, not realistic.


@6B!: Those two look awesome! But as Rick said, it depends on drawing skills alot.

Share this post

Link to post
Share on other sites

A Tower Defense game. I would just make it 2D. Because you will likely reach your goal faster (= making the game), it likely runs better on mobile devices, and most important, drawing topview walking characters or towers likely looks better than using (low poly) 3D models. Just compare old RTS games (Command & Conquer, ...). I found the drawed sprite ones look better than their 3D counterparts. Because sprites can show any complex drawing, while with low-poly models, you are stuck to more simplistic shapes. Same with lighting & animations.


I don't know what you are using right now, but OpenGL can draw transparent quads (sprites) just as well. Neither are you forced to use all kinds of complex shaders or lights. In other words, with OpenGL, you can do what any 2D engine can do as well. So if you like the way how GL works, you can still decide to go for GL of course. And since GL works on those mobile devices as well, its not such a crazy choice. 

Share this post

Link to post
Share on other sites

Yeah I've worked with OpenGL ES on an iOS project at work, actually. So I would make a quad, apply sprite texture, and perhaps do post effects using shaders?


I'm using SFML at the moment. It's more of a make a game and learn than anything else. I've tried to detach all the drawing code from game code, so If i choose to change the graphics engine, I just have to write implementations for drawing classes etc.


I will probably stick with sprites, just would like to consider other options.

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