Specifications

ManualsBrandsAmazon ManualsComputer equipmentVERSION 2.0V1

Table Of Contents

Release Notes for Mari 2.5v1

RELEASE NOTES FOR MARI 2.5V1

Release Date

07 October 2013

Best Bits of

2.5v1

• Mari support for Mac OS X 10.8.4 Mountain Lion, or above, with NVIDIA

graphics cards, and over 150 general improvements and optimizations.

• A Custom Shader API, and accompanying API documentation, has been

created. Documentation can be accessed from Help > SDK > Custom

Shader API.

• The shader code has been re-factored to improve usability and to adhere

to the coding standards.

• The smart selection tool performance has been significantly improved

and now has a progress bar, as well as the ability to be a cancelable

action.

• Key modifier behavior in the layers view has been updated so that

holding down different modifier keys while dragging layers allows you to

switch between copy, share, or move modes more easily.

• The ability to extract a snapshot in the Snapshots palette has been re-

enabled.

System

Requirements

Officially Supported Operating Systems

• Mac OS X 10.8.4 (Mountain Lion), or above

• Windows 7 (64-bit), or above

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

5.4)

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

Summary of content (19 pages)

PAGE 1
RELEASE NOTES FOR MARI 2.5V1 Release Date 07 October 2013 Best Bits of 2.5v1 • Mari support for Mac OS X 10.8.4 Mountain Lion, or above, with NVIDIA graphics cards, and over 150 general improvements and optimizations. • A Custom Shader API, and accompanying API documentation, has been created. Documentation can be accessed from Help > SDK > Custom Shader API. • The shader code has been re-factored to improve usability and to adhere to the coding standards.
PAGE 2
RELEASE NOTES FOR MARI 2.5V1 System Requirements 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.
PAGE 3
RELEASE NOTES FOR MARI 2.5V1 New Features Please download and install the latest graphics driver for your card from the NVIDIA or AMD websites. NOTE: Ensure that you are using 8.982.8.1 (AMD Catalyst 12.10) drivers or higher for AMD cards. Due to the number of cards available in the market, we are unable to test every card and, therefore, cannot officially qualify all of them individually.
PAGE 4
RELEASE NOTES FOR MARI 2.5V1 Feature Enhancements tearing if the canvas is running faster than the monitor’s refresh rate. This setting is OS- and driver-dependent. Shaders • A Custom Shader API and accompanying API documentation have been created. This allows you to create your own shaders to use alongside the default shaders in Mari. The Custom Shader API documentation has been added to the Help > SDK menu in Mari. The Shader API now contains Perlin and Simplex noise functions.
PAGE 5
RELEASE NOTES FOR MARI 2.5V1 Feature Enhancements • You can now export Ptex quad faces suitable for bilinear interpolation. • The Ptex triangle-to-quad warping conversion methods have been improved. Tolerance checks also prevent NaNs from causing out-ofbounds accessing on image data. Shaders • The shader component name Specular IOR of the Cook Torrance shader has been renamed to Specular IOR Weight. • Custom patch sizes now use the global ShaderInputs default patch size when no patch size is specified.
PAGE 6
RELEASE NOTES FOR MARI 2.5V1 Bug Fixes Shorctus and Preferences • The preference Max Batch Index Size in the GPU settings has been removed. • BUG ID 34810 - In the Manage Keyboard Shortcuts dialog, the search function has been improved so that incomplete search parameters still return results that contain part of the search string. • BUG ID 36216 - The shortcut Alt+drag and drop for channels now duplicates the dropped channel.
PAGE 7
RELEASE NOTES FOR MARI 2.5V1 Bug Fixes • Mari occasionally crashed when failing to create a layer shader. • Ptex models with concave quads resulted in quad warping during rendering. • The use of gl_PrimitiveID in the GLColorSwatch caused performance issues. The use of this has been removed. • BUG ID 13435 - The grid and lights were sometimes clipped in Ortho view. • BUG ID 27657 - Linux only: Mari did not always correctly restore the window position and size.
PAGE 8
RELEASE NOTES FOR MARI 2.5V1 Bug Fixes • BUG ID 35050 - Pressing the modifier keys while the mouse button or tablet pen were held down did not engage navigation. • BUG ID 35058 - Mari did not update the copy, move, and share modes of layer dragging when you changed the modifier key. • BUG ID 35061 - Mari did not calculate values over 1.0 in the Screen blend mode. The blend mode is now calculated so that it is in line with the standard that Nuke uses.
PAGE 9
RELEASE NOTES FOR MARI 2.5V1 Bug Fixes • BUG ID 35501/36894 - The clamp() function was incorrectly accessible from various blend modes and the HSV adjustment layer. • BUG ID 35650 - Object Space Linear Gradient was not operating for displacement for deferred rendering. Additional information related to this bug has been included for developers in the Developer Notes. • BUG ID 35728 - Undo stopped working after using the Paint Buffer Transform tool.
PAGE 10
RELEASE NOTES FOR MARI 2.5V1 Bug Fixes • BUG ID 36909 - It was possible to clamp the Levels adjustment layer. • BUG ID 36952 - Reloading files containing multi-object projects used incorrect channels on the shader. • BUG ID 36972 - The Zoom Paint Buffer mouse cursor did not appear over the canvas. • BUG ID 36998 - Cached nodes were incorrectly triggering node upgrades.
PAGE 11
RELEASE NOTES FOR MARI 2.5V1 Bug Fixes • BUG ID 37696 - Spheres that represented lights were rendered in front of scene objects instead of in depth order. • BUG ID 37726 - Opening Levels or Clamp filter dialogs sometimes caused Mari to crash. • BUG ID 37736 - Mari sometimes displayed the Converting Layers dialog on opening a project that was created in the same version. • BUG ID 37740 - The Add Noise filter stopped the canvas rendering correctly.
PAGE 12
RELEASE NOTES FOR MARI 2.5V1 Known Issues & Workarounds Known Issues & Workarounds Mari Tools • BUG ID 15810 - The black borders at the edge of the canvas in Perspective view are selected, if an object overlaps the borders when a selection is made using the Marquee Select tool, with the selection mode set to Magic Wand. • BUG ID 13640 - The Blur tool can be slow to use on the initial stroke. Wait for Mari to process the blur before applying a second stroke.
PAGE 13
RELEASE NOTES FOR MARI 2.5V1 Known Issues & Workarounds • BUG ID 26460 - Painting a mask in a Mask Layer Group sometimes results in unexpected paint results. To prevent this from happening, either: • Use a white “color” layer at the bottom of your mask stack. Any layer used over this initial “color” layer should then be fine, or • If you want to create a mask in a Mask Layer Group, simply add another layer on your Mask Layer Group instead, and paint white into it to create a mask.
PAGE 14
RELEASE NOTES FOR MARI 2.5V1 Known Issues & Workarounds Ptex • BUG ID 17626 - It can take a long time to import very large or very high polygon count Ptex models. The workaround is to assign a small uniform face size (1x1 or 2x2) on import, and then increase the resolution of the relevant bits of the model as necessary after loading. • BUG ID 17618 - Ptex does not bake properly if the resolution of the face is too small.
PAGE 15
RELEASE NOTES FOR MARI 2.5V1 Known Issues & Workarounds To work around this, set the locale (language) to English. • BUG ID 31946 - Sometimes paint is not baked because of memory management issues on the graphics card. This can be due to issues such as a high resolution paint buffer, a high bit-depth paint buffer, large virtual texture size, or even a large scale value on the paint buffer transform. These issues can usually be identified by glError: 0x505 out of memory messages in the log.
PAGE 16
RELEASE NOTES FOR MARI 2.5V1 Developer Notes If this number gets too large, you may also have to modify GDIProcessHandleQuota. • BUG ID 12102 - Current brush settings do not get saved as part of the project. Instead, Mari reverts to the default settings when you close and relaunch it. • BUG ID 11874 - Mari doesn’t recognize 3-digit padded .obj sequences as animation. Developer Notes These are the changes relevant to developers. New Features • The module mari.current has been added to the Python API.
PAGE 17
RELEASE NOTES FOR MARI 2.5V1 Developer Notes Feature Enhancements The Foundry • New classes have been added to the MriShaderNetwork.pro file. • BUG ID 27593 - The new signals mari.projects.aboutToArchive and mari.projects.archived have been added. • BUG ID 34698 - The new function Layer.setName() has been added to the Python API. • BUG ID 34727 - The LayerStack.exportImages(), LayerStack.exportImagesFlattened(), PaintableLayer.exportImages(), and ProceduralLayer.
PAGE 18
RELEASE NOTES FOR MARI 2.5V1 Developer Notes Bug Fixes The Foundry • Context log tracking has been disabled. • The Python API metadata flag METADATA_REMOVEABLE has been deprecated due to a spelling error. The metadata flag METADATA_REMOVABLE should be used in future. • Mari occasionally crashed when fewer than four pairs of numbers were given to MriGradient. • Mari unnecessarily added Change Expression undo records, even with non-undoable actions.
PAGE 19
RELEASE NOTES FOR MARI 2.5V1 Developer Notes • BUG ID 36400 - Mari::GeoEntity::systemShader() and Mari::GeoEntity::SystemShaderType() functions have been added to the Python API. These functions ensure that system shaders such as Current Channel can be obtained using Python. • BUG ID 36958 - The ability to set MriExportTemplate and MriImportTemplate metadata for a project was incorrectly added. The ability to set the MriExportTemplate and MriImportTemplate metadata of an object has been added instead.