• Maya 6.0 has been qualified under IRIX 6.5 (only):

The OS versions specified in this table are the ones used for the qualification process. While it may be possible to use Maya successfully on earlier or later versions, Alias cannot guarantee their performance or behaviour.

• How To Obtain IRIX 6.5 upgrades.

Customers with valid SGI software support can gain access to overlays through the worldwide web at support.sgi.com. Customers in North America can also call the Technical Assistance Center at 1-800-800-4744. International customers should call their local SGI office.

Customers without worldwide web access should call the Technical Assistance Center or their local SGI office as indicated above.

mental ray for Maya: Is qualified on the same platforms as Maya.

• At least 512MB of RAM is required and more is strongly recommended for any practical use of Maya.
• It may be possible to successfully use Maya with a non-qualified or partially qualified configuration, but support and maintenance programs will be subject to the Alias Support services guidelines.
• The configurations shown are subject to change, and additional qualified configurations may be added after qualification testing has been carried out.
• The OS versions specified in this table are the ones used for the qualification process. While it may be possible to use Maya successfully on earlier or later versions, Alias cannot guarantee their performance or behaviour.
• We do not recommend saving data directly from Maya to NFS or Novell Netware or other remote mounted file systems. We have received several reports of data corruption when saving in this method although we have been unable to reproduce this. We strongly recommend that you save the files locally and then copy the data to the mounted storage system.
• When texture images are stored on systems remote from the rendering process; depending on network speed, specifications and load it is possible that the renderer may be unable to access a texture file on demand and may 'drop' individual textures on a frame by frame basis. To reduce this occurrence store textures on a system local to the rendering process.
• Maya Developer's Tool Kit:
  To build Maya plug-ins, you must have MIPSpro C++ compiler version 7.2.1 or  7.3.1.1m (recommended). Additionally, plug-ins for this version of Maya must be build on IRIX 6.5. Plug-ins built on IRIX 6.2, 6.3 or 6.4 will normally crash or behave improperly if loaded into Maya.
• Maya Hardware Renderer is not supported on IRIX

• For any product other than Render Software, all SGIs require a z-buffer, except Indy XL, and Indigo2 XL. Eight-bit graphics configurations are not supported. 

• CVs and vertices may show through polygonal geometry in hardware shaded mode 
• Under some circumstances, sprites in hardware shaded mode may appear broken up. 
• Some workflows may cause screen refresh to be incorrect as you tumble and track views. Although it is unlikely that you will encounter this, changing to shaded mode and back will often correct the display. 
• Transparency does not display correctly in Hardware Render Buffer.
• Indy graphic systems may encounter minor graphics related problems that are not listed here in detail. These problems should not affect your workflow. 

• File textures not transparent in xray mode and you will be unable to see CVs, vertices or other components of objects that are behind file mapped objects. 
• Some surfaces may incorrectly appear white when rendered in the Hardware Render Buffer. 
• Sometimes rendering a region in IPR doesn't display correctly. 
• Indy graphic systems may encounter minor graphics related problems that are not listed here in detail. These problems should not affect your workflow. 

• Hardware Render Buffer output - particularly of particles, may differ between Indigo2 graphic systems and other graphics systems. As Hardware Render Buffer entirely depends on the graphic hardware or its emulation, use caution when combining HW Render images created on different hardware. 
• Some surfaces may incorrectly appear white when rendered in the Hardware Render Buffer. 
• Some transparent/translucent surfaces may appear opaque when rendered in the Hardware Render Buffer. 
• Some surfaces may appear to alter colour when viewed in shaded mode with Hardware Texturing ON depending as the camera zoom changes. 
• Some workflows may cause screen refresh to be incorrect as you tumble and track views. Although it is unlikely that you will encounter this, changing to shaded mode and back will often correct the display. 
• Indigo2 graphic systems may encounter minor graphics related problems that are not listed here in detail. These problems should not affect your workflow. 

• Occasionally unselected CVs are not displayed in the right color.
• Occasionally the wrong textures are displayed in Hardware Texture mode. This usually happen after using the Hardware Render Buffer.
• Occasionally segments of the attribute editor will be drawn in the buffer too.

• Attempting to perform a Hardware Render Buffer - Render Sequence may result in all black frames.
• Occasionally the wrong textures are displayed in Hardware Texture mode. This usually happen after using the Hardware Render Buffer.  You may also encounter a number of other problems with shaded mode with textures and Hardware Render Buffer.

• image planes containing alpha channels do not display correctly and the Alpha Gain control for images planes does not work.
• Dynamic playback of uncached particles at 24fps may not be adequate and may result in gaps in emitted particle streams.
• Hardware shadows do not display as they are not supported.
• Running Maya for long periods of time may result in slow-downs and assorted unexpected behaviours. Quitting and restarting Maya seems to resolve this.
• Hardware sprites do not display correctly in Hardware Render Buffer on SSI and ESSI graphics.

• You may encounter depth sorting problems when you're painting in 3D (paint effects window) while in shaded mode, or the display may become garbled.

• You may encounter depth sorting problems when you're painting in 3D (paint effects window) while in shaded mode, or the display may become garbled.
• Dynamic playback of uncached particles at 24fps may not be adequate and may result in gaps in emitted particle streams.
• You may encounter unexpected stability problems on systems with V6 graphics.

• Dynamic playback of uncached particles at 24fps may not be adequate and may result in gaps in emitted particle streams.
• Hardware sprites do not display correctly in Hardware Render Buffer on SSI and ESSI graphics. Occasionally segments of the attribute editor will be drawn in the buffer too.

• A number of items, such as light manipulator pivots, stencil map manipulator handles, particle emitters, many NURBS items such as first and last CVs, pivot points, etc. may not display correctly
• Alias has not been able to validate the performance of sound on this system.

You should install patch 5602 rpc.mountd updates

You may encounter the following situations:

• The paint effects window may become garbled, "flash" intermittently, or appear to paint behind shaded surfaces.
• The sculpt surfaces directional-arrow tool is invisible.
• Parts of the model grid may display over shaded geometry.
• Dragging files, hypershade icons, etc, inside Maya may result in trailing artifacts left behind.
• The Maya main window may not redraw correctly when minimized/maximized, or when other application's windows are moved across it. You must force a redraw of the affected area to correct the display.
• Moving the render view window while the IPR window is refreshing the selected region will cause a severe refresh problem. The selected IPR region will be refreshed from the original position on screen. You must redo the entire ipr render to work again.

• R4000 Indigo 
• Professional Series 
• Power Series 
• Personal Iris 
• R3000 Indigo 

• GT Graphics 
• GTX Graphics 
• VGX Graphics 
• VGXT Graphics 
• ANY 8-bit Graphics platform