[vtk-developers] (no subject)

Volpe, Christopher R (CRD) volpecr at crd.ge.com
Tue Oct 30 22:30:31 EST 2001


I got a substantial improvement as well after pasting the change into my pre-4.0 build at home
(Athlon 650, GeForce-256)

Pre-change:

Best results, summary :
  - intel running Windows NT 5.0
  - VTK 3.2.0 (rev: 1.997, 2001/10/06 00:04:38)
  - Win32OpenGL
  - Visual is 1600x1200, truecolor/truecolor/32
  - Tcl/Tk 8.3.3
  - window was 400 x 400
   1) 256x256 : 2050.2 kpolys/s : [stripper]
   2) 256x256 : 1103.7 kpolys/s : []
   3) 256x256 : 1103.7 kpolys/s : [transparency]
   4) 256x256 : 1088.3 kpolys/s : [small_sphere]
   5) 256x256 : 1088.3 kpolys/s : [wireframe]
   6) 256x256 :  813.3 kpolys/s : [texture]
   7) 256x256 :  811.6 kpolys/s : [texture, transparency]

------- DONE (in 98 sec.) -------


Post-change:

Best results, summary :
  - intel running Windows NT 5.0
  - VTK 3.2.0 (rev: 1.997, 2001/10/06 00:04:38)
  - Win32OpenGL
  - Visual is 1600x1200, truecolor/truecolor/32
  - Tcl/Tk 8.3.3
  - window was 400 x 400
   1) 256x256 : 4584.5 kpolys/s : [stripper]
   2) 256x256 : 2782.8 kpolys/s : [small_sphere]
   3) 256x256 : 2763.1 kpolys/s : []
   4) 256x256 : 2763.1 kpolys/s : [transparency]
   5) 256x256 : 2580.3 kpolys/s : [texture]
   6) 256x256 : 2530.1 kpolys/s : [texture, transparency]
   7) 256x256 : 1022.4 kpolys/s : [wireframe]

------- DONE (in 40 sec.) -------

Anyone know why wireframe mode is impervious to the fix?

>



More information about the vtk-developers mailing list