On Thu, 3 Feb 2005, Rune Petersen wrote:
Vladimir Dergachev wrote:
One thing you might try is to exchange the order of arguments or do
something similar. There are some comments by Nicolai on ordering of
arguments in r300_reg.h, these might reflect actual hardware limitations.
For example, I do not understand why in flat texture shader one has to have
two identical instructions and why the first and last instructions in
single texture shader are identical as well.
I couldn't find a combination that makes alpha look any better and got angry
at the identical instructions which didn't do anything.
So I removed them.
I don't se any problem without these innstuctions. unless there are special
cases. q3a and NeHe lessons 2-20 don't look any worse.
You are quite right - also the following instruction:
{
EASY_PFS_INSTR0(MAD, SRC0C_XYZ, ONE, ZERO),
EASY_PFS_INSTR1(0, 0, 0 | PFS_FLAG_CONST, 0 | PFS_FLAG_CONST, NONE,
ALL),
EASY_PFS_INSTR2(MAD, SRC0A, ONE, ZERO),
EASY_PFS_INSTR3(0, 0, 0 | PFS_FLAG_CONST, 0 | PFS_FLAG_CONST, OUTPUT)
}
looks like a NOP ( it basically does reg0<-reg0*1+0.0 ).
best
Vladimir Dergachev
Rune Petersen
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
