Specifications

ManualsBrandsAmazon ManualsComputer equipmentVERSION 2.0V1

RELEASE NOTES FOR MARI 2.0V2

Release Date

13 August 2013

Best Bits of

2.0v2

• Caching and uncaching multiple selected layers now works on all selected

layers instead of the last selected layer only.

• Add Mask Stack and Add Adjustment Stack buttons have been added to

the Layers palette.

• New functions have been added to the Python API and the API

documentation has been updated.

System

Requirements

Officially Supported Operating Systems

• Windows 7 (64-bit) or above

• Linux 64-bit operating system (Fedora 12 or Red Hat Enterprise Linux

5.4)

Minimum Hardware Requirements

•Quad-core processor

• 250GB disk space available for caching and temporary files (or a

minimum of 50GB if you're working on a small project)

• At least 4GB RAM

• Display with 1680 x 1050 pixel resolution

• An NVIDIA or AMD graphics card with at least 1GB of RAM and OpenGL

3.2 support (see

Tested Graphics Cards below)

NOTE: Some newer Linux distributions have changed their network device

configuration handling and won’t work with Mari without some

configuration changes. Known affected distributions at this time include

Fedora 16, Red Hat Enterprise Linux 6, and CentOS 6 on certain, notably

Dell, hardware. Please see our FAQs for more information:

http://www.thefoundry.co.uk/support/faqs/#question_97

NOTE: Displacement preview is currently only available on the cards and

drivers that support OpenGL 4.0 or newer.

Summary of content (10 pages)

PAGE 1
RELEASE NOTES FOR MARI 2.0V2 Release Date 13 August 2013 Best Bits of 2.0v2 • Caching and uncaching multiple selected layers now works on all selected layers instead of the last selected layer only. • Add Mask Stack and Add Adjustment Stack buttons have been added to the Layers palette. • New functions have been added to the Python API and the API documentation has been updated.
PAGE 2
RELEASE NOTES FOR MARI 2.0V2 System Requirements Virtual Memory Requirements It is recommended that virtual memory be available for Mari to use, especially when handling large projects. The use of virtual memory improves stability, helping to prevent data loss on large projects.
PAGE 3
RELEASE NOTES FOR MARI 2.0V2 New Features New Features There are no new features in this release. Feature Enhancements • BUG ID 33877 - The Layers palette has been extended and now includes buttons to Add Mask Stack and Add Adjustment Stack. This makes it easier than navigating through several menus. • BUG ID 34818 - Share As Channel has been renamed to Share Layers As Channel, which now shares all selected layers into a new channel.
PAGE 4
RELEASE NOTES FOR MARI 2.0V2 Known Issues & Workarounds • BUG ID 36393 - Some combinations of Bake Render Size, Virtual Texture Size, and assets, when cached or flattened, produced incorrect blocks of color. • BUG ID 36399 - A progress dialog appeared during Python export function calls. • BUG ID 36484 - In certain instances, baking was corrupted when navigating when Auto Bake and Clear was active.
PAGE 5
RELEASE NOTES FOR MARI 2.0V2 Known Issues & Workarounds groups and layers, or to cache parts of your layer stack until a shader can be created. • BUG ID 34679 - On extremely large projects, issues can arise with shader limits and reaching the maximum allowed texture slots available. To avoid reaching these shader limits on large projects, try the following workarounds: • hide groups and layers, or • cache groups and layers.
PAGE 6
RELEASE NOTES FOR MARI 2.0V2 Known Issues & Workarounds Nuke<>Mari Bridge • BUG ID 23010 - Nuke<>Mari Bridge: If Mari crashes when receiving incoming components from Nuke when the Virtual Texture Type is set to Float, lower the Virtual Texture Size to a value below 8192x8192. • BUG ID 19829 - Nuke<>Mari Bridge: Unprojecting a displaced piece of geometry does not project correctly in Nuke. • BUG ID 19780 - Nuke<>Mari Bridge: A projector created in Ortho view in Mari does not re-project correctly in Nuke.
PAGE 7
RELEASE NOTES FOR MARI 2.0V2 Known Issues & Workarounds • BUG ID 18457 - Using NVIDIA graphics cards from the Fermi series with drivers older than version 270 results in various rendering issues when the Virtual Texture Type is set to Half or Float. To resolve this, please download and install the latest graphics driver for your card from the NVIDIA website. • BUG ID 12567 - Enabling Sync to VBlank in NVIDIA settings can drastically reduce Mari’s performance.
PAGE 8
RELEASE NOTES FOR MARI 2.0V2 Known Issues & Workarounds • BUG ID 14201 - Linux only: Mari becomes unresponsive after the system is woken from sleep. • BUG ID 13700 - Adjusting the Camera > Perspective settings for a Projector is not reflected on the canvas until the Projector is made Current. • BUG ID 13571 - Launching a new version of Mari for the first time, when a config file exists from a previous version, sometimes results in an object not appearing in the Ortho view.
PAGE 9
RELEASE NOTES FOR MARI 2.0V2 Developer Notes Developer Notes These are the changes relevant to developers. New Features • BUG ID 35012 - The mari.Channel.setName() and name() functions have been added to the Python API. • BUG ID 35941 - The Channel and LayerStack classes are now derived from the Metadata class, so that metadata can be added to a channel, as in earlier versions. • BUG ID 36142 - The Layer.siblingSharedLayerList() function has been added.
PAGE 10
RELEASE NOTES FOR MARI 2.0V2 Developer Notes • BUG ID 36252 - The GeoEntity.shaderStandaloneTypeList(), GeoEntity.shaderDiffuseTypeList(), and GeoEntity.shaderSpecularTypeList() functions have been made static. This allows them to be called without a specific GeoEntity object. Bug Fixes The Foundry • BUG ID 15922/36208 - The ImageSet.importImages() function did not properly handle $CHANNEL and $LAYER token replacements in file names during imports. The ImageSet.