When you display a power of 2 texture on android, you get a blank texture if the dimemsions are not equal. For example: 256 x 128. I’m just letting you know I’ll be fixing that in the days to come.
Can you explain your issue a bit more? Android already supports textures with different pow 2 dimensions for height and width. I use them in my apps without any issues.
What format are the images in (png, jpg) ?
Do the images have an alpha channel?
Firstly, this is I’m not the first person to report this, older threads report the same problem.
It happens whether I use JPG or PNG.
The alpha channel is not a problem when I use images with equal height and width.
In short, I’m using Nexus 7 1st Gen. And the textures go black when used in this manner.
All I can tell you is that I already use images with the following image resolutions with no issues:
64x512
256x32
128x256
128x16
These are all in my current app as png with an alpha channel.
There may indeed be an issue, but it is not a generic issue with just having different sized height and width. I’m just trying to figure out what is different about your images than what I am currently using without any issues.
I think I remember a long time ago having an issue with this, but that was quite a while ago.
1 Like
It’s probably a limitation of the android device you are using…
Here is one of the images:
I think this has to do with the shaders and my device. I just have a hunch. I’m not using any shaders or any special tricks though.
What a bummer! I’ll have to still solve this problem though.
The image displays fine on my device. No special shaders either. I threw the texture on a Picture quad and it just shows up fine.
@iwgeric Don’t worry, it just another day in the android-coding world. I’ll just test the whole pipeline and report back any findings.
@Pixelapp said: I'm just letting you know I'll be fixing that in the days to come.
What??? How can you possibly know that you will be able to fix it? Usually people just say, “I’ll dig around a bit and see what I can do”.
EDIT: Its good to be keen but… wat?
1 Like
@javagame “I’m just letting you know I’ll be fixing that in the days to come.” It’s just means, please don’t duplicate the efforts. Buddy. What’s the outrage about??
@Pixelapp said: @javagame "I’m just letting you know I’ll be fixing that in the days to come." It's just means, please don't duplicate the efforts. Buddy. What's the outrage about??
No outrage. He like many of us thought it was kind of funny. I imagined you going to the doors of the hardware vendors and threatening them with bodily harm. Made me smile.
In general, you cannot and should not “tag” things as “I’m going to do it.”. In an open source project, never try discourage someone who might do it better or faster. If you do it faster then no biggy. Giving us a heads up that you are looking at it is fine… but trying to cut off all other attempts is poor open source etiquette.
@Pixelapp said: @javagame "I’m just letting you know I’ll be fixing that in the days to come." It's just means, please don't duplicate the efforts. Buddy. What's the outrage about??
Sorry If I seemed like I was trying to flame you, pspeed hit the nail on the head 
@pspeed “threatening them with bodily harm” Hey, no pain no gain.
“I’m just letting you know I’ll be fixing that in the days to come.” Also means, is there any maintainer I should contact?!
“but trying to cut off all other attempts is poor open source etiquette.” Go figure, I learn something everyday. 
@javagame No hard feelings.
@Pixelapp said: @pspeed "threatening them with bodily harm" Hey, no pain no gain.“I’m just letting you know I’ll be fixing that in the days to come.” Also means, is there any maintainer I should contact?!
“but trying to cut off all other attempts is poor open source etiquette.” Go figure, I learn something everyday.
Heheh.
In general, it’s probably better to say what you actually mean. So if you meant “I’m going to look into this. If someone has pointers or is maintaining this code then let me know” then that’s what you should say.
Language and cultural differences will often erase any subtlety anyway… so better just to say what you mean.
1 Like
This is a hardware problem!
When I use .dds images instead of .jpg, it works correctly.
Great!!!
I doubt that its a hardware problem. DDS and JPG are just containers, they don’t define the image data or how it is decoded by the system.