Solid Angle has released Arnold 5.2, the latest update to the production renderer, adding support for texture baking, a new Sheen effect for rendering fuzzy surfaces, and built-in support for Cryptomatte.
There is also a new cellular noise shader; and a new energy-preserving Sheen function in the Standard Surface shader, designed to mimic the look of surfaces with microfibres, like peach fuzz or velvet.
Other new features include a new edge detection control in the toon shader added in Arnold 5.1; plus the option to generate ID passes for volumes, and Z-depth AOVs for volumes in standard as well as deep files.
Solid Angle has also updated its integration plugins for DCC tools to take advantage of the new features in Arnold 5.2, releasing MtoA 3.1 for Maya, MAXtoA 2.1 for 3ds Max and C4DtoA 2.4 for Cinema 4D.
The goal of any visualization process is to produce visual representations ofthe data. The visual representations are shown in modules called views.Views provide the canvas on which to display such visual representations,as well as to dictate how these representations are generated from the raw data.The role of the visualization pipeline is often to transform the data so thatrelevant information can be represented in these views.
Referring back to the visualization pipeline fromSection 1.2, views are sinks that take in input databut do not produce any data output (i.e., one cannot connect other pipelinemodules such as filters to process the results in a view). However,views often provide mechanisms to save the results as images or in other formatsincluding PDF, VRML, and X3D.
Rendering Views are views that render geometries or volumes in a graphical context. The Render View is one such view. Other Render View-based views, such as Slice View and Quad View , extend the basic render view to add the ability to add mechanisms to easily inspect slices or generate orthogonal views.
Chart Views cover a wide array of graphs and plots used for visualizing non-geometric data. These include views such as line charts ( Line Chart View ), bar charts ( Bar Chart View ), bag charts ( Bag Chart View ), parallel coordinates ( Parallel Coordinates View ), etc.
Comparative Views are used to quickly generate side-by-side views for parameter study, i.e., to visualize the effects of parameter changes. Comparative variants of Render View and several types of the Chart Views are available in ParaView.
New views can be created by splitting theview frame using the Split View controls at the top-right corner of theview frame. Splitting a view divides the view into two equal parts, eithervertically or horizontally, based on the button used for the split.On splitting a view, an empty frame with buttons for all known typesof views is shown. Simply click on one of those buttons to create a new view ofa chosen type.
You can move views by clicking and dragging the title bar for the view (orempty view frame) and dropping it on the title bar on another view (or emptyview frame). This will swap the positions of the two views.
Similar to the notion of active source, there is a notion of activeview .Several panels, toolbars, and menus will update based on the active view. TheDisplay properties section on the Properties panel, for example,reflects the display properties of the active source in the active view.Similarly, the eyeball icons in the Pipeline Browser show the visibilitystatus of the pipeline module in the active view. Active view is marked in theUI by a blue border around the view frame. Only one view can be active at any timein the application.
Besides being able to create multiple views and laying them out in a pane,paraview also supports placing views in multiple layouts underseparate tabs. To create new tabs, use the button in the tab bar. You can close a tab, which will destroy all views laid outin that tab, by clicking on the button.To pop out an entire tab as aseparate window, use the button on thetab bar.
The active view is always present in the active tab. Thus, if you change theactive tab, the active view will also be changed to be a view in the active tablayout. Conversely, if the active view is changed (by using the PythonShell , for example), the active tab will automatically be updated to be the tabthat contains the active view.
You can make the views of the active layout fullscreen by using View > Fullscreen (layout) (or using the F11 key).You can also make the active view alone fullscreen by using View > Fullscreen (active view) (or using CTRL + F11 keys).To return back to the normal mode, use the Esc key.
When a new view is created, it is automatically made active. You can manuallymake a view active by using the SetActiveView function. Several of thefunctions available in pvpython will use the active view when noview is passed as an argument to the function.
When using Python Shell in paraview, if you create a new view,it will automatically be placed in the active tab by splitting the active view.You can manually control the layout and placement of views from Python too, usingthe layout API.
Just like parameters on pipeline modules, such asreaders and filters, views provide parameters that can be used for customizingthe visualization such as changing the background color for rendering views andadding title texts for chart views. These parameters are referred to as ViewProperties and are accessible from the Properties panel in paraview.
Similar to properties on pipeline modules like sources and readers, viewproperties are accessible from the Properties panel. Theseare grouped under the View section. When the active view is changed, theProperties panel updates to show the view properties for the active view.Unlike pipeline modules, however, when you change the view properties, theyaffect the visualization immediately, without use of the Applybutton.
To understand the reasoning behind that, we need to understand why theApply action is needed in the first place. Generally, executing a dataprocessing filter or reader is time consuming on large datasets. If the pipelinemodule keeps on executing as you are changing the parameter, the user experiencewill quickly deteriorate, since the pipeline will keep on executing withintermediate (and potentially invalid) property values. To avoid this, we havethe Apply action. This way, you can set up the pipeline properties to yourliking and then trigger the potentially time consuming execution.
Since the visualization process in general focuses on reducing data togenerate visual representations, the rendering (broadly speaking) is less time-intensivethan the actual data processing. Thus, changing properties that affectrendering are not as compute-intensive as transforming the data itself. For example,changing the color on a surface mesh is not as expensive as generating the meshin the first place. Hence, the need to Apply such properties becomes lessrelevant. At the same time, when changing display properties such as opacity,you may want to see the result as you change the property to decide on the finalvalue. Hence, it is desirable to see the updates immediately.
Display properties refers to available parameters that control how data from apipeline module is displayed in a view, e.g., choosing to view the output mesh as awireframe, coloring the mesh using a data attribute, and selecting which attributesto plot in chart view. A set of display properties is associated with aparticular pipeline module and view. Thus, if the data output from a source isshown in two views, there will be two sets of display properties used to controlthe appearance of the data in each of the two views.
Display properties are accessible from the Display section on theProperties panel. When the active source or active view changes, thissection updates to show the display properties for the active source in theactive view, if available. If the active source produces data that cannot beshown (or has never been shown) in the view, then the Display propertiessection may be empty.
The Render View is the most commonly used view in ParaView. It is used to rendergeometries and volumes in a 3D scene. This is the view that you typically thinkof when referring to 3D visualization. The view relies on techniques to map datato graphics primitives such as triangles, polygons, and voxels, and it rendersthem in a scene.
Most of the scientific datasets discussed in Section 3.1are composed of meshes. These meshes can be mapped to graphics primitives usingseveral of the established visualization techniques. That is, you can compute theouter surface of these meshes and then render that surface as filled polygons, you canjust render the edges, or you can render the data as a nebulous blob to get a betterunderstanding of the internal structure in the dataset. Plugins, likeDigital Rock Physics, can provide additional ways of rendering data using advancedtechniques that provide more insight into the data.
Surface rendering methods provide general rendering by rendering a surface mesh for the dataset. For polygonal datasets (Section 3.1.8), this is simply the raw data. In cases of other datasets including structured (Section 3.1.3, Section 3.1.4, Section 3.1.5) and unstructured (Section 3.1.7) grids, this implies extracting a surface mesh for all external faces in the dataset and then rendering that mesh. The surface mesh itself can then be rendered as a filled surface or as a wireframe simply showing the edges, etc.
Slice rendering is available for uniform rectilinear grid datasets (Section 3.1.3) where the visualization is generated by simply rendering an orthogonal slice through the dataset. The slice position and alignment can be selected using the display properties.
Each of these techniques are referred to asrepresentations. Whenavailable, you can change the representation type from the display properties on theProperties panel or using the Representation Toolbar .
Usually in ParaView, you are interacting with a 3D scene. However, there are cases whenyou are working with a 2D dataset such as a slice plane or a 2D image. In suchcases, paraview provides a separate set of interaction optionssuitable for 2D interactions. You can toggle between the default 3D interactionoptions and 2D interaction options by clicking the 2D or 3D button inthe view toolbar. The default interaction options for 2D interactions are asfollows:
7fc3f7cf58