Sorry Bijou, I don't see what you're saying. Some of the functionality of Studio is limited at this time because it's a pre-beta release. So some figure functionality and morph manipulation capability is missing, and some of the figures come in looking odd. That (hopefully) will be fixed for the beta release and fully functional for the full release. Judging that now on a pre-release piece of software is mistaken. However, I agree completely with you about evaluating your own direction. Alpha software is "not" a judge of the final product, never has been, never will be. You should see the alpha versions of games and other software for a good clue here, they only represent the finished software in basic form. Most of the code is present, yes, but only a small amount is active. If the program won't run on your system then judging it as useless is again mistaken. It's not FINAL yet, it's an Alpha (does anybody actually understand what Alpha means?) Report the problem to Daz and explain what error message (if any) you get, your system spec and what precisely happens and what you do to cause the crash. They'll perhaps try to fix it, or manage to identify what causes the problem and explain it to you. As has been said in other threads here, Studio crashes can be caused by a variety of things, identifying that "thing" is the important part. If you are expecting to be able to work with Studio and use it in a production pipeline as part of your earnings now, then quite frankly anyone trying that trick is playing with fire. It's not ready for that yet, regardless of what a certain person is trying to beat into people. Your system not being a scrapheap is immaterial, something is conflicting. Same as with the release of Poser 5 there were massive conflicts for many people and a 2 ghz plus computer was seen as essential. I know someone running studio on a p3 500 quite happily and it's far more stable than Poser4, and yet another who can't even get the thing to install. It's test software, being tested to determine problems. If new figures are introduced for Studio (distinctly possible depending on the direction of the software) then yes, you need to evaluate whether you want or need to move up to these and spend yet more money. Thus far I've resisted the version 3 figures from Daz because I have no use for them. Same thing applies to any other models. If I don't "need" it, I won't buy it. Studio is no different. I won't buy figures or models I don't need and would hope to be able to use my existing libraries as best as possible - with a view to converting them if necessary. Free updates are distinctly possible. I know several vendors who updated their products for Poser 5, and several more who updated their products for the version 3 figures - releasing these updates as "free". Daz may or may not offer the same facility. Mostly though I should imagine that a new control figure (cr2 or in this case .daz) would be released rather than a new geometry model, because mostly we work from referenced geometry not imported geometry. Daz may already have plans in this regard and it wouldn't be the first time that they released an updated reference model using existing geometry. It's impossible to make those judgements at this stage of development because only parts of Studio are currently functional. The new dynamic morph system that Rob is talking about as a Studio replacement for inj morphs sounds fascinating, but it's not ready yet. Inj morphs still work the same, but studio employs them differently, dynamically. So there are changes there. I'm not trying to argue with you, just say that making assumptions about what will or won't work at this stage is like predicting the lottery numbers. The only people who know are the development team and the project co-ordinator. Weight mapping isn't uvmapping. Weight mapping is a joint control system that tells the software what polygons stretch and move, and which ones stay in place. So you wouldn't need to re-purchase clothing and textures all over again, your existing clothing would work and existing textures would apply to them because the uvmaps would be the same. What would change is the nature of the geometry being referenced and the information in the control file. Same as it is with Poser 5 dynamic cloth. You export an existing piece of clothing as a solid object. Import it to use in the cloth room, and wow, the uvmap is intact. Studio can work the same way. So there's no need to re-purchase anything. NEW models are a different matter all together, you will probably buy those for poser anyway - or studio if it eventually suits your work style - unless you're trying to say that you'll never buy clothing, figures or textures again, ever.