Re: [r300] nasty bug found and fixed

[Aapo T. <ae...@ra...>]

> 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 brok=
en
>> 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=3DNULL warni=
ng?

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 versio=
n
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
>


--=20
Aapo Tahkola