With Unity 5.2p1, the API for BaseMeshEffect has changed yet again, this time requiring us to implement Code (csharp): public abstract void ModifyMesh (VertexHelper vh); The previous method that took a Mesh is still there, too: Code (csharp): public virtual void ModifyMesh (Mesh mesh); (which was much nicer to work with and more efficient for our use cases). Is this API stable now? We're changing all of our code for the 3rd or 4th time to account for this API changing so frequently. Can we please implore you great folks at UT to settle on a direction here and stick with it? We can adapt to whatever direction you need to go, but it has been changing so often that it has become really painful to upgrade Unity versions. Do we think this new API is "the one" for a while, or should we expect more changes here soon? Also, is there any longer any point in overriding the method takes a Mesh? Since the one that takes a VertexHelper is abstract we're stuck having to override that guy, so why is the other one still there? Also, are there any code samples for how to properly use this new version that takes VertexHelper? We are clearing it and re-adding the stream on every frame which sounds wasteful. Are we supposed to somehow keep that "stream" from one frame to the next? And what is stream-oriented about it, anyway? It's exposed as a simple List<UIVertex> to us. Thanks very much!