# OpenGL NeHe FreeTypeFont tutorial - blank screen

## Recommended Posts

I'm trying to make the NeHe freetypefont tutorial to work, but I get a blank screen for some reason...

What I did:
- got precompiled Windows binaries of freetype (freetype-2.3.5-1-bin)
- made a project in Code::Blocks (SDL+OpenGL+FreeType lib included)
- downloaded the source code from http://nehe.gamedev.net/tutorial/freetype_fonts_in_opengl/24001/ (the Linux/SDL Code For This Lesson. ( Conversion by Aaron Graves) version) and I have not forgotten about the font either :)

So, I have built it and run and... I'm getting a blank screen. I added a standard "OpenGL triangle code" and it is displayed properly, so I assume OpenGl + SDL works as it should. I got no errors of any kind.

I don't know how to bite it. Is it because the tutorial is broken? Or I downloaded a broken version of it? Or I got a wrong/broken/incompatible version of FT library? Or something else?

Does anyone got this tutorial working? Edited by Acharis

##### Share on other sites

OK, maybe I should ask another question. Do you know of any working FreeTypeFont OpenGL rendering tutorial?

##### Share on other sites

First of all i never downloaded the code, i just read the tutorial (and understood it), and rewrote it myself, and it did work with me. And i also did it on windows.

And the Freetype library is correct, this tutorial uses freetype 2.

You say you downloaded the FreeType windows binaries, and the Linux/SDL code? It doesn't make sense.

If you have windows, then download the windows code, if you have linux, i believe the windows freetype binaries won't help.

##### Share on other sites

Windows

But the sources were for SDL, it's supposed to run on absolutelly everything...

Anyway, I can't use the VC++ source codes because these use glaux, which is not included in code::blocks.

##### Share on other sites

http://nehe.gamedev.net/tutorial/lesson_06_texturing_update/47002/

EDIT: Or if you want to use glaux, download the files here http://mycodelog.com/2010/05/15/gllibs/, place the files in their correct folders (you only need the glaux.h and glaux.lib), and see if the program works.

And keep in mind that this tutorial is deprecated in various ways.

Display lists, GL_LUMINANCE_ALPHA, drawing using glBegin()...glEnd(), glaux, etc are all deprecated in modern OpenGL (along with the way the freetype headera are included).

Also, i just downloaded the VC++ code, compiled it and it works for me EXCEPT you must change the following bit:



for(const char *c=text;*c;c++) {

to



const char *c=text;

for(;*c;c++) {

or an error will occur.

See if it works, and let me know.

##### Share on other sites

OK, maybe something easier first. Where can I get prebuild libraries of FreeType for Windows? Includes+lib+dlls, all that are guaranteed to be compatible and work together (doeas not matter which version, as long as all of these files are compatible).

I noticed the one I was using is kind of strange and does not look like the others (it has freetype2/freetype directory structure instead of freetype like all tutorials require, I manually changed it but... it's still suspicious, so maybe I just have some broken version of TTF library).

I tried the package from the official freetype site (http://download.savannah.gnu.org/releases/freetype/) but it has no prebuild libraries (and I definitely want to avoid building these myself now, I would then be completely in blind at which step I made a mistake if it does not work).

##### Share on other sites

Unzip the files, and you will have the include, lib, and dll files

You just need the freetype6.dll and freetype.lib.

The include file directory has the following structure

copy that same structure to your IDE include folder, but remove the 'freetype2' folder in between (it should become ...include\freetype\<the freetype headers>)

then link your project with the freetype.lib, and run it. It should work (i hope).

If you have doubts, or it doesn't work then post again.

## Create an account

Register a new account

• ### Forum Statistics

• Total Topics
628366
• Total Posts
2982274
• ### Similar Content

• 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?

• 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.

• 10
• 9
• 13
• 24
• 11