Elysian Shadows

There isn't a course in college that will teach you how to make games. However, almost every single one will arm you with tools necessary to tackle the problems inherent in game development. That said, I would try to challenge yourself. I would say, sure...make Pong, or some simple game. Here you wi...

Definitely pay attention in Data Structures/Algorithms. It will form the basis of virtually every single thing you do in game development. Your knowledge of language is of secondary importance. Making a "whole game" now is fairly complex to the point that you might want to specialize in so...

SFML is likely grabbing them directly from system calls. In this case they will always be screen relative. EX: In Win32, you might use "GetCursorPos", it does not take a HWND (window handle) parameter. How would it know to which window the cursor is relative to?? Point being, except global...

FAR more liberal.

2 years is not very long.

Where do you work and what is your job title?

Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.

Who in the HELL ever said that?!

Poor render state or bad calls between a begin/end pair. Check for errors thrown by the GL. You don't know that its not rendering, but you do know it's not doing what you want. There's a big difference. Deprecation is possible, but I've yet to see a driver enforce it...

What is it you're trying to do?

Help us help you. I just see a picture of a red square on a black canvas. For all I know you want tons of red squares everywhere, maybe one big red square covering the whole screen, perhaps just a black screen.

No clue what it is you're doing here.

Your state management looks absolutely atrocious. You have LoadIdentity's and PushMatrix's all over the place and in non-sensical places. I have no idea what you're trying to do, what it's supposed to do, or what other varieties of jacked up states you've got going on there from other places. .....b...

Your texture selection is frame limited, if the primitive rendering isn't limited by that EXACT same limiter, then you can run into this problem. Where your primitives are coming down the pipeline willy nilly, but your texture selection is inconsistently limited. From what I can see, your limiter lo...

Game programming is full of very complex problems in every specialization. It might help if you specialize in an area that you're genuinely interested in. When you run into road blocks (which you will), your interest should be enough to keep you going. If you're not interested, you're more likely to...

^ this code is bad. :]

Try not to think of it as "I need a position buffer, a normal buffer, a texture buffer, etc..." Back in the day we had static "vertex formats", which helps sortof bridge the gap. It used to be that you could not specify custom vertex formats. Now that you can, it's important to r...

I'm not sure how OpenTK is organized, but it looks like this SHOULDN'T work. Essentially with a simple C implementation, the buffers are never bound at the SAME time. This is required for rendering. Because what would happen here is that the texture buffer would kick the vertex buffer out. You need ...

Did you just take bits and pieces from the tutorial they gave you so that you wouldn't have to deal w/ interleaved arrays? The code above is pretty incomplete. Remember that when you bind an object as ElementArrayBuffer, it remains current until kicked out by binding a different handle to ElementArr...