> Aapo Tahkola wrote:
>> Ok. I said that this bug doesnt exist and it was just my problem ...
>> I changed my mind as it appeared again after rebuilding just about
>> everything and tracked it down after long battle. This was caused by
>> missing curly braces around texcoord VAP input configuration and
>> resulted
>> in all 8 texture units to be configured whenever vertex programs were
>> used.
>>
>> However there is one thing I dont understand about this:
>> How did badly configuring VAP input caused vertex programs to get broken
>> when dummy var was added into struct r300_dma or struct r300_state ?
>
> 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)
>
>
> Rune Petersen
>
--
Aapo Tahkola
-------------------------------------------------------
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_ide95&alloc_id396&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
