Release Notes for Modo 10.2v2

 

Release Date

21 February 2017

System Requirements

Officially Supported Operating Systems

Mac OS X 10.9.x, 10.10.x, 10.11.x, and 10.12.x (64-bit only)

Windows 7, Windows 8, and Windows 10 (64-bit only)

Linux 64-bit operating system (CentOS/RHEL 7+)

Minimum Hardware Requirements

Intel processor(s), Core i3 or higher

10 GB disk space available for full content installation

At least 4 GB RAM

Display with 1920 x 1080 pixel resolution

Internet connection for product activation and online videos access

The Advanced viewport mode requires an NVIDIA or AMD graphics card with at least 1 GB of graphics memory and drivers that support OpenGL 3.2 or higher.

Recommended System Requirements

Note:  This information is our best recommendation for the average user. Requirements vary by usage, and individual users may have different requirements from those listed here.

2.5+ GHz quad-core processor

250+ GB disk space available for caching and temporary files, SSD is preferable

16 GB RAM with additional virtual memory*

Display with 1920 x 1080 pixel resolution

An NVIDIA or AMD graphics card with the latest drivers

2+ GB of graphics memory

OpenGL 4.4 or higher support

*The use of virtual memory improves stability and helps prevent data loss on large projects.

Tested Workstation Hardware

The configurations listed below are those that The Foundry have tested with Modo 17.1v1. Due to the constantly changing nature and wide variety of computer hardware available in the market, The Foundry is unable to officially certify hardware. The list below can be used as a recommendation and does not guarantee that it meets your particular needs.

Please download and install the latest graphics driver from the NVIDIA or AMD websites. Make sure that you are using 8.982.8.1 drivers or higher for AMD cards.

If you encounter any issues, please visit the Support Portal at supportportal.thefoundry.co.uk.

Tested Workstation Hardware

Apple

MacPro4, 1

MacPro5, 1

iMac13, 2

MacBookPro10, 1

Dell

Dell T1700

Dell T3610

Dell T3620

Dell T5810

Dell T7610

Dell T7910

Dell Precision Rack 7910

Dell Precision 5510

Dell Precision 7710

Dell M2800

Dell M6800

HP

HP Z440

HP Z600

 

Tested GPU Hardware

AMD Prosumer Graphics Cards

Radeon™ HD 1900 XT

Radeon™ HD 2400 XT

Radeon™ HD 2600 Pro

Radeon™ HD 3870

AMD Enterprise Graphics Cards

FirePro™ W4170

FirePro™ W5000

FirePro™ W8000

FirePro™ W2100

FirePro™ W5100

FirePro™ W4100

FirePro™ W7100

FirePro™ W8100

FirePro™ W9100

 

NVIDIA Prosumer Graphics Cards

Geforce GTX 680

Geforce GTX Titan

Geforce GT 650M

NVIDIA Enterprise Graphics Cards

Quadro® K6000

Quadro® K5000

Quadro® K4000

Quadro® K2000

Quadro® K600

Quadro® K5200

Quadro® K4200

Quadro® K2200

Quadro® K1200

Quadro® K620

Quadro® M5000

Quadro® M4000

New Features

There are no new features in this release.

Feature Enhancements

Game Export: Substance textures can be exported, when enabling Copy Textures.

Note:  The Different Only option is currently not supported.

Network Rendering: Minimal logging has been added to full-frame mode.

Topology: The Retopo Edge Lock and Retopo Edge Flow controls have been added to the Mesh Edit sub-tab of the Model tools, allowing you to create edge selection sets.

Bug Fixes

Documentation: F1 Help links were broken for some UI elements.

GL: Mac OS X only: The Advanced viewport was incorrectly disabled on some operating systems.

MeshFusion: Legacy conversion issues occurred when multiple unions shared meshes through inactive input links.

MeshFusion: Enabling the MeshFusion command did not consider mesh instances.

MeshFusion: Strip Width could not be set to a width less than 10 mm in the Strip Properties.

MeshFusion: Converting multiple legacy MeshFusion setups didn't work as expected.

MeshFusion: Using MeshFusion with procedural meshes didn't work as expected.

Procedurals: The selection stack operated on the incorrect selection type if the selection type channel on the Mesh Operations list was not set correctly on creation.

Schematic: Dynamic schematic didn't allow forces to connect to dynamic replicator filters.

Shader Tree: When working with detail normal map effects, there was no prompt to switch to linear colorspace.

Shader Tree: Using Unreal and Unity materials caused a memory leak.

Shader Tree: Creating shaders occasionally caused Modo to crash.

Shader Tree: Moving non-GL textures under the base Shader item caused Modo to crash.

UV: UV peeling multiple meshes at once sometimes resulted in Modo crashing.

• ID 39162 - Rendering a frame with no visible render outputs caused Modo to crash.

• ID 47276 - Windows only: Loading long audio files sometimes caused Modo to crash.

• ID 47509 - File Output: Exporting to .dae or .obj formats with OpenSubdiv elements in a scene caused Modo to crash.

