Truth be told, cutting resolution isn’t usually a huge sacrifice. This is not a 100% rule, see these threads () for more info and tips. If you don’t have a technical director overseeing a project, you suddenly get a mod full of super-high-res beautiful textures (or a huge mod with lots of smaller high-quality textures) but you can only use so many of those before crashing.Īnother thing modders need to watch out for (who don’t have experience with game-specific art) non-square textures can take up as much texture memory as a square texture the size of the longest side of the image, because of the way game engines and graphics cards may process textures. Unfortunately, they also gobble memory like there’s no tomorrow. They give you good quality, transparency channels, and are readable by any decent app under the sun. Initially, developers were using TGAs, as they are generally the basis for most game art. (Usually around 3,500,000 of private memory for the app.) KSP crashes hard when you hit a magic wall of memory utilization. In modding games like KSP, which don’t (yet) have a stable 64-bit build for handling a large number of graphically-heavy additions, you end up killing performance or outright crashing the game (usually the case, with KSP). Every artist wants to make their work look as good as possible, so telling someone to smash their gorgeous 2048×2048 texture down to 512 (or lower) can be met with resistance. This requires hard choices during development, and one of the first places to cut is on texture resolution.

When you’re a game developer creating content for consoles or mobile devices, you have a specific memory budget that you have to maintain. One of the biggest problems modders and their fans run into is the issue of memory management.

Ksp 64 bit mods