1D Texture Coordinate Problem

- Some hardware/drivers can''t handle textures that don''t have power-of-two dimensions. These hardware would - hypothetically, I''ve not actually used non-pow2 textures on such hardware - either fail texture creation (most probably) or do bogus texturing.

- Some hardware/drivers support only square textures. Again, on such hardware, you''ll either get failure or bogus texturing.

- You can check for support of pow2 textures and square textures using the caps (don''t remember the exactcaps bits, though)

- I think this doesn''t apply here, but why don''t you try biasing your u''s a little?.

Sorry if it wasn''t much help

Muhammad Haggag

Oh wow, cool. Thanks a lot, I guess I''ll have to manipulate the textures a bit

Okay, been testing out different stuff for about 4 days now since I''ve gotten this problem. More testing today with square textures and different pow-2 sizes but it''s doing something weird. I can''t figure out whether it''s the texture loading that''s being goofy or the the drawprimitive not using the texture coordinates right. I use D3DXCreateTextureFromFileEx with 1 filter level and 0 mipmaps but I don''t see how the loading function would have much of a problem with all of this...
It looks something like this right now:



The problem is that the computer doesn''t seem to be recognizing 0,0 nor 1,0 uv coordinates. The texture itself is a threshold grayscale from dark to light. Has anyone encountered something like this before with texturing problems? The texture loads fine, that''s for sure, lol. Thanks!