Draw the inside,not a surface through it
An isosurface picks one value and shows where it lives. Volume rendering shows every value at once, weighted by the opacity you set.
A ray is cast per pixel and accumulates colour and opacity through the whole volume, not just its skin.
Plumes, gradients, diffuse regions — anything with no obvious surface to draw a contour on.
It is for seeing where something is. Read numbers off it with a probe, not by eye.
One dropdownstarts it
Switching to volume rendering takes about four seconds. Making it show something worth looking at is the rest of the afternoon.
Your data has to be a scalar field on a 3D grid for this to be offered at all. Image data and rectilinear grids work directly; unstructured meshes are supported but slower, and a common move is to resample onto a uniform grid first with Resample To Image.
It is allthe transfer function
Volume rendering has one control that matters and several that do not. The opacity curve is the one that matters.
The transfer function maps scalar values to a colour and an opacity. Colour is mostly taste. Opacity is the entire result: leave everything semi-opaque and you get fog, make everything sharp and you have reinvented the isosurface badly. What you want is a narrow band of opacity around the values you care about, and near-zero everywhere else.
Set near-zero opacity over the background range so the interesting values are the only ones you see.
Cool-to-warm is the safe default. Rainbow maps invent structure that is not in the data.
Export the colour map as a preset so the same field is drawn identically across runs and figures.
Look at the histogram behind the curve in the Color Map Editor before touching anything. If most of your cells sit in a narrow spike, a linear opacity ramp will be dominated by that spike and you will see nothing else. Drag the control points so the ramp lives where the interesting values are, not where the bulk of the data is.
Three dials,in this order
Volume rendering is expensive, and it gets expensive suddenly rather than gradually.
Shrink the data first — Extract Subset or a coarser resample beats every rendering option. Then raise the Scalar Opacity Unit Distance, which is the sampling step: larger is faster and grainier. Only then worry about shading, which adds depth cues but costs a normal calculation at every sample. On a rented machine with a GPU, the card does the raycasting, so the thing that actually limits you is usually how much of the dataset fits in its memory.
ParaView isalready built
Nothing here needs compiling. Pick a machine, and these two commands put it on there.
$ dxflow workflow create --identity paraview hub://paraview
$ dxflow workflow start paraview