Borden Haelven wrote...
Cool. I always thought NWN could only handle square textures. Or do I leave half blank or possibly double them up?
You can double them, stack them, whatever you wish to do.
Take a look at any of the xxx_detail textures used in the various sets for an easy example. These are the textures used to map onto say the vegetable bins in markets etc... you can pick what part of the texture it mapped to the specifc faces on the objects etc.
Keeps total file count down that way, and can save a bit of space depending on how the textures are mapped.
Word of warning though, 2048 textures are HUGE, and not really all that useful in NWN.
The main thing to remember is that the size needs to be a power of 2, on each side. anything below 256 is typically so low quality as to not be much use, anything above 1024 is typically a waste of space, but can add more detail. Textures that sized, have to be loaded, them mapped (all textures do) so using a huge texture, for a small section of a single object/building whatever, is a big waste of ram for nwn. Remember, you can push the limits, but only by reducing total area sizes, creature counts, and total number of placeables in a given area. Otherwise, NWN just bogs down. NWN can only use 64 meg ram and can only use that much if you specify that in nwnplayer.ini under the game options (Max Memory Usage=64) Setting higher numbers doesn't help, as the engine will go back to defaults instead which is lower than the 64.
NWN Aurora is OLD, the technology has far surpased what was coded for. We can push the limits to some extent, but only sooo far, then it just crashes or becomes unplayable due to lag.
