| Age | Commit message (Collapse) | Author |
|---|
|
Check for NaN/Inf, print exec vectors, print temp registers.
|
|
The 'dots' register wasn't getting properly un-negated and un-swizzled
after emitting the code for back-face lighting. So, if more than one
light source was enabled, the specular exponent for the next light source
was wrong.
During execution we were evaluating pow(x, y) where y was negative instead
of positive. This led to the outcome being zero or NaN.
This fixes the occasional black triangles seen in isosurf when hacked to
enable two-sided lighting.
|
|
|
|
And print/warn NaN/Inf in print_vertex().
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit b65bc1b6cb72df950c2e26446936804dfcdc432c)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A breakpoint is much nicer than abort when gdb is attached.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Clearly, something else is wrong.
|
|
|
|
|
|
|
|
ARGB, not RGBA.
|
|
|
|
Why didn't this come up before?
|
|
|
|
We don't upload the pixels with the CPU in that case, so the map will
only serve as a way of triggering cache flushes over a bunch of data we
don't touch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Make python surface just a dumb (texture, face, level, zslice) tuple.
|
|
Surfaces are now by definition GPU views. So CPU access flags don't make
any sense when creating a surface.
For now we are forcing surfaces to be GPU read/write, but that will go away
soon.
|
|
|
|
|
|
|
|
|
|
|
