Hi, this is Chad at DAZ Productions: I just got a heads-up on this thread and wanted to take the opportunity to check in. Thanks for the compliments and feedback, everyone. I'm happy to hear that so many of you are happy with your purchase of Victoria 2. (As usual, there's a money-back satisfaction guarantee if you're not.) It seems that the issue that needs to be addressed is not product value and customer satisfaction, however. So on to the subject of distributing Victoria2-derivative files... First off, let me just say that we're in the process of posting this information (what's legal and what's recommended for those wanting to distribute these files) on our website in the F.A.Q. section. It should be available there later today or tomorrow. Also, I'd like to say that we do look forward to artists creating and distributing V2-derivative products. (We will be both creating and brokering some in the near future.) In the meantime, I'll give a quick run-down of some of the possibilities. (Many of these are redundant with what some of you have already mentioned in this thread; thank you for helping to explain these issues.) -Poses (.pz2, .fc2, .hd2) These can be distributed with morph channels included. -Characters and Scenes (.cr2, .pz3) These contain data exclusive to the Victoria2 product itself, and therefore cannot be distributed (with or without modification) any more than they can for other artists' Victoria1-derivative files. -Maps (binary formats) These cannot be distributed if they are derived from DAZ-sold maps either, though templates are freely availabe to use in the creation of third-party maps. Presuming that the map is made "from scratch" it is legal to distribute, though it should not be accompanied by a V2 .cr2 referencing it, of course. (We recommend using MAT Pose files, so that the map will be easy to apply to Victoria 1, 2, or any derivative characters using that model.) -Morphs (.obj, .cr2, etc.) Here's the tricky one, with 3 scenarios: 1) If you're distributing out a strictly V2 morph-combo, then Pose files will work fine. [See Poses, above.] 2) If you're creating out a strictly "from scratch" Victoria morph (that you can create from the freely distributable V2 .cr2 available on our website), then you can either distribute it in a Victoria1-derivative .cr2 file, or as a vertex-only .obj file. The V1 .cr2 file could be used itself by the end user, or transferred to V2 by the end user (especially easy with a utility like MorphManager). The vertex-only .obj file can be applied to either V1 or V2 by the end user, and is easy to create (in MorphSqueeze, MorphMasher, or a text-editor). 3) If you're creating a custom morph target using one or more V2-exclusive morphs as a starting point then there's only one way I can currently think of to legally distribute this. Others may be discovered in the future. You can dial up the morphs you wish to start from, and record which specific morphs you used and at what values. Then create your custom morph as you normally would. Once you have it, apply it to V2 at a value of 1 and then "inverse out" the morph values you used as your starting point. (ie: dial them negatively at the same value that use originally used. Remember that two negatives make a positive.) Then, export the new .obj, which at this point only includes the changes truly original to your morph, and make it a vertex-only .obj file. You can now distribute your hybrid morph as a Pose file accompanied by a squished morph file. When the end-user uses both together they have your character. Hope that helps. Like I said, this type of thing will be covered more thoroughly in the new FAQ section on our site soon. Thanks for the feedback everyone, -Chad Smith DAZ Productions