[Crystal-cvs] CVS update: CS/docs/texinfo/apps/walktest

[Jorrit T. <jo...@sl...>]

Date:	Friday March 31, 2000 @ 1:07
Author:	jorrit

Update of /cvsroot/crystal/CS/docs/texinfo/apps/walktest
In directory slayer.i.sourceforge.net:/tmp/cvs-serv15191/docs/texinfo/apps/walktest

Modified Files:
	general.txi 
Log Message:
- Added static compilation support for line renderer and new
  infinite renderer.
- Added new infinite 3D renderer for statistics gathering. This
  is a theoretical infinite speed renderer with which you can
  exactly time what work the engine is doing and what the
  maximum theoretical FPS for the engine is.
  This renderer doesn't even create a window so it is not
  interactive at all. This means that you have to prepare a
  bit in order to use it. First start with a normal renderer
  and go to some spot that you want to benchmark. Press shift-C
  there to record the position (in 'coord'). Then quit and
  restart walktest with the following parameters:
  	walktest level -video=infinite -exec=perf.scr
  perf.scr is an example script that will turn on the c-buffer,
  restore the camera to the location, render a number of frames
  and then quit CS.
- Added -overdraw commandline option for the infinite 3D renderer
  so that you have additional testing for the overdraw ratio
  per frame. The overdraw ratio is the ratio of drawn pixels
  compared to the number of screen pixels. A ratio of one means
  no overdraw. A ratio less than one means underdraw (i.e. not
  all of the screen is rendered). Note that since the default
  clipper in CS is actually slightly less than the screen size
  you will get something like 0.98 also even if you have perfect
  no overdraw.
  Note that overdraw testing SLIGHTLY increases the infinite
  3D renderer processing time so this means that performance
  might go down a little.
- Added -fastmesh commandline option for the infinite 3D
  renderer which simulates a renderer that has hardware accelerated
  transforms. In other words, DrawTriangleMesh and DrawPolygonMesh
  will not do any transformation from world->screen space anymore
  as it happens when -fastmath is not used. Note that this
  invalidates the accuracy of the overdraw testing. So you should
  probably not combine both options.
- Added argument to 'perftest' command for the number of
  performance iterations.