Xref:	news2.mv.net comp.os.msdos.djgpp:2830
From:	amason AT cs DOT uct DOT ac DOT za (Ashton Mason)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: GRX20 Speed
Date:	16 Apr 1996 08:27:04 GMT
Organization:	University of Cape Town
Lines:	26
Message-ID:	<4kvlko$ee7@groa.uct.ac.za>
References:	<316D3201 AT macduff DOT ficsgrp DOT com>
NNTP-Posting-Host:	inky.cs.uct.ac.za
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In <316D3201 AT macduff DOT ficsgrp DOT com> DBI <DBI AT ficsgrp DOT com> writes:


>>GrBitBltNC functions.  I was STARTLED to see that I could only achieve
>>around 40 FPS just clearing a memory context then writing it to the
>>screen in 320 x 200 x 256 mode.  A similiar program written in
>>Borland C 4.5 REAL mode accomplishes 160+ FPS.

>I don't know about GRX, but I suggest you take a look at ALLEGRO (on   
>X2FTP). This is a graphics/sound/keyboard/joystich/mouse/timer library   
>built for game programming with well optimized blitting routines!. I get   
>speeds of 200-300 FPS in 320x200x256 (on a 486 DX4-100) doing something   
>similar. (just clearing->blitting)

Were you using a virtual screen in RAM (I forget what Allegro calls them),
or a hidden page on the virtual screen in video memory?

I've tried both without much luck, but I think I must be doing something
wrong. I must say, the documentation for Allegro could be a bit clearer,
IMHO. (not that I could do any better).

Ash
--
"how can all these things be true?"
amason AT cs DOT uct DOT ac DOT za        http://www.cs.uct.ac.za/~amason 

- Raw text -