The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly.

The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly.

The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly.

It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog.

It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog.

It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog.

It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog.

It is now possible to set the input labels for VEX operators and custom subnet operators. This is done on the Input/Output page of the Type Properties dialog.

Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors.

Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors.

Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors.

Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors.

Fixed bug where entering 0...3 or 2..3..4 in a numeric parameter results it in being accepted. However, it was unclear as to what the actual interpretation was. We now properly flag this as an expression which evaluates with errors.

Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message.

Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message.

Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message.

Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message.

Fixed Halo crashes that would happen if the raster failed to allocate for some reason. It now produces and error with an informative message.

Composable transforms do not work correctly if the input has a different resolution from the current node. This case was quite common with a transform or a scale on the foreground input to a composite or layer. In this case, we disable the composing of transforms.

Composable transforms do not work correctly if the input has a different resolution from the current node. This case was quite common with a transform or a scale on the foreground input to a composite or layer. In this case, we disable the composing of transforms.