• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

font rendering

6 posts in this topic



I have a few questions regarding OpenGL font rendering. But to generalize it:

1. What's the current state of art regarding font rendering in OpenGL?


I have many sub-questions as well as many own ideas and requirements, but I would like to hear how you do it and what the advantages/disadvantages are.


2. Are you using textured quads, tesselated outlines, maybe distance fields or something entirely different?

3. Can you scale your text freely or are you limited to a (few) fixed size fonts?

4. How cross platform is it?

5. Does your way of rendering fonts support vertex buffers or are you using the fixed function pipeline?

6. What about internationalization, do you support any language as long as the font contains the required characters or do you only support a fixed set of languages?

7. How hard was it to implement/build your solution?



For my own project I guess I would use tesselated outline fonts. Because of their scalability, the potential to use the vertex shader to transform them and because you can use the same anti-aliasing as you do for your other geometry.

I already started by building a small tool that creates a mesh for each glyph in a font. The tool will be used offline in the build step and the meshes shipped with the game, since I believe just loading a few thousand meshes is faster than tesselating them on the users computer. It's also much more deterministic, since I won't have to rely on the glu tessellator installed on the users computer and can test for exact output.

Now I do plan on using SIL Graphite to generate the positions for each glyph, that way I do have the same support for languages on all platforms that graphite supports. Even minority scripts in case I would really like to translate my project into some language that the operating system is not supporting.

That's my plan so far. Maybe when I have time I will actually put it in action.



Share this post

Link to post
Share on other sites

1. No idea

2. Textured quads. It's fast and simple, yet surprisingly effective. Mipmapping can handle font scaling better than you'd think--better than actual geometry without antialiasing--and it's very very fast.

3. Any font.

4. The fonts are loaded and rendered using SDL_ttf, so it is completely cross-platform.

5. Actually, my font module really only serves to create the texture. What is done with it is up to you.

6. Anything SDL_ttf can do.

7. Easy. Ridiculously easy.


