Updated Vibrant Graphics drivers for Autodesk 3D Studio Release 3/4

                     Inline Driver Version 1.1.3
                       Release date -- 02/21/97

***********************************************************************
 
Keys: 
    Autodesk 3D Studio, Vibrant Graphics drivers, VIB3DS.VLM, 
    VIBRANT.RES
 
Abstract:
    This is an update to the Vibrant Graphics drivers which shipped with
    Autodesk 3D Studio release 3 and 4.  Specifically, this consists of
    VIB3DS.VLM and VIBRANT.RES.  Numerous changes were made - see below.

Caution:
    This software has not been tested by Autodesk.  Use at your own risk.
    Autodesk disclaims any responsibility for supporting users running
    3D Studio Release 3 and Release 4 with this new set of driver.

Installation instructions:
    Run the Install program to install the files on your system.  See the 
    README.TXT file for more information. 
 

*** DRIVER CHANGES *************************************************

    New support for the Imagine 128 Series II


*** CARDLIST SUPPORT ***********************************************

Additional supported Cards:

    Fujitsu Sapphire 3D Designer
    Fujitsu Sapphire 2SX
    ELSA GLoria
    Spea Fire GL
    Number Nine Motion FX 771
    Number Nine Imagine 128 Series II

Additional supported Chipsets:
    
    C&T 65535 and 65545
    Trident 9440 and 9660

*** IMPLEMENTATION SPECIFICS ***************************************

Attention TIGA users:

    A new VG940124.RLM file is included to replace VG920922.RLM. This 
    file is required to support the new TIGA draw-library.  This RLM 
    file will be placed into the directory specified with the -m 
    parameter in your TIGA environment variable.


Attention ATI Mach64 users:

    You may experience a long delay between giving the command to 
    start 3D Studio (typing '3ds' and pressing <Enter>) and seeing
    the display on your screen.  This is caused by 3D Studio making
    a series of calls to the ATI BIOS, and these calls take place
    *before* the Inline driver is started.  This delay only happens
    when 3D Studio actually starts: switching between the main 
    display, the Materials Editor, and the Rendering screen is not 
    affected.  This delay happens after leaving the VIBCFG screen
    to go into 3D Studio.


Attention S3 users:

    An earlier version of the Inline driver had a bug with flics and
    S3 chips.  If a flic was generated with this version of the driver,
    it will continue to hang with newer versions.  If you encounter a
    flic which hangs on playback, then you should regenerate it with
    this newer driver.  This only seems to apply to S3s.


*** KNOWN BUGS *****************************************************

Intergraph G91-2MB (rev. C)

    Noticeable overscan (several pixels worth of the display shows 
    on the left side of the screen instead of the right side) can be 
    seen in all Intergraph modes except for 640x480x8bpp and 
    800x600x8bpp, which don't work at all.  This is due to a problem
    with the Intergraph P9X00RES.DAT file. Similar problems have been
    seen with the Intergraph Windows driver.

    The latest Intergraph P9X00RES.DAT files have, in the individual
    timing sections, lines reading

        MemCfgClr=E7FFFFFF
        MemCfgSet=00000000

    The first line is incorrect: the value should be FFFFFFF (change
    E7 to FF). Alternatively, both lines can be deleted without
    affecting the Vibrant driver.  The effect this change has on
    Windows and other drivers is not known at this time.
    
    The problem has been communicated to and acknowledged by 
    Intergraph.  With their next release of Windows drivers, they
    will remove, comment out, or otherwise disable the MemCfgClr and 
    MemCfgSet values.
    

miroCRYSTAL 8S; 1024 x 768 x 8bpp; 3D Studio

    In 3D Editor, select Renderer, then Render View (use the default
    resolution for rendering).  While the system is calculating,
    hitting the space bar to switch to the rendering screen will
    cause the system to switch to the rendering screen and display 
    an *empty* dialog box, then lock.  
    
    A similar problem was seen using the VESA 800 x 600 x 8bpp mode; 
    in that situation, the dialog box displayed the message 
    "Oops. Went past end of dither buf: 0/0" and displayed the word 
    "Continue" in the button.  In both cases, clicking the button 
    registered a click (i.e. the button was 'pressed' and 'released') 
    but the program remained stuck on that screen until the system 
    was rebooted.


miroCRYSTAL 10S (monitor: miroCONV.PAL), 768 x 576 x 16bpp

    In all applications, there is noise consisting of horizontal
    lines (roughly 100 pixels long) on both sides of the screen ONLY
    when horizontal lines are being drawn (i.e. a box or the cursor 
    is being moved in AutoCAD). The noise goes away after the drawing
    of the line is finished.


======================================================================

If you have questions or comments about the Inline Driver please
call:

    (415) 507-5000

Ask to be connected to the Multimedia Group.

If you have any questions about any other Vibrant Graphics' products, 
please call:

    U.S. and Canada, (512) 250-1711
    U.K. and Europe, +44-91-478-1016
    Asia (Taiwan voice), +886-2-593-5201
    
Vibrant Graphics can also be reached on the World Wide Web at:

    http://www.vibrant.com

or via our BBS at:

    (512) 918-3411 (U.S. phone number)

======================================================================