New answers tagged graphics
This should help: From MSDN: How to: Restore Default Project Templates: If you accidentally delete the default project templates that are included with Visual Studio, you can use this procedure to restore them without reinstalling Visual Studio. To restore the default project templates In the command prompt, navigate to the location of devenv.exe. ...
If you can only afford to have one set of sprites drawn (i.e. your artist time/effort is limited) then get them to do the largest resolution. It's far easier to make hi-res sprites look okay when scaled down than it is to make low-res sprites look okay when scaling up. Neither approach is better than having sets of sprites tailored for your target ...
Vector images are useful since they would work with any resolution, and you can even use them directly in the game, letting OpenGL/DirectX rasterize it only when they are rendered to the frame buffer. But since you specifically mentioned pixel art it doesn't sound like you would get the right look with vector graphics, in that case you want to be careful ...
Pixel art generally responds extremely bad to any scaling. Just a small size adjustment will make pixel art appear either blurry or distorted, depending on what scaling algorithm your engine uses. For that reason it is important to make sure that the graphics are designed in exactly the resolution in which they appear in the finished game. Here is a ...
I found out that when I switched computers I downloaded a more up to date version of Assimp that required me to use the "aiProcess_PreTransformVertices" flag whereas some older versions of Assimp do this already.
Make them the size they would normally be. Don't try to make them big and scale them down later. That way there will be less time loading the images (Not that it's all that long.) Less data stored as well. Make sure that when you are scaling them up to draw them to the screen, you don't use a any sort of filter. Anotherwords... Use no mipmapping. Ie point ...
Depends on what look you're going for. Usually you'd design for your target platform and then scale/rework art assets for secondary platforms. Make it look nice for the largest chunk of your players, essentially.
Calculating the vector that points from a spring at point A = (x0, y0) to a spring at point B = (x1, y1) is simply: v = (x1 - x0, y1 - y0) Assuming no other forces acting on the player, then changing the player's velocity to some scalar multiple of v when they hit spring A would direct them to spring B. If another force like gravity is involved, then, ...
Turns out to have been caused by a lwjgl bug I reported here.
As far as I know, whenever you make a sprite using any spritesheet, that spritesheet will be loaded automatically. So you don't have to load anything.
Top 50 recent answers are included