• ID 50247 - Mac OS X only: The Advanced viewport was disabled on systems using NVIDIA cards with non-Apple drivers (NVIDIA web drivers).

• ID 50629 - GL: Changing the Default View Colorspace preference when using the Advanced viewport caused Modo to crash.

• ID 50959 - GL: Drawing UV distortion in the UV view sometimes caused Modo to crash.

• ID 52045 - Rendering scenes without Environment items multiple times caused Modo to crash.

• ID 52073 - Rigging: The Gravity channel modifier was disabled.

• ID 52310 - Render window: The progress bar in the top left of the Render window did not show the Global Illumination pre-pass progress.

• ID 52722 - File Output: STL meshes changed dimensions when exported and re-imported.

• ID 53215 - MeshFusion: Partially coincident geometry sometimes caused meshing errors.

• ID 53220 - Modeling: Auto curve edit didn't work for curves in the base mesh with ghosting enabled.

• ID 53442 - Rigging: User channel minimum and maximum values were reset to 0 when editing the user channel.

• ID 53461 - Preview: Locking Preview with Render All Outputs disabled, then changing the Effect, restarted the render.

• ID 53468 - UV: Using Transfer UVs with multiple meshes caused Modo to crash.

• ID 53478 - Linux only: Opening scenes containing a Wrap Deformer sometimes caused Modo to crash.

• ID 53491 - Procedurals: Using the Boolean mesh operation with an irregular driver or target mesh sometimes caused Modo to crash.

• ID 53498 - Mac OS X only: Export Selected Layers caused Modo to crash on some operating systems.

• ID 53512 - Topology: Using Automatic Retopology on meshes with degenerate triangles caused Modo to become unresponsive.

• ID 53528 - Sculpting: The Text tip brush didn't respect font selection.

• ID 53534 - Rigging: Undoing moving a rig created by the CharacterBox kit by PSoft caused Modo to crash.

• ID 53540 - Sculpting: Sculpting didn't work on meshes scaled to 200% or more in Item selection mode.

• ID 53544 - Edge tracking on procedural models caused Modo to crash when edge vertices belonged to different meshes.

• ID 53554 - The item type for VDBVoxel items could not be set to Mesh.

• ID 53556 - Procedurals: Using the Boolean mesh operation with Driver Surface set to the selected mesh caused Modo to crash.

• ID 53557 - Mac OS X only: Activating the interactive help tool sometimes corrupted the About MODO panel.

• ID 53558 - Mac OS X only: Clicking on About MODO or Preferences when the menus were corrupted, caused Modo to crash.

• ID 53560 - Putting the main Modo config file into an import path caused Modo to crash on launch.

• ID 53573 - Procedurals: Adjusting Edge Bevel using channel hauling, with Edge Snapping enabled, caused Modo to crash.

• ID 53578 - Modeling: Deleting instances sometimes caused Modo to crash.

• ID 53584 - Render window: Dismissing a collapsed thumbnail slider's tooltip sometimes caused Modo to crash.

• ID 53588 - UI: Overwriting a 3D viewport preset occasionally caused Modo to crash.

• ID 53589 - Modeling: Activating the B-Spline tool, after selecting a B-Spline created from two edges, sometimes caused Modo to crash.

• ID 53590 - Windows only: Activating Edges to Curves from the Curve Palette on adjoining edges of a cube caused Modo to crash.

• ID 53598 - Shader Tree: Transferring materials from one scene to another swapped the order of the layers.

• ID 53599 - Modeling: The Quadruple command run on a selected polygon in a customer scene caused Modo to crash.

• ID 53602 - Color: Giving a long name to an OCIO profile sometimes caused Modo to crash.

• ID 53604 - Rendering scenes with mesh lights and masked render outputs occasionally caused Modo to crash.

• ID 53613 - Loading scenes with unnamed vertex maps sometimes caused Modo to become unresponsive.

• ID 53619 - Windows only: Loading some scenes with backdrop images into layouts with multiple GL viewports caused Modo to crash.

• ID 53620 - MeshFusion: Manipulating the control handles after mirroring a Fusion Trim item sometimes caused Modo to crash.

• ID 53622 - Procedurals: Applying the Polygon Bevel mesh operation after Symmetrize caused Modo to crash.

• ID 53634 - Rendering: When rendering certain scenes with an Orthographic camera, fireflies (hot pixels) appeared on the output.

• ID 53637 - Modeling: Using Background Morph from the Vertex Map menu caused Modo to crash.

• ID 53642 - Procedurals: Editing meshes used by hidden meshes with mesh operations caused intermittent crashes.

• ID 53647 - UI: Setting a subtext on a menu item caused Modo to crash.

• ID 53651 - GL: Calling InvalidateOverrides in modo_cl resulted in Modo crashing.

• ID 53652 - GL: Playing particle simulations in the Advanced viewport sometimes caused Modo to crash.

• ID 53653 - Network Rendering: Modo crashed when the master and worker bucket directories were not writable.

