Re: vrml browsers

[email protected]
Thu, 1 Jun 95 10:36:43 CDT


>
>
> Dear Daeron and the rest of the list. (Especially you browserbuilders) I have
> a problem with opengl. The problem is that on PCs opengl tends to be slow (100
> mhz p5 with 32 megs RAM) Now I do have a hardware accelerator for my Matrox
> impression plus. At Matrox they are saying that they want to support opengl at
> a future date however I should expect about 40k polys a seconf on that system.
> Using the rendermorphics library I would (according to rendermorphics!) be
> able to push 300k polys a sec (My pentium can benchmarked in C (haven't tried
> asm) only push about 200k polys a sec). With such differences it makes me
> wonder if it would be worth it to translate from opengl to rendermorphics
> specs on the fly and use that.
>
> NOTE: I may sound like an idiot here and i'm getting the specs right after I
> wrote this letter. My impression is that vrml relies heavily on opengl if I'm
> wrong; please don't flame; or ad me to any "dog"lists (I'm sensitive ;-) I'm
> just fairly scatterbrained and if I don't post my thoughts when they come up I
> might never do it.
>
> Hi-Lo
>
> [email protected]
>

Hello there,

Just to clarify on your thoughts, the VRML language is only a file format
for describing 3D objects. There is no magical tie between VRML and OpenGL
other than the fact that most people are writing VRML browsers that use
OpenGL for doing the actual rendering of each object. Of course, you could
just as easily use other rendering languages to build your browser such as
PEX or the rendermorphics library you referred to.

To rephrase your question then, I believe you are asking what is the advantage
of using OpenGL over rendermorphics, if any? The answer is that OpenGL
has much wider acceptance than rendermorphics does. That is, it is
available on more platforms and supported by more hardware companies
than any other realtime 3D rendering language. So, if you were to write
your browser based on OpenGL, you would find porting it to other platforms
a lot easier. If, however, your main concern is speed not portability,
you might really want to use the rendermorphics library to squeeze the
maximum performance out of your hardware. Keep in mind that many companies
are promising cheap fast 3D hardware that will use OpenGL real soon now :-)
Your accelerator which may seem speedy now, could quickly become obsolete.
Will your browser become obsolete too or require a complete rewrite? If
you use OpenGL, you'd probably be able to use new hardware without so much
as a recompile.

If you decide to use rendermorphics, you can at least be careful to build
your browser in a very modular style so that you can easily swap out the
rendering code and replace it with OpenGL rendering code at a later date.

Happy coding,

Daeron

(this letter written by voice)