Quote from: Tangled-Universe on May 04, 2020, 06:24:54 AMQuote from: WAS on May 03, 2020, 01:58:51 PMSpeaking of that cause Oshyan just tossed a key at me, I never even actually agreed to any agreements or were shown them before receiving a license.
Every time you install TG you explicitly agree with the EULA.
Different Agreement, Martin. It doesn't even contain the VDB segment, and you can't legally have two contradicting agreements, to begin with. It creates a nullified agreement due to liabilities.
And again, all contracted work is technical presale of services/assets. It's not you working for a company, etc, and you can't extended agreements on them.
---
And honestly how is this going to help Terragen except inhibit sales? Also, how is it going to protect Terragen when exported VDBs are as such, an exported VDB. Any VDB can be extensively augmented until it doesn't resemble the original, and used for thousands of iterations, and you'll never know. And as far as VDBs out there that you can't cover with a new agreement, how does it help? They can all be used for almost limitless variations and tweaking.
---
Further more applying restrictions to an open format which doesn't have any, anywhere else, is really shady. Just cause TG exports it? What does TG do in the OpenVDB that warrants any uniqueness? Especially using basic perlin, which is available in other software? Heck if no one is using easy clouds, you could very well mistake perlin from other software as TG generated and opena can of worms. TG Easy Clouds are easy to spot, but basic perlin noises in VDB format?
---
Seems the damage has been done, and trying to attack consumers over it is wrong. The mistake was made to not restrict them, and it shouldn't be changed because you're hurting. That's just more fuel for the TG fire.