There is a subtle change in the way object lists are built for renderers (i.e. .ifd files, .rib files, etc.) Previously, the status of the display channel/display flag was tested after the object was queued for the render. This meant un-necessary work was being done. Now, the display flag/display channel is tested at the outset resulting in less work for objects which aren't displayed.

In most cases, this will not affect existing renders. The only case where this may have an effect is if the render script was being modified by hand to attempt to garner some information about an object which wasn't being rendered, but had it's geometry sent down to the renderer.

There is a subtle change in the way object lists are built for renderers (i.e. .ifd files, .rib files, etc.) Previously, the status of the display channel/display flag was tested after the object was queued for the render. This meant un-necessary work was being done. Now, the display flag/display channel is tested at the outset resulting in less work for objects which aren't displayed.

In most cases, this will not affect existing renders. The only case where this may have an effect is if the render script was being modified by hand to attempt to garner some information about an object which wasn't being rendered, but had it's geometry sent down to the renderer.

There is a subtle change in the way object lists are built for renderers (i.e. .ifd files, .rib files, etc.) Previously, the status of the display channel/display flag was tested after the object was queued for the render. This meant un-necessary work was being done. Now, the display flag/display channel is tested at the outset resulting in less work for objects which aren't displayed.

In most cases, this will not affect existing renders. The only case where this may have an effect is if the render script was being modified by hand to attempt to garner some information about an object which wasn't being rendered, but had it's geometry sent down to the renderer.

There is a subtle change in the way object lists are built for renderers (i.e. .ifd files, .rib files, etc.) Previously, the status of the display channel/display flag was tested after the object was queued for the render. This meant un-necessary work was being done. Now, the display flag/display channel is tested at the outset resulting in less work for objects which aren't displayed.

In most cases, this will not affect existing renders. The only case where this may have an effect is if the render script was being modified by hand to attempt to garner some information about an object which wasn't being rendered, but had it's geometry sent down to the renderer.

There is a subtle change in the way object lists are built for renderers (i.e. .ifd files, .rib files, etc.) Previously, the status of the display channel/display flag was tested after the object was queued for the render. This meant un-necessary work was being done. Now, the display flag/display channel is tested at the outset resulting in less work for objects which aren't displayed.

In most cases, this will not affect existing renders. The only case where this may have an effect is if the render script was being modified by hand to attempt to garner some information about an object which wasn't being rendered, but had it's geometry sent down to the renderer.

The following functions were removed from the cop2 VEX context since they are unsafe and produce un-predictable results:

• matrix optransform(string, float)
• matrix optransform(string)
• vector toNDC(string, vector)
• vector toNDC(vector)
• float ch(string)
• float ch(string, float)
• string ch(string)
• string ch(string, float)

This may cause existing COP2 VEX functions to fail (if they used these functions).

The following functions were removed from the cop2 VEX context since they are unsafe and produce un-predictable results:

• matrix optransform(string, float)
• matrix optransform(string)
• vector toNDC(string, vector)
• vector toNDC(vector)
• float ch(string)
• float ch(string, float)
• string ch(string)
• string ch(string, float)

This may cause existing COP2 VEX functions to fail (if they used these functions).

The following functions were removed from the cop2 VEX context since they are unsafe and produce un-predictable results:

• matrix optransform(string, float)
• matrix optransform(string)
• vector toNDC(string, vector)
• vector toNDC(vector)
• float ch(string)
• float ch(string, float)
• string ch(string)
• string ch(string, float)

This may cause existing COP2 VEX functions to fail (if they used these functions).

The following functions were removed from the cop2 VEX context since they are unsafe and produce un-predictable results:

• matrix optransform(string, float)
• matrix optransform(string)
• vector toNDC(string, vector)
• vector toNDC(vector)
• float ch(string)
• float ch(string, float)
• string ch(string)
• string ch(string, float)

This may cause existing COP2 VEX functions to fail (if they used these functions).

The following functions were removed from the cop2 VEX context since they are unsafe and produce un-predictable results:

• matrix optransform(string, float)
• matrix optransform(string)
• vector toNDC(string, vector)
• vector toNDC(vector)
• float ch(string)
• float ch(string, float)
• string ch(string)
• string ch(string, float)

This may cause existing COP2 VEX functions to fail (if they used these functions).