Quote - > Quote - 'Copy protection' ... was implemented to permit content creators to decide for themselves how stringent they wanted to protect their work (and to cover e-on from a legal standpoint as well, considering how many frivolous DMCA suits are currently floating around).

Interesting feature indeed-- though I do find it interesting, I know of no other 3D application which uses 'copy-protected' object files in such a way. You would think at least one other serious 3D application would want to provide such an obvious feature seeing how it would protect them from 'frivolous DMCA' lawsuits. (I'm not including CAD programs which occasionally use encryption for transferring files to and from service bureaus).

Frankly, I think copy protection a bad business decision made a long time ago, and now they're stuck with it. The simple fact is, there are no successful 3D programs which care so greatly for their own object model DMCA issues (if that is indeed the real argument for 'copy protecting').

Of course, I'm more than willing to entertain good reasons for such, but those presented certainly don't make a case to me.

Most other 3D apps are content creators; Vue is more an environment generator and end stage renderer. A modeler -has- to be able to output multiple formats; renderers only have to be able to accept those formats. It may be bad business; pirates weren't going to pay for what they stole to begin with, so claiming lost revenue is nonsense. However, I have also had things I have written stolen, so I can fully appreciate the desire to protect something that has a good bit of time invested into it.