Re: Line Clipping

2000-01-29 Thread Rubén

On 2000/Jan/28, Dmitry Semenov wrote:

 Also I found that Matrox G100 acceleration is slowly than software drawing.

It's impossible! On my machine the S3 Virge acceleration is _always_
faster than software drawing, even taking into account that it means lots of
ioctl's on /dev/fb. I have an PII 333 MHz. And AFAIK S3 Virge is much slower
than Matrox G100, maybe I'm wrong?
-- 
  _
 /_) \/ / /  email: mailto:[EMAIL PROTECTED]
/ \  / (_/   www  : http://programacion.mundivia.es/ryu
[ GGL developer ]  [ IRCore developer ]  [ GPUL member ]



Line Clipping

2000-01-27 Thread Dmitry Semenov

Hi

I found that standard GGI line clipping getting perpetual loop with some
arguments. It was while using these arguments: 568, 383, 49360, and 1234 for
clipping area 100, 3, 1019, 766. May be it was different because I found it
written in my notebook but sure only for 90%. Anyway it was close enough. It
happened because of overflow in line formula.
Solution is: just break the perpetual loop. It's not necessary there.
Also I found that Matrox G100 acceleration is slowly than software drawing.
That's it.

Best Regards, Dmitry Semenov
EMail: [EMAIL PROTECTED]
Web:  www.chollian.net/~hatter

-Original Message-
From: Rubén [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 28, 2000 7:36 AM
To: [EMAIL PROTECTED]
Subject: Re: SGI OpenGL freely avalibale.


On 2000/Jan/27, Steffen Seeger wrote:

  Dynamic assembly code generation for rasterization is not yet included,
  making software rendering performance slow.

 Interesting, we came about the same technique as SGI:
 The GGL code in KGI-0.9 was a code-study how to dynamically
  ^^^

What do you refer to with GGL? :)
--
  _
 /_) \/ / /  email: mailto:[EMAIL PROTECTED]
/ \  / (_/   www  : http://programacion.mundivia.es/ryu
[ GGL developer ]  [ IRCore developer ]  [ GPUL member ]
  ^^^