@Azath - Oh I know about the big brother stuff, it's just one of many reasons why it ain't getting internet access. I wasn't referring to that though. I was just puzzled how SM got Cycles into Poser in a licence-friendly way, and to be honest, I'm even more puzzled now I've seen Wolf's reply!

@Wolf - So are you saying they took the code, edited it, forked it, then bundled it with Poser as part of it's distribution? I was always under the impression that you cannot bundle the code as part of a proprietary product. Blender Game Engine users themselves face that situation when it comes to distributing a game made with the Blender Game Engine, cause the code of the engine itself cannot be closed in any way, it has to be open.

So I'm really puzzled how SM got around that. Surely the same technique would be of benefit to Blender Game Engine games that users would like to protect. It sounds as if you're saying SM have somehow managed to take the open code and bundle it into a closed product. Forking the source and making it available doesn't, as far as I'm aware, remove the restriction of it being included as part of a closed product. I always thought that such measures demand that the whole program using the code, whether as-is or modified, follow the same licence as the code that was used, or "extracted" as you put it. No doubt SM would not have done whatever they did it were not permitted, but I'm absolutely baffled how they did it - lol

Regards DAZtoBlender8, yup, looks awesome. I'll definitely pick it up if I can get DAZ Studio to export under WINE. You still do puzzle me in you fear of it breaking though. That pipeline cannot break, because your current DS, the plugin, and Blender can all be backed up to disk and reinstalled any time you wish. And even if an update introduced a bug, you would still be able to go back to the working version.