zacaj

Go over the points in your grid, calculate distance from center point of circle to that point.  If it's less than the radius of the circle, then do point.z+=(1-distance_away/radius)*height_change to get a gradient

Check out Unity 3D

256MB is a very conservative estimate.  Any recent computer is going to have at least 1GB.  Check out the Steam Hardware survey at http://store.steampowered.com/hwsurvey under VRAM.  99% of people have at least 256MB, 91% have 512MB.  I'm not sure how high resolution textures you're using, but I doubt you'd even get close to the 256.  256MB gives you space for a 8192x8192 texture.  If each tile is 16x16, that gives you enough space for 262144 tiles.  If you've got more than 1000 different tiles loaded at once, you might want to reevaluate what you're doing.    

 

When your video card runs out of space, the driver will just start using the regular system ram as "virtual memory", which I know causes major slowdowns, but I don't have any first hand experience there.  Don't forget though, using it as virtual memory is going to be pretty much the same as you just uploading your textures from RAM each time they're used.  I'd assume you can do a much better job of switching out the textures that are least likely to be used than the graphics card can, if by some strange turn of events that actually happens.

Numbers that big are going to be cut off. The computer can't store them. Because of depth buffer accuracy issues, you should generally never have the far distance be more than a few thousand. I'd recommend you use a smaller unit for your world

If you're using GL2+, just do this:

int getFreeVideoMemory()
{
	int availableKB[4];
#ifdef GL234
	if(GLEW_NVX_gpu_memory_info)
		glGetIntegerv(GL_GPU_MEMORY_INFO_CURRENT_AVAILABLE_VIDMEM_NVX,&availableKB[0]);
	int temp=GLEW_ATI_meminfo;
	if(GLEW_ATI_meminfo)
		glGetIntegerv(GL_TEXTURE_FREE_MEMORY_ATI,availableKB);
	return availableKB[0];
#endif
	return 0;
}

Often I've also seen models that contain multiple meshes

When I was fourteen I spent a year and a half writing my own software renderer from random tidbits of information I found around the internet, a lot of trial and error, and plenty of working out how different math worked on post it notes.  Once you've written a software renderer regular graphics programming is a lot easier to understand.

Did you note the i--?

Try using

 

delete zombie[i];

zombie.clear( zombie.begin() + i-- );

If you're having problems understanding where stuff is actually used, your best bet is to actually try to program something real and see where they end up getting used.  That said, I'm up for answering some questions.  Feel free to PM/email/tweet/whatever me.

http://realtimecollisiondetection.net/blog/?p=86

The idea is that you shouldn't have a second pointer referencing the same data. Another function could save unique_ptr.get(), just like they could just save a copy of a plain pointer, but having a unique_ptr makes it quite obvious that they shouldn't do that.

4. In this case shared_ptr would be a better bet. However, in general you should have some policy for each class regarding what 'rights' they have regarding the pointer you give them. If you're giving it to another class you should know whether that class is ever going to delete it or anything, and with any of your own classes that will be accessed by another person's code you should also make sure they know if you're going to be doing anything with their pointers. Generally I try to always have a policy regarding any place that a pointer is in my code about who 'owns' the pointer; whether it's the class that contains (say) the array the pointer is in, the function that created the pointer and added it to the array, etc.

1. You don't have to delete it
3. because then some other function can't get a copy of your pointer and then have an invalid pointer after your class is destructed

You can save a lot of time once you realize that the order of the bullets in memory doesn't matter. When bullet is deleted, memcpy the last bullet in the list to the deleted bullet's place, that way all the active bullets will be first and you can bust add a new one to the end

~ is a tilde