In this directory is an evaluation release of VR-386.

Please read vr386.doc and vr_api.h if you wish to see what's new.
If you have suggestions or comments, please send e-mail to
dstampe@psych.toronto.edu

To help you use this stuff, I've include the proper version of pkunzip.exe
in this directory.  If you're having problems with download limits,
look in the uue directory for split versions of theses files.

The main files are: (in the ~ftp/pub/vr-386 directory)

vr386.zip: all source, demos, and API docs
video.zip: new video driver kits, including 320x400 drivers and cyberscope
cyber.zip: Cyberscope driver for use with "Virtual Reality Creations"
vr386.doc: Documents purpose and ideals of VR-386.  Various data
vr_api.h:  include file for much of VR-386, copiously commented.
borland4:  Borland C++ 4.0 update, new IDE and a couple of other files fixed

For those who don't have TASM, the object files for all assembler
modules are in ASMOBJ.ZIP.  These were compiled with BC 3.1, so
may or may not work with your linker.

When using PKUNZIP, please use the -d option to re-create the 
directory structure!

There should be a Borland C .PRJ file in the VR386.ZIP file, as well as
an (automatically created==brain dead) MAKE file.

Some of the new VR-386 command line options are:
-emm
-emm <size>
   These enable the use of your EMM386 expanded memory driver (installed
in CONFIG.SYS) for extra memory.  Size is in Kbytes: if no size is
given, all available EMM will be used.  Note that most debuggers will
not support EMM (except Soft-Ice, and it's driver is pretty slow).  If
no EMM is available, VR-386 will default to normal memory.

-k
  Enables the "key monitor" for smooth key motion.  DON'T use with
any debugger except Soft-Ice unless you like system crashes!

Speed: 
  Yes, VR386 is somewhat faster than REND386.  Why then are the 
frames per second numbers the same or lower?
  The REND386 timer ran at 120 or 180 Hz, and could not properly
compute drawing speeds above 20 fps because of this.  It also did
not take into account the overlays (messages, compass, etc) on
the screen.
  The VR-386 timer has a resolution of 1 millisecond (by reading the
timer counters) so is accurate to at least 100 fps.  It does take into
account these extra drawing operations.  Therefore reported frame
rates are more accurate.
  If you want to test _real_ frame rates, press the left arrow key,
then the "r" key.  The motion will repeat 100x with minimal 
delay from other program parts, and you can use a stopwatch and this key
to benchmark the renderer.


Borland C 4.0 notes: vr386_4.ide added, logiptr.c and vdrinte.asm
updated to fix linker/compiler differences.  Other files just keep
the dates correct, the #$@! build in BC 4.0 never does recover if file
dates are different than the .ide file expects.

FTP address:  psych.toronto.edu is at 128.100.61.1


- Dave Stampe, 29/4/94

