* Curtis L. Olson -- Friday 15 August 2003 19:56:
I haven't looked into this issue very closely. I have an nvidia card
and wasn't seeing anything odd, but perhaps I wasn't looking closely
enough.
Same for me: nvidia without having seen anything strange.
m.
Melchior FRANZ wrote:
* Curtis L. Olson -- Friday 15 August 2003 19:56:
I haven't looked into this issue very closely. I have an nvidia card
and wasn't seeing anything odd, but perhaps I wasn't looking closely
enough.
Same for me: nvidia without having seen anything strange.
Here are
Curtis L. Olson wrote:
Erik,
Using glGet() is considered a no-no in real time applications. That
stalls out the pipeline and forces all pending operations to flush
before the card can return with the correct answer. We might be able
to get away with it in limited quantities, but this can
Erik Hofman wrote:
Curtis L. Olson wrote:
Erik,
Using glGet() is considered a no-no in real time applications. That
stalls out the pipeline and forces all pending operations to flush
before the card can return with the correct answer. We might be able
to get away with it in limited
Erik Hofman writes:
Curtis L. Olson wrote:
Erik,
Using glGet() is considered a no-no in real time applications. That
stalls out the pipeline and forces all pending operations to flush
before the card can return with the correct answer. We might be able
to get away with it in
Curtis L. Olson wrote:
Erik Hofman writes:
Curtis L. Olson wrote:
Erik,
Using glGet() is considered a no-no in real time applications. That
stalls out the pipeline and forces all pending operations to flush
before the card can return with the correct answer. We might be able
