The display driver for prman (provided by proto_install) has been modified. The new driver is improved in that it now supports output of floating point channels, short channels without quantization directly to mplay. It is also tile based (as opposed to scanline based). This means that more accurate data will be presented in mplay in a more interactive fashion.

However, at the current time, the new driver will no longer output to PRISMS .pic files. It will only output images to mplay.

The display driver for prman (provided by proto_install) has been modified. The new driver is improved in that it now supports output of floating point channels, short channels without quantization directly to mplay. It is also tile based (as opposed to scanline based). This means that more accurate data will be presented in mplay in a more interactive fashion.

However, at the current time, the new driver will no longer output to PRISMS .pic files. It will only output images to mplay.

The display driver for prman (provided by proto_install) has been modified. The new driver is improved in that it now supports output of floating point channels, short channels without quantization directly to mplay. It is also tile based (as opposed to scanline based). This means that more accurate data will be presented in mplay in a more interactive fashion.

However, at the current time, the new driver will no longer output to PRISMS .pic files. It will only output images to mplay.

The display driver for prman (provided by proto_install) has been modified. The new driver is improved in that it now supports output of floating point channels, short channels without quantization directly to mplay. It is also tile based (as opposed to scanline based). This means that more accurate data will be presented in mplay in a more interactive fashion.

However, at the current time, the new driver will no longer output to PRISMS .pic files. It will only output images to mplay.

Fixed bug introduced in 6.1.147 where CaptureEdit and CapturePaint SOPs need not properly update themselves when captured bones were renamed.

Fixed bug introduced in 6.1.147 where CaptureEdit and CapturePaint SOPs need not properly update themselves when captured bones were renamed.

Fixed bug introduced in 6.1.147 where CaptureEdit and CapturePaint SOPs need not properly update themselves when captured bones were renamed.

Fixed bug introduced in 6.1.147 where CaptureEdit and CapturePaint SOPs need not properly update themselves when captured bones were renamed.

Fixed bug introduced in 6.1.147 where CaptureEdit and CapturePaint SOPs need not properly update themselves when captured bones were renamed.

Fixed bug where doing a "Create Parameter" or "Create Constant" operation from the MMB menu on a VOP input button would sometimes cause the new VOP to appear way up and to the left of the originating VOP.

Fixed bug where doing a "Create Parameter" or "Create Constant" operation from the MMB menu on a VOP input button would sometimes cause the new VOP to appear way up and to the left of the originating VOP.

Fixed bug where doing a "Create Parameter" or "Create Constant" operation from the MMB menu on a VOP input button would sometimes cause the new VOP to appear way up and to the left of the originating VOP.

Fixed bug where doing a "Create Parameter" or "Create Constant" operation from the MMB menu on a VOP input button would sometimes cause the new VOP to appear way up and to the left of the originating VOP.

Fixed bug where doing a "Create Parameter" or "Create Constant" operation from the MMB menu on a VOP input button would sometimes cause the new VOP to appear way up and to the left of the originating VOP.

There is a new "On Input Changed" script on the Events page of the Type Properties dialog. This script is run whenever an input to an operator of the given type is changed. The script is passed the full path of the node that was changed, and the operator type of the node that was changed.

There is a new "On Input Changed" script on the Events page of the Type Properties dialog. This script is run whenever an input to an operator of the given type is changed. The script is passed the full path of the node that was changed, and the operator type of the node that was changed.

There is a new "On Input Changed" script on the Events page of the Type Properties dialog. This script is run whenever an input to an operator of the given type is changed. The script is passed the full path of the node that was changed, and the operator type of the node that was changed.

There is a new "On Input Changed" script on the Events page of the Type Properties dialog. This script is run whenever an input to an operator of the given type is changed. The script is passed the full path of the node that was changed, and the operator type of the node that was changed.

There is a new "On Input Changed" script on the Events page of the Type Properties dialog. This script is run whenever an input to an operator of the given type is changed. The script is passed the full path of the node that was changed, and the operator type of the node that was changed.

It is now possible to drag and drop string parameters from within a parameter dialog. It is also possible to drag and drop parameters that are disabled.

It is now possible to drag and drop string parameters from within a parameter dialog. It is also possible to drag and drop parameters that are disabled.

It is now possible to drag and drop string parameters from within a parameter dialog. It is also possible to drag and drop parameters that are disabled.

It is now possible to drag and drop string parameters from within a parameter dialog. It is also possible to drag and drop parameters that are disabled.

It is now possible to drag and drop string parameters from within a parameter dialog. It is also possible to drag and drop parameters that are disabled.

When a Transformer handle from a contained SOP is promoted to be bound to the parameters of a top-level subnet, the scale and rotate operations now behave properly.