Elysian Shadows

Blender scripts are such a pain. Much better than making a modeler, though.

Star with C.

Move onto C++ when you feel comfortable.

You can run code::blocks off a flash drive - I've done it and it works great. This is what I recommend.

If you don't use an IDE you'll have to mess with makefiles which can be a pain.

3 options:
1. hardcode the directory the correct directory into your game.
2. make a config file that contains the correct directory and load it when your level editor starts. This is probably the best option.
3. use a "save-as" dialog box.

Is your texture part of a texture atlas?
You might be seeing the edges of other surrounding textures.
Try reducing the bounding box of your texture coordinates.

I've changed the sizeof(Tile**)'s to sizeof(Tile*) and the sizeof(Tile*) (from before) to sizeof(Tile). Its still crashing at the same point, this time instead of the whole mess of messages, its giving me the "Segmentation Fault". Hm, that is strange. Are you sure your malloc calls are re...

First off, change: DynamicTileArray(); DynamicTileArray(int width, int height); To DynamicTileArray(int width = 10, int height = 10); This is wrong: (Tile*)malloc(sizeof(Tile*)*10); sizeof(Tile*) is the size of a pointer - which will be 4 bytes on x86. You want sizeof(Tile) instead. Also, sizeof(Til...

Try making the size of the cubes slightly larger so they overlap.

x = turret.x + cos(turret.direction) * turret.length; y = turret.y + sin(turret.direction) * turret.length; Something like that for a single barrel. For multiple barrels, you can either: A. use the above code twice - one perpendicular, and one going outwards B. Use the above code but add a value to...

Here is basically what I was trying to say (code wise). //This is a little pseudo.// class Entity { public: virtual void Attack(); }; class Player : public Entity { public: void Attack(); }; void Player::Attack() { std::cout<<"Attack the goblin!"<<std::endl; } class Goblin : public Entity...

Well, one could actually have all the autotile calculations be done when you change tiles rather than when you render them. That would not only save CPU time, it would also make your life at least a little easier. Yeah, you only need to update the 8 adjacent tiles of the one that has been changed.

I use CRTP all the time - it is very handy.

I prefer it over dynamic inheritance.

Anyone care to discuss? http://www.youtube.com/watch?v=p6FSKSdhQgY I like to think of OO as just being a wrapper around procedural calls and data, which in reality it is. For modern video games, it is almost a necessity to use some sort of OO - whether it uses functionality built-into the language ...

I already have grid snapping working just fine along with multiple other things like multiple tile selection etc. Oh, I guess I saw that from an outdated video - the new one looks good! The problem is the widget doesn't scroll and it offsets everything. Why not translate the GL matrix to match the ...

To check if snapped to grid just use modulo, and split up movements into numbers divisible by grid number.

You are unable to move outside the map in some places because I'm assuming that you are accessing out of bounds data.