Since some recent update, Starling now uses non zero default stencil value. If graphics context is shared and user calls Context3D.clear() and Starling.nextFrame() manually, there is no way no specify of even get the initial stencil value expected by Starling. In my case, Context3D.clear() was called with all default parameters and after placing any masked display object i would get black screen.
Can you please consider making Painter.DEFAULT_STENCIL_REFERENCE_VALUE constant a public property or, at least, make it a public constant, so Starling.nextFrame() caller can take it into account?
You are perfectly right, it's important that this value is available for external access. I just renamed it to DEFAULT_STENCIL_VALUE and made it public.
Hello,
Since some recent update, Starling now uses non zero default stencil value. If graphics context is shared and user calls
Context3D.clear()
andStarling.nextFrame()
manually, there is no way no specify of even get the initial stencil value expected by Starling. In my case,Context3D.clear()
was called with all default parameters and after placing any masked display object i would get black screen.Can you please consider making
Painter.DEFAULT_STENCIL_REFERENCE_VALUE
constant a public property or, at least, make it a public constant, soStarling.nextFrame()
caller can take it into account?Regards, Alexander