be aware that when you switch between Daily Builds and Alpha7.2 any masking render element will behave differently.
This is due to the fact that within the advanced options rollout of the materials “the intention” of the mask option has changed into the opposite from alpha to Daily build. It changed from “visible” towards “invisible”.
Very annoying if you render out an animation…
Maybe it is wise to switch it back to “visible” because:
alpha users will experience the same thing as they use their old files with the new commercial build.
users material libraries made with alpha 7 will have the same problem with newer builds.
Or is it possible to add some extra code that the switch between the older and newer builds will take visible or invisible masks into account?
there is supposed to be a check that will invert the value when first loaded in new version… I must look why it is not working. But only single report is necessary.
the build in check is working from alpha 7.2 towards daily builds. And gives the expected behaviour.
But not from daily builds towards Alpha 7.2.
-Create a file in Alpha 7.2 with two objects. Attach to both of them a standard corona mtl. One with invisible mask (Object A) unchecked and one with the option checked (Object B).
-When rendering the Mat ID pass, Object A will be visible and Object B not.
-Save the file
-Open the same file with a daily Build and render the file. Object A will be visible and Object B not.
-Save the file.
Open the same file again with Alpha 7.2 and render out the Mat ID pass.
Result: Object A is not visible and Object B is.
is active! all possible max parameter are tested! don´t have alpha channel in Framebuffer! or any other element!
sure is corona! the problem appers after last DB update!
