Gordon_S; If the models you want to export are the excellent houses in Vue that Alain Gracia created, it was a stipulation he requested of e-on at the time the contracted them; no redistribution, period. That was no issue in Vue4, as nothing exported. If it is newer content, then it was the decision of the content creator to not allow export. On that first import into Vue, you'll find a check box for blocking export. The 'encryption' iloco is...discussing, as it were... is nothing but =KEY ENCRYPTION= (that was for others who seem to have problems parsing things). If you've bought any of the SolidGrowth plants from the e-on site, you know you had to wait a day or three for the installation code, which was keyed to the reg code of -your- copy of Vue (As an example: I could give my zip of the orange tree, and the reg key, to a friend, and it would throw an invalid code error and not work, since it wasn't my copy of Vue it was installed on). What has happened since Cornucopia went live is that they've automated the process; the reg key is embedded into the content you buy at download time, so that it only installs on your chosen version of Vue. And you don't have to wait 2 days to use your purchase, and don't have to enter a couple hundred 20 digit codes if you have to do a reinstall. That is =all= the so-called 'encryption scheme' does. It has nothing to do with whether an object can be exported or not. With the exception of the SolidGrowth plants (which is proprietary e-on knowledge), that decision is in the hands of the content creator/provider. (And just to be scrupulously fair, which is frankly beginning to get a bit wearing, the first three 5.08 updates that enabled the key encryption scheme broke Vue to the point that =all= the export functions were....for lack of a better phrase, fubared. That has long since been fixed).