home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
World of Graphics
/
WOGRAPH.BIN
/
761.BOUNDING.DAT
< prev
next >
Wrap
Text File
|
1992-11-04
|
6KB
|
130 lines
All test were run on the same machine, a 486/66 with 16 Megs of RAM.
Each of the original images contained the same exact object, just
differing in size. The ASMALL image is an 18 point "A" done with a
True-Type font (similar to Roman) under Windows. AMEDIUM is the same
character at 36 points. ALARGE was done at 72 points. AHUGE was done
by using Alchemy to scale ALARGE 2x2, thus it's approximately a 144 point
character.
Note that AHUGE will render exactly the same as ALARGE, since the
image was evenly scaled without dithering or anti-aliasing. It was just
added to get some ideas of render time, and it's resulting renders should
not be used in a quality comparison.
Each of the PoV objects was scaled to be one unit high and one unit
thick. The width was scaled proportionately to the height. Basically,
it's a 1x1x1 object.
The object's texture{ was "color red 1" to keep it simple. The camera
was placed at a distance which made the object almost fill the screen.
Each was rendered at 640x480 with no anti-aliasing. Three light sources
were placed, one White and two Gray60. Everything was kept as basic as
possible.
Each of the resulting targa file would have been exactly the same,
except for the blockiness which occurred in the objects converted from the
smaller Targas.
File ASMALL AMEDIUM ALARGE AHUGE
Image Size 60x56 115x108 223x211 446x422
File Size 3 Kb 12 Kb 47 Kb 188 Kb
Boxes Output 91 184 369 738
Character Size 18 Pt 36 Pt 72 Pt 144 Pt
Best /B Setting 2 3 5 6
Lines/Bound 7 10 16 20
=== TIMES ===
Lines
Per
/Bn Bound ASMALL AMEDIUM ALARGE AHUGE
1 4 7:04 11:10 19:35 35:52
2 7 >6:37< 10:06 15:51 28:37
3 10 6:53 > 9:31< 14:39 25:22
4 13 7:15 9:32 14:29 23:51
5 16 7:50 9:56 >14:17< 23:12
6 20 8:41 10:43 14:30 >22:48<
7 25 9:43 11:29 15:02 22:54
8 35 11:41 13:16 16:56 23:49
9 50 17:00 17:29 19:51 25:56
Ver 1.0 -- 16:56 32:49 1:06:05 2:10:48
The results from TGA2POV version 1.0 where thrown in to get an idea of
version 2.0's improvement.
Notice the times on each side of the best time for each character.
There's not much difference. So even if you're off by one setting, it
won't make much difference.
Don't use these times to get an idea of how long your object will take
to render. Since each object almost fills the screen, most of the rays
hit it, thus maximizing the render time. If you scale the objects to a
tenth the size, the render takes a fraction of the times above.
In the images used in the chart above, each object was 1 unit tall and
placed about 2 units away from the camera. I also ran the same objects
placed 30 units from the camera. The time differences between these
renders where negligible. For some reason, I didn't write down these
times, but AHUGE took about 15% longer to trace than ASMALL. They all
took slightly longer than a minute.
I also ran a couple of other images. One was my initials, and the
other my full name. Both were done in a fancy, cursive font, which
resulted in a lot of boxes being output. Due to time constraints, I
didn't get to do complete testing with these images. However, both
rendered faster when converted using a smaller /B option.
The image containing my initials was 932x400 and contained 3158 boxes.
It's best time was with /B2.
The full name image was 2910x478 and contained 5092 boxes. It's best
time was with /B1.
Hopefully this file will help you find the best bounding option with a
minimum of fuss. And considering that it doesn't make that much of a
difference if you use /B4 or /B5, then hopefully you'll get it right the
first time.
Also, remember that the render takes much less time if the object is
not too large in the render. If the entire screen is filled by an object,
it's going to take a long time. But if you just want to add your initials
in the corner, then it shouldn't make too great of a difference.
EXAMPLES.ZIP
============
This file contains a half dozen images using the above mentioned
objects. They should give you some idea of the quality to expect with
your images.
Each of the A's was rendered at 800x600, with no anti-aliasing. The
last two were done at +a0.001. Anti-aliasing (even a little) seems to
make a big difference with these objects.
ASMALL.GIF Three copies of the letter A converted from the 18-pt font.
AMEDIUM.GIF Three copies from the 36-pt font.
ALARGE.GIF Three copies from the 72-pt font.
ALL.GIF This contains two samples from each of the font sizes, 18,
36, 72, and 144.
The top left object is the 18-pt A. The top right is the 36-pt.
The bottom left is the 72-pt, and the bottom right is the 144-pt.
Across the middle they run 18 thru 144 point, left to right.
As you can see, there's not too much difference in the smaller
objects.
SES.GIF My initials done in a fancy cursive font.
MIRROR.GIF My full name in the same font. I positioned this object
behind the camera, and placed a sphere textured as a mirror in
front. Because there's nothing else in the scene, you have no
indication that it's a mirrored object, and it appears to curve
around. I just did it this way for the hell of it.