Hi, Just to address a few questions that have been asked on this forum and elsewhere:- Anton is correct about the connection between Drops and the Python interface, we are, with Poser, dependent on the Python functionality to launch the plug-in. Having said that, we should also point out that a considerable portion of the code (95% or more) is compiled binary, and for the most part is neither Windows nor Poser specific. We don't forsee any great problems in porting most of the plugin code to other platforms or applications. In the Poser implementation of Drops, Python is a necessity to launch the plugin, but we also voluntarily chose (early on) to use Python/Tk to implement the user interaface. Although this initially gave us a fairly simple cross-platform implementation, a large number of the problems that we've had to tackle or bypass seem to have been caused by this portion of the code. In future development we will certainly be looking at the benefits of re-implementing the interface using native Windows and Macintosh interfaces. The company fully recognises the significant portion of Mac users within the community. We did not have the resources, at the outset, to develop across platforms, but we intend to begin development and porting to the Mac platform for Poser in the near future. Replacing the Tk/Python interface with a native platform interface is also an essential step towards this as we are aware of some reports of fundemental compatiblity problems with Poser's Python/Tk interface on the Mac. Likewise, we hope to be ready to port to any future Poser/Studio implementaions on Linux. So far as DAZ Studio is concerned, we full intend to provide a port as soon as the program and interfaces become available. Hopefully we will be able to allow full compatibility with imported Drops/MetaForm enabled Poser scenes. DAZ have indicated that there will be a Python interpreter implmented, but the timing is somewhat questionable. However, DAZ|Studio Python will not be compatible with Poser Python, so there is no prospect of the plugin running directly with Studio. However, while Python is a necessity for us on Poser, we are hoping to be able to avoid it altogether in implementing the plugins for Studio. Instead we look for forward to the opportunity to utilise the main (and more direct) Studio API/SDK which DAZ have also indicated is to be a feature of their application. This should provide a far more suitable and compatible environment for our software. Ideally we will have some opportunity to provide early feedback to help DAZ refine their interfaces. We do, after all, have a very good idea of exactly what we need to make our plugins work. For us, Drops is an essential test bed platform for our interfacing techniques as it's much simpler in functionality than our other plugins. Therefore we intend to continue supporting and refining it and it should be the first port we do to any other platform; Macintosh and Studio users shouldn't have to wait too long to get their hands on it. Little Dragon, So far as MKParticles is concerned we don't possess a copy to be able to compare the features. As we understand, however, it's "apples and oranges". MKParticles seems to distibute (maybe duplicate) Poser props whereas our MetaFlow technology generates simulations of multiple "virtual" metaballs which are only visible when they form a fluid surface (i.e. in "Surfacing" mode). The intent for us was to create liquid flow, fire and smoke simulations and the like. We are doing some work with creating "particle" effects by using texture maps or P5 materials combined with some of the advanced surfacing and mapping features. We should be demonstrating some of this and providing a bit more explanation on the Product Showcase forum imminently. We have future ideas and plans for more advanced dynamic particle and modelling software, but our current goal with these plugins is to push the metaball/isosurface type technology as far it will go. Thank you all for your enthusiasm. Happy blobbing. Bill