From: Keith W. <ke...@tu...> - 2005-02-04 10:41:17
|
Ian Romanick wrote: > Keith Whitwell wrote: > >> Ian Romanick wrote: >> >>> You guys have been doing a lot of work lately on the Unichrome >>> driver. That's really cool as that driver needed a LOT of work done. >>> Unfortunately my only Unichrome box is now my home firewall, so I >>> can't do any more work on it. >>> >>> In anycase AFAIK, DOT3 bumpmapping is still totally busted on the >>> driver (at least on CLE266). I played around with it for a couple of >>> days and could never get it to work. I don't have the docs, so maybe >>> one of you guys could look at it and get it working? ;) >> >> >> I've only skimmed the docs but it looks at least like it will only >> work in single-texture mode, or it may require some sort of multiple >> pass arrangement to get the work done. The docs are kindof opaque and >> don't necessarily shine a lot of light. > > > Ouch. So, did they just use babblefish to translate them from the > original language or something? :) > >> As it turns out I'm in that area at the moment, but trying to >> understand the glean texCombine failures. DOT3 is definitely further >> down the priority list at the moment, but if things go smoothly I may >> have a little time to investigate... > > > Yeah. :( I made \todo notes in there about some simple texenv cases > that also fail. That chip seems to have some odd "quirks". Turns out there's only one remaining quirk in the texture combine area - the internal color values on my CLE266 hardware seem to overflow occasionally when the 4x scaling is enabled. Once you get your head around what the regs are actually specifying, it all works pretty faultlessly... I'm not sure DOT3 is salvageable though, as it relies on the 4x scaling mode... It may be that later hardware fixes the issue, but I haven't had a chance to check yet. Keith |