This topic is 3627 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

Recommended Posts

I decided to start trying to learn OpenGL a couplt of days ago, and followed the NeHe tutorial, but at lesson 1 I've had problems compiling, my first problem was with GLuax, which after searching here I discovered how to add new libraries to Dev-C++, but now whenever I try compiling, I get a bunch of linker errors, a quick example: [Linker error] undefined reference to glViewport@16' [Linker error] undefined reference to glMatrixMode@4' [Linker error] undefined reference to `glLoadIdentity@0' My initial thought was Dev-C++ was the problem, so I tried compiling with Code::Blocks, and the exact same errors occured, I've searched (not for long I admit as its begining to annoy me) and had no luck as to what the problem is. I'm not a total newby at programming, and I'm guessing I'm missing something from my makefile, but I'm using the auto generated ones from Dev-C++ and Code::Blocks. Also, a quick random question, my normal language is C, and not CPP, is it possible to use OpenGL in C, or only in CPP? (I've not found any guides to C so I highly doubt it). Thanks in advance for any replies. -Aura

Share on other sites
It sounds like the linker isn't finding the OpenGL shared libraries. It's been a while since I've used Dev-C++, but you'll want to double check that Dev-C++ is telling the linker to link properly.

I believe there is a Project Options menu or something, where you can "Add Libraries". Try adding something like -lopengl32 to it.

Also, I know nothing about GLaux except that I believe it is deprecated and no longer used anymore. You might want to double check but I don't believe you should be using it.

OpenGL should work fine with C. I believe it was even designed with C in mind.

Share on other sites
Thanks for that, its solved, apparently glu32 and opengl32 were not linking, I guess I'll use my own makefiles, which is what I'm used to, I just hoped Dev-C++ would make life easier for me. Thanks a lot :)

-Aura

Share on other sites
DevC++ has a package update that downloads all kinds of libraries and it has one to setup openGL files. Go to the package/updates, you can get openGL, and then you can actually build a pre-setup openGL application.

They also have a glaux library as well.

Share on other sites
btw, C and C++ are interchangeable in projects. I would assume DevC++ supports changes since its a decent compiler.

Share on other sites
Quote:
 Original post by dpadam450btw, C and C++ are interchangeable in projects. I would assume DevC++ supports changes since its a decent compiler.

Standard DevC++ bashing / nitpick post: DevC++ is not a compiler, it's an IDE. It's also old (no updates since 2005) and horribly buggy.

Far better to use Code::Blocks (new release version just out), or MS Visual C++.

Share on other sites
Quote:
 Original post by sprite_houndStandard DevC++ bashing / nitpick post: DevC++ is not a compiler, it's an IDE. It's also old (no updates since 2005) and horribly buggy.Far better to use Code::Blocks (new release version just out), or MS Visual C++.

I agree Dev-C++ is buggy, and I know its very old, but at the moment it compiles, which is more than I can say for Code::Blocks, whenever I try and compile with it I get errors, and I'm finding the whole layout more difficult to get to grips with, Dev-C++ is (in my opinion anyhow) better laid out.

I normally use Notepad++ for editing, and Cygwin for compiling, and I'll probably end up switching back to this method as its what I know.

-Aura

Share on other sites
Quote:
 Original post by sprite_houndFar better to use Code::Blocks (new release version just out)...

Oh, excellent! I've been too lazy to get the nightly builds from SVN, so it's great to hear that they've got a new version out.

Share on other sites
Yeah, I've come to realize that I prefer having no IDE, just a good text editor and command-line compiler (invoked through standard makefiles).

I use VIM for my text editor, it takes a little bit to learn, but for C/C++ programming I find that once familiar with it, programming becomes much more efficient.

Share on other sites
Agreed, it also allows portability, as you can save everything you need to a flash drive and compile on other computers (which is what I did in the past), it also means you don't have to get bogged down trawling through options just to add a new library or to update your current libraries, you place them where you want, and add the location to your makefile. First time I saw a makefile I was totally confused, its only since I started developing on PCs and not consoles that I've realised how dependent on them I've become (in a good way of course).

-Aura

• 12
• 10
• 10
• 11
• 18
• Similar Content

• Good Evening,
I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
I am really stucked right now because of the fundamental question:
Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on.
In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
Should I treat those debug objects as entities/components?
For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
Regards,
LifeArtist
• By QQemka
Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
Let's go:
Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
There were several more but i forgot/solved them at time of writing
• By RenanRR
Hi All,
I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
#version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);
So, some doubts:
- Why use it like that?
- Is it okay to manipulate the camera that way?
-in this way, are not the vertex's positions that changes instead of the camera?
- I need to pass MVP to all shaders of object in my scenes ?

What it seems, is that the camera stands still and the scenery that changes...
it's right?

Thank you

• Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

int rgbValue = int(textureSample.w);//4 bytes of data packed as color
// algorithm might not be correct and endianness might need switching.
vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
extractedData /= 255.0f;

• While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
Anyone has any idea .. what should I do?