More DIF goodness :)

#1 I think they need to be 2,4,8,16,32,64,128,256,512,1024,etc... Dimentions.

-Jeff

#2 Oh! So you can't use anything other than those dimensions?

That blows. Why is that?

#3 POwers of 2 are easy to proccess. So they put that as a restriction on the texture.

AAAAHHHHHH so wonderful. LOL

Matt

#4 It's inconvieniant, but it's easy enough to work around. Just slap your 192x64 onto a 256x64 image. To save texture memory, you can fill the extra space with images for other objects as well(unless it's tiled or a sprite).

-Jeff

#5 *Giant stream of profanities @#$!%@^&$@&#(@*&(#&@^$&@%#^@!%^&#@!!!!!*

We can change the code though can't we?

cause 512x512 textures don't work properly either. They get lines through them.

#6 You can change the code.

Not sure what kind of lines are going through the images. What format are they? Does your card support 512?

EDIT: My Stupidity

-Jeff

#7 This is already on my todo list...give me a week or so.

#8 PNG format and being used for the terrain....

Holdon.


Every 512x512 image I've used always gets these interlaced lines through them.

#9 And I'm using a Geforce 3 ti200 64 meg so it better support 512 x512 :P

#10 Someone should point out the power of 2 requirement is mostly a nod to voodoo cards. If you aren't supporting them, you can hack this restriction out of the engine without costing yourself anything.

#11 Terrain textures MUST be 256x256 no bigger, no smaller unless you modify the engine code.

#12 that's what I thought.

Thanks Donavan

#13 one of the problems is the Terrain engine barfs on shear vertical cliffs like that. That is the real culprit here.

#14 No, the banding is definately caused by 512x textures.

#15 yeah its definitely the 512 textures causing the problem. Clifss just cause the texture to stretch funny.

#16 use 256 by 256 for the terrain images