• ID 53655 - Particles: Converting a particle simulation into a mesh, then playing back the simulation and converting the mesh to particles caused an error when the simulation reached the end of the timeline.

• ID 53656 - Modeling: Moving vertices with the Transform tool with Snapping enabled occasionally caused Modo to crash.

• ID 53667 - Modeling: Using the poly.make command in Edge selection mode with Symmetry enabled sometimes caused Modo to crash.

• ID 53668 - Modeling: Localization occasionally caused Modo to crash when the scene was loading.

• ID 53674 - Rendering: Baking textured displacement produced a black image.

• ID 53676 - UI: Closing multiple scenes with the pointer over the Item List sometimes caused Modo to crash.

• ID 53680 - Modeling: Using the Topology tool in Symmetry mode occasionally caused Modo to crash.

• ID 53681 - Procedurals: Using polygon loop selection in the UV view occasionally caused Modo to crash.

• ID 53683 - Painting: Projection Ink did not respect the Density setting of the brush.

• ID 53688 - Modeling: Ctrl/Cmd+clicking and dragging on primitives did not work as expected.

• ID 53705 - MeshFusion: Clicking the Trim button with multiple meshes selected in a specific scene caused Modo to crash.

• ID 53706 - Modeling: Fill Quads using Fill with Grid Pattern did not work correctly on concave patches.

• ID 53708 - MeshFusion: Triggering an update after assigning a material to a mesh in a specific scene sometimes caused Modo to crash.

• ID 53724 - Topology: Automatic Retopology didn't respect transforms on parent items.

• ID 53728 - MeshFusion: Opening a specific scene, selecting a Fusion item in it, then activating Fusion On caused Modo to crash.

• ID 53729 - Documentation: The Preview option for Final Render Quality was not documented.

• ID 53733 - Mesh Types: Performance was low with instances imported from Collada.

• ID 53734 - Rigging: Command Regions were not selectable when the rig was moved.

• ID 53736 - Procedurals: Selecting a hidden mesh layer after editing vertices caused Modo to crash.

• ID 53754 - Scripting: Using edge.knife in a script caused Modo to crash.

• ID 53756 - MeshFusion: Clicking the Fusion Source Mesh Visibility button displayed an error message.

• ID 53768 - GL: Value gradients did not display in the Advanced viewport.

• ID 53790 - Rendering: The surface area calculation for mesh lights with non-uniform scaling produced incorrect illumination.

• ID 53791 - Modeling: Snapping didn't work on background geometry in Shaded and Default modes if geometry was overlapping.

• ID 53816 - Rigging: Deleting items from a specific scene with Command Regions caused Modo to crash.

• ID 53821 - MeshFusion: The Fusion Source Mesh Visibility control didn't affect the Compound Trim Locator.

• ID 53828 - Sculpting: Dismissing Preview lock warnings after trying to UV sculpt occasionally caused Modo to crash.

• ID 53834 - Preview: Modifying a mesh light while Preview was rendering sometimes caused Modo to crash.

• ID 53838 - Item List: Hiding unselected items also hid all images and clips.

• ID 53845 - Render window: There was no option to set the maximum render slots in the Preferences.

• ID 53852 - Network Rendering: Separate Render Outputs were not saved when using the Render with Network Nodes Only and Send Whole Frames to Network Render Nodes settings.

• ID 53885 - File Input: A scene imported using a command caused Modo to crash.

• ID 53894 - Modeling: Primitives were not placed at the position where you first clicked in the viewport.

• ID 53895 - Rendering: Lights rendered black and in the wrong place when the geometry was not visible in the scene.

• ID 53896 - Rendering: Rigging area lights with negative width or height values caused Modo to crash.

• ID 53899 - MeshFusion: Evaluating a model in a specific scene sometimes caused Modo to crash or produced a bad mesh.

• ID 53911 - Rigging: Sculpting a corrective morph onto a Joint Influence was not possible.

• ID 53912 - Modeling: While in Edge selection mode, Modo crashed when you tried to lasso-select edges on a curve that had been UV transformed.

• ID 53919 - UI: When the Info tab was expanded horizontally to display the spreadsheet view, values could not be selected, copied, or pasted.

• ID 53930 - Preview: Area lights added to an existing Group Locator caused Modo to crash.

• ID 54084 - Deformers: In some scenes, playing back an animation with cached deformations caused Modo to crash.

Developer Notes

Here are the changes relevant to developers.

Bug Fixes and Enhancements

SDK: It was not possible to get a CLxUser_SchematicNode() interface from a Schematic item node.

SDK: ILxSchematicNodeConnection has been replaced with ILxSchematicNodeChannel in the Schematic SDK.

• ID 53503 - Scripting: Disconnecting graph connections using the bitshift-operator (<<) caused an error.

• ID 53713 - Scripting: Several vertex and polygon properties returned values from the wrong components.

• ID 53741 - Scripting: Querying edge selection resulted in a MeshEdges object has no attribute _mesh error.

• ID 53844 - SDK: It was not possible to put geometry into setup mode when using a CharacterBox kit script.