QTVRW.QTC 1.0 Release QTVRW.QTC requires that QuickTime for Windows 2.0 or later be properly installed on your Windows computer. You may then copy QTVRW.QTC into the same directory as Director, or into the same directory as your QuickTime movie playing application. Do not install QTVRW.QTC into your WINDOWS\SYSTEM or WINDOWS directory: it has not been designed for this use. If you wish to use QTVRW.QTC in conjunction with QuickTime's standard PLAYER.EXE application, we recommend that you make a copy of PLAYER.EXE and PLAYENU.DLL in a different location from their standard installation location in the WINDOWS directory. The TESTBED.DIR Director document provides a Windows-based version of the QTVR Director Testbed, and should allow you to get started. This release has been tested on 486/25, 486/33, 486/66, Pentium 90 and Pentium 100 systems. It offers the same video board compatibility as QuickTime for Windows. As with QuickTime for Windows, some video board configurations may require the standard QuickTime usage of the Optimize=DIB or Optimize=BMP settings in order to work properly. The Windows implementation of QuickTime VR does not automatically choose between the two resolutions of a dual-resolution VR panoramic movie. By default, the higher resolution is used. To force the lower resolution to be used, add the following lines to your QTW.INI file: [VR] Resolution=1 Any other setting of this variable will have unpredictable results. BE SURE TO READ QUICKTIME VR TECHNICAL NOTE 7: WINDOWS RUN-TIME SWITCHES WHEN PORTING QUICKTIME VR MOVIES FROM MACINTOSH TO WINDOWS SYSTEMS IN ORDER TO ENSURE THAT THE MOVIES WILL BE COMPATIBLE. Change Notes from QuickTime VR for Windows 1.0b6: QuickTime VR for Windows 1.0 has an upgraded caching strategy which improves performance by reducing disk hits while panning. This code was not in place for the beta release which came with early versions of the QuickTime VR Authoring Tools Suite, and was not originally scheduled for inclusion with this release. Technical Note 7 mentions QTVRW's less aggressive caching scheme and offers some workarounds. These workarounds should no longer be necessary with this release.