Besides, the noai tag shouldn’t be an opt-in in the first place, but people should manually opt-out of it IF they want their content to be used for AI generators.
This is the first time I use this forum, but as someone on the other side of the conversation I wanted to also add my two cents.
Section 17 of the new ECLA [Epic Content License Agreement]
17. Artificial Intelligence
For purposes of this Agreement, “Generative AI Programs” means artificial intelligence, machine learning, deep learning, neural networks, or similar technologies designed to automate the generation of or aid in the creation of new content, including but not limited to audio, visual, or text-based content. You shall not collect, aggregate, mine, scrape, or otherwise use NoAI Content
(i) in datasets utilized by Generative AI Programs; (ii) in the development of Generative AI Programs; or (iii) as inputs to Generative AI Programs.
I was a master student on Machine Learning that made use of the flexibility of Unreal to use assets and create worlds in which I would virtually train my Ai using Reinforcement Learning/Imitation Learning the Tesla way. I came to EPIC knowing 0 >>Zero about game development. But thanks to UE5 I was able to create a great world after one year and half of trial and error. Testament to all the trailers and teasers about how easy and great UE5 is.
Due to this new agreement I do not see how someone like me would be able to save significant time of development, as you pointed it out yourself, the general consensus seems to be to tag everything [NoAi] by default.
Not everyone is using assets to create datasets duplicating and modifying your creations. There are some of us that use UE5 to create worlds like any other developer; but then, these worlds are intended to be played by Ai not Timmy from Ohio.
Anyhow. Just my 2 cents.
Thank you for the message. I am happy I finished my project before I had to clicked “I agree”. Issac it is.