forums.ps2dev.org

[ruspa]

hello, I need some hints with my code, as I got a program that display two textures (two square polygons [3*2]) one with a clock display and one with the pointer. Apart that I still can't have the transparency out of the png alpha channel (this will be next in line), it happens that first texture is rendered correctly, the second appears stretched, messed up, and the code used to display it is the same of the other. What can it be? The two pngs are the same, I'm trying to load the same png one above the other for debugging ease (anyway the topmost one, the pointer, rotates as you move the analog stick, so one can see what there's behind).

here are the code portions:

[chp]

Do you flush the cpu caches after swizzling the textures? Otherwise the last texture might still be in the data cache since GU operates on uncached memory when it's writing to the display list.
_________________
GE Dominator

[ruspa]

you mean I have to put a

sceKernelDcacheWritebackInvalidateAll();

between the two

[ruspa]

:( same result (If I got what you meant, at least)

If can help, I reversed and adapted the neheport lesson n°5 (the solid, textured cube), I used just a face and rotate it with a texture on it, then another single textured polygon is drawn later, and behind since it's more distant. I tell this just to help tracing my error, maybe it's a thing dealing with 3d/2d thingies..

===============================
What I discovered:

if I set sceGuTexMode( GU_PSM_8888, 0, 0, 0); in the initGU I disable the swizzle thing (and I expected to see two ruined textures, as far I learned if you want to use textures exceding 32x32 pixels you've got to swizzle them and to set in the initGU the last parameter to true) instead it happened that the first texture got wobbled and the second appears correct. In other words my code swizzle only the first texture, not the second. That's why setting the swizzle parameter to false, the unswizzled texture appears correct. But... this is confusing me because those textures are bigger than 32x32... yesterday before learning swizzle I was getting panned tilted textures... O__O what have I misunderstood?

I use a swizzling routine found on a dev site, here is it:

[chp]

swizzle_fast() should be ok, considering that I wrote that code back in the day.. :)

But you don't need to swizzle textures if you don't want to, but performance will suffer if you don't (and preferably you should use sceGuCopyImage() to copy the texture to VRAM before you use it, but that's only if you get all of this working...). sceGuTexMode(GU_PSM_8888, 0, 0, texture->swizzled ? GU_TRUE : GU_FALSE) before each draw would select swizzled/unswizzled mode for the texture.

Is Image::swizzled cleared properly when you instance it? From the code I can see in swizzle() you have a condition that might skip the swizzle altogether, and you might swizzle the first but not the second.
_________________
GE Dominator

[ruspa]

[ruspa]

IT WORKS!!!!!!!!!!!!!! IT WORKS!!!! EVEN WITH TRANSPARENCY!!!
(sorry for shouting) I read some docs on initialization instructions (sceGuenable stuff) and I was missing the alpha test, and to resolve the swizzling, I simply removed the "if already swizzled" test, this just because we don't need to re-swizzle textures after initializations, so every texture need to be swizzle once and not any more. This way every texture is forced to be swizzled and the problem is resolved :D
Thanks man, I feel really very happy!



just got to understand why I get this
"h@#@#[/game150/LANC2/lance+ùèùà" sht string if there's no printing functions in my code O__o Anyway I'm having big fun, now that things starts working :D tnx again chp!

[chp]

Good to see that you fixed it! And I don't get pissed off as long as it's proper development stuff which this was, so no worries there. :)
_________________
GE Dominator