Aapo Tahkola wrote:
Aapo Tahkola wrote:
I think the dummy only worked for you. It didn't help me.
this also fixed software fallback for me.
just to be sure:
when you run arbvptorus (unmodified) do you get the texobj=NULL warning?
They dont show up today and they arent in yesterdays logs.
Not even "Mismatch between"-warn.
I must say that iv removed last instruction("MOV result.texcoord,
vertex.texcoord;\n") from arbvptorus.c long time ago from my local version
as it shouldnt be there.
Here are the logs done by tweaking arbvptorus to draw only 30 frames:
http://nu.rasterburn.org/~aet/log.14 (broken)
http://nu.rasterburn.org/~aet/log.15 (working)
Bad news:
That extra instruction causes texobj=NULL and therefore texture corruption.
Rune Petersen
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