I personally recommend against anything too complicated (e.g. tessellated or mesh-based fonts. Maybe there's some special applications (e.g. flying through a piece of text for an effect) but really, rasterized fonts are fast, easy, robust, portable, and easy-to-implement.


Share this post

Link to post
Share on other sites

I've had good results using glfont. It is fairly simple to integrate into a project and is fast. I've used it on Windows and Linux, but see no reason why it won't work on OS X. The only causion is that the routine for reading the font file requires a slight modification on 64-bit machines (the use of sizeof causes a problem becuase the format of the file is based on 32-bit data types).


Share this post

Link to post
Share on other sites

1. there's a state-of-the-art font rendering ?

2. textured quads

3. any - but my personal preference is to keep things crisp and scale so that texels are exactly stretched or smashed into a concise number of screen pixels

4. as much as OpenGL itself is

5. I use display lists to render character strings, where I can basically just glCallList(string) after applying appropriate matrix transforms to put it where I want

6. I built my font system around a simple texture packing/quantization setup that I devised so I could store font textures inside my executables by including a header. I wrote a tool which will take any sized font texture and spit out a header file to include in my projects that contains a packed array of texels and various font character / texture dimensions needed by the font rendering system itself.

7. It was easy, but it was a slow evolution that occurred during work on different projects over the course of a few years.


On a side note, as far as game development is concerned, I am particularly attentive to how much CPU/GPU text output consumes. I feel that it is even overkill to use quads (two triangles) per character, because I'd rather be using those triangles on the game scene itself. Ideally some sort of precomputation setup that generates a single texture or vertex buffer for use over multiple frames for each string to be rendered would be the fastest, so long as the text on the screen isn't constantly changing every frame, because with most font-rendering setups it may as well be (including mine) what with the redundant re-submission of text to be rendered being sent to the GPU every frame.


Share this post

Link to post
Share on other sites

Thanks for all of your replies.


Well my idea with the tesselated fonts started when I was imagining a game where test was more important than usual. Not walls of text like in some RPGs, but where you have small parts of text that are important.

Maybe I will try to write a small benchmark some day, to find out how much it does cost. Since tesselated glyphs have between a few and a few hundred glyphs I imagine it would be difficult for languages that have complex glyphs to stay in budget.


Since most of you are using some preprocessing stage, I do have some more questions:

8. Do you just include all of the glyphs in a font or do you use only a subset?

9. How do you handle stuff like ligatures and other advanced features? What about Right-to-left? Do you handle all of that stuff yourself, do you let the OS do it's thing or do you just not support it?

10. How open is your system, e.g. if your game supports modding, are mod makers limited to the language and font you selected or is it possible to choose another font and write text in languages your own game does not nativly support?


Share this post

Link to post
Share on other sites

My in-progress system uses Freetype to load/render the font glyphs at arbitrary sizes to a set of texture atlases. When rendering a string, I build a vertex buffer using textured quads for each glyph, then draw that vertex buffer.


As for glyph management, when rendering each character:

  • Do hash lookup to find if the character's glyph is already present in one of the texture atlases for the font.
  • If it's present and the size of the glyph in the texture is big enough for the currently rendered font size, the renderer uses the existing glyph image to texture a properly scaled and aligned quad.
  • If the required glyph is not present, the renderer picks an available spot in a texture atlas and renders the glyph to that region of the texture using the largest size that can fit in one of the texture atlas's slots. The glyph texture can then be used as described above.
  • Texture atlases are stored as 8x8 (because 64 characters is mostly enough for ASCII text) grids where each grid slot is a power of two sized square region of the texture. For a glyph whose bounding box is at most 16x16 pixels, it will be placed in a texture atlas with 8x8 = 64 slots of size 16x16. When an atlas is full or different size is necessary, a new one is created. The renderer has to make sure to split up strings that require different atlases into different rendering calls. In practice, this doesn't happen very much for most scripts.
  • Kerning information for adjacent character pairs is retrieved directly from the freetype font during rendering.

The result of this system is that only the glyphs (at the proper size) that are actually needed are cached from the font in the texture atlases.


Share this post

Link to post
Share on other sites

Textured quads with distance fields. This works very well for both scaling up and down, and you can nicely antialias at any scale (plus, special effects if you want). Shaders are well-documented in several papers and readily available with liberal licenses, so implementing it is not all that hard. Performance is almost identical to using normal textured quads on modern GPUs.

Tesselated outlines are forbidding if you need to render more than a few dozen characters in real time.


Signed distance fields is a great approach if you want an effective way of rendering multi-scale fonts, including bold, italic, light etc. all from the same font texture. A good video of some of the results can be found here: http://www.youtube.com/watch?v=CGZRHJvJYIg, and Bitsquid have very kindly made a generator from font file available here: http://bitsquid.blogspot.com/2010/04/distance-field-based-rendering-of.html


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  
Followers 0

  • Similar Content

    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
    • By Tchom
      Hey devs!
      I've been working on a OpenGL ES 2.0 android engine and I have begun implementing some simple (point) lighting. I had something fairly simple working, so I tried to get fancy and added color-tinting light. And it works great... with only one or two lights. Any more than that, the application drops about 15 frames per light added (my ideal is at least 4 or 5). I know implementing lighting is expensive, I just didn't think it was that expensive. I'm fairly new to the world of OpenGL and GLSL, so there is a good chance I've written some crappy shader code. If anyone had any feedback or tips on how I can optimize this code, please let me know.
      Vertex Shader
      uniform mat4 u_MVPMatrix; uniform mat4 u_MVMatrix; attribute vec4 a_Position; attribute vec3 a_Normal; attribute vec2 a_TexCoordinate; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { v_Position = vec3(u_MVMatrix * a_Position); v_TexCoordinate = a_TexCoordinate; v_Normal = vec3(u_MVMatrix * vec4(a_Normal, 0.0)); gl_Position = u_MVPMatrix * a_Position; } Fragment Shader
      precision mediump float; uniform vec4 u_LightPos["+numLights+"]; uniform vec4 u_LightColours["+numLights+"]; uniform float u_LightPower["+numLights+"]; uniform sampler2D u_Texture; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { gl_FragColor = (texture2D(u_Texture, v_TexCoordinate)); float diffuse = 0.0; vec4 colourSum = vec4(1.0); for (int i = 0; i < "+numLights+"; i++) { vec3 toPointLight = vec3(u_LightPos[i]); float distance = length(toPointLight - v_Position); vec3 lightVector = normalize(toPointLight - v_Position); float diffuseDiff = 0.0; // The diffuse difference contributed from current light diffuseDiff = max(dot(v_Normal, lightVector), 0.0); diffuseDiff = diffuseDiff * (1.0 / (1.0 + ((1.0-u_LightPower[i])* distance * distance))); //Determine attenuatio diffuse += diffuseDiff; gl_FragColor.rgb *= vec3(1.0) / ((vec3(1.0) + ((vec3(1.0) - vec3(u_LightColours[i]))*diffuseDiff))); //The expensive part } diffuse += 0.1; //Add ambient light gl_FragColor.rgb *= diffuse; } Am I making any rookie mistakes? Or am I just being unrealistic about what I can do? Thanks in advance
    • By yahiko00
      Not sure to post at the right place, if not, please forgive me...
      For a game project I am working on, I would like to implement a 2D starfield as a background.
      I do not want to deal with static tiles, since I plan to slowly animate the starfield. So, I am trying to figure out how to generate a random starfield for the entire map.
      I feel that using a uniform distribution for the stars will not do the trick. Instead I would like something similar to the screenshot below, taken from the game Star Wars: Empire At War (all credits to Lucasfilm, Disney, and so on...).

      Is there someone who could have an idea of a distribution which could result in such a starfield?
      Any insight would be appreciated
    • By afraidofdark
      I have just noticed that, in quake 3 and half - life, dynamic models are effected from light map. For example in dark areas, gun that player holds seems darker. How did they achieve this effect ? I can use image based lighting techniques however (Like placing an environment probe and using it for reflections and ambient lighting), this tech wasn't used in games back then, so there must be a simpler method to do this.
      Here is a link that shows how modern engines does it. Indirect Lighting Cache It would be nice if you know a paper that explains this technique. Can I apply this to quake 3' s light map generator and bsp format ?
  • Popular Now