home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!rutgers!concert!borg!phoenix.radonc.unc.edu
- From: soltys@phoenix.radonc.unc.edu (Mitchel Soltys)
- Newsgroups: comp.sys.sgi
- Subject: GLX slow rendering problem
- Keywords: GL, GLX, shaded rendering
- Message-ID: <14891@borg.cs.unc.edu>
- Date: 1 Sep 92 14:54:08 GMT
- Sender: news@cs.unc.edu
- Distribution: usa
- Organization: Radiation Oncology, NCMH/UNC, Chapel Hill, NC
- Lines: 43
-
- under GLX. I am guessing that the problem is that some state is turned
- on/off and causing the slow down. Unfortunately I am adding additions
- to some old X software and do not know exactly which states may be in
- effect. Thus my question:
-
- Would someone please tell me what "things" might slow down rendering
- under GLX?
-
- To be specific, I am comparing a GLX program I wrote to render ~84000
- triangles to some GLX code in a MUCH LARGER program. In my code I am
- able to render the triangles in ~ .5 secs (no meshes, the old code
- doesn't use meshes). In the old code, this section of code:
-
- for(i = 0; i < num_triangles;i++){
- bgnpolygon();
- n3f(fake_vector);
- v3f(fake_vector);
- n3f(fake_vector);
- v3f(fake_vector);
- n3f(fake_vector);
- v3f(fake_vector);
- endpolygon();
- }
-
- takes ~1.6 secs ... more than three times as slow. The fake_vector was
- used to make sure that valid values were passed to n3f and v3f. Taking
- out the v3f call and leaving only the n3f (just trying to figure out
- where the problem is) cuts the rendering time to ~.4 secs in the old
- code which leads me to strongly suspect that there is some global
- variable set which is interfering with rendering.
-
- The program I am modifying is quite complex, using, stenciling,
- texture mapping, multiple windows under X etc. Things I have been
- trying include texturing (turned off), subpixel(TRUE). I would like to
- be able to guarantee "a clean environment", render dummy triangles
- using n3f and v3f in less than .6 secs, and work back from there. But
- right now I can't get anything to render quickly.
-
- Much thanks to anyone who can give me a clue as to what may be going
- wrong. It may be some stupid mistake in my code, but I haven't found
- it yet. Thanks again for any help.
-
- Mitchel Soltys
-