Elysian Shadows

You should be DAMN fucking good. Not "decent". The industry these days is extremely competitive. Now what will set you apart is a wealth of work to show. You can talk all day long but until you put your money where your mouth is it won't account for much. I know 15 year olds who blow alot ...

It depends.

In win32, BOOL is 4 bytes. It's typedef'd to INT.
In most implementations, compilers choose to implement the C99 "bool" as a 1 byte type.

This leads to many problems if you're not careful with type consistency when copying data. Use one type consistently or define one thusly.

Folks, you really need to be pragmatic about this. The case where you'd code assembly "because it can be fast" is rapidly waning. As a matter of fact its not as easy as simply inserting inline assembly blocks into C code anymore. If you compile against x64 with any modern IDE, you won't ev...

...what the fuck level is THAT?

Look, ya'll are again getting caught up in a X vs Y API dilemma. There's nothing inherent within XNA that would ban you from doing something as terribly simplistic as this, nor would there be anything in D3D that would do this either. What I'm saying is that problems this simple are completely API a...

Yea 2.5D is an emulated 3D space. Usually they have limited cameras that simply pan along a plane and perspective is just handled with linear scaling of world elements. Anywho, I've seen MANY a *VERY* ambitious project with XNA (including and far beyond raycasters). So I would not discount XNA at al...

Your load function is not returning the texture handle. It's returning true or false. You're then assigning this value to "menuTextures[x]" and attempting to bind either true or false as a texture object. :]

GL_BGR_EXT

No, its because for practical purposes it's significantly unlikely that two discrete calculations that should theoretically yield the exact same value will ever happen. Very significantly unlikely. You do this in science. If you've taken chem lab or physics lab or what have you, you'll be expected t...

You've more than likely got both problems running at once, which is just EXCELLENT for you. The T-junction problem is pretty well documented and will definitely require you to sit down and re-think your approach to rendering your world. It's definitely more than I'm willing to go into here. The text...

You must define operator== for non-native types. You want to define the binary operator== for const types since you're using constant iterators. Observe const correctness, lest ye compiler become upset: inline float X() const { return _x; } inline float Y() const { return _y; } Define binary operato...

You need to first determine what the issue really is. It VERY much looks like a T-junction issue.

Disable texturing and see if the issue still appears.

You need to take bnpph's advice and make the geometry overlap slightly. You've got here a pretty classical problem w/ co-linear geometry becoming victim of floating point roundoff error due to the non-linearity of perspective projections. This is evidenced by the fact that your clear color (red) is ...

Oh come now, he's only 14....he's got several prime douchebag years ahead of him.

...we're only scratching the surface

Trade contact info with me and I'll resolve the problem with you.