- Joined
- Sep 14, 2024
- Messages
- 778
- Solutions
- 3
- Reactions
Policy Update: AI-Assisted Content
AI tools are now part of how a lot of VaM content gets made and shown off. Our existing rules cover most of it, but a few gaps have come up. This update closes them.
1. Photographs of people (real or AI-generated)
The Hub has never allowed a resource to present photographs of a real person as the source or inspiration for a model. We've been asked whether an AI-generated photo of a person who doesn't exist gets around that rule. It doesn't.
2. DLSS5 and other AI rendering enhancements
DLSS5 neural rendering uses AI to make a 3D character look more realistic. This section applies to DLSS5 and to any similar AI-based rendering enhancement that comes along later.
We understand why it's popular, and DLSS5 itself is welcome here. The port, guides, and related plugins can be hosted on the Hub like any other resource. What we don't allow is using it to enhance how other content is presented, for three reasons:
For those reasons:
In short, what you show in a resource listing must be what VaM produces without AI enhancement.
We have been clearing existing resources by hand. If we missed yours, please fix it as soon as possible, especially if DLSS5 was used and not disclosed.
You can share DLSS5 screenshots in these places:
3. Fully AI-generated 3D models
The Hub has traditionally not curated on quality, and that is not changing in general. AI-generated 3D models are the exception for now. The examples we've seen so far have poor geometry and poor textures. We expect that to improve as the technology does.
4. AI-written plugins and apps
If AI was the primary author of your code, please say so in your resource description. This includes "vibe coding" and any workflow where the AI wrote most of the code and you directed it. People deciding whether to use or buy a plugin want to know this, and leaving it out can misrepresent your skills and your ability to support the plugin. We are not asking for disclosure of AI assistance in general, only in this case.
AI and copyright: things you should know
This part is not new policy. More plugins are being written with AI help, and a few misconceptions about copyright keep coming up, so here are the corrections:
"I gave the AI the paid plugin as a reference, but I told it not to use it."
The AI has no "ignore this" switch. Everything you paste in becomes part of what it reasons over, and your instruction is only one more line in that pile. It may avoid copying exact lines, but the original's layout, naming, and approach still steer the result. You can't un-show it something.
"It rewrote everything in its own words, so it's original."
Rewording isn't originality. Copyright can protect how a program is structured and organized, not only its literal text. Building your own plugin that does the same job is fine. Following someone else's implementation with different variable names is not, in the same way that a retold novel is still that novel.
"That was a different chat. This one is fresh."
Not necessarily. Many current AI tools keep memory across sessions and can search your old conversations, and you often can't see exactly what they've kept. Opening a new chat doesn't reliably reset what the tool knows.
None of this means you shouldn't read other people's code. Studying existing plugins is how most VaM developers learned, and we encourage it. The difference is between learning from a plugin and handing it to an AI to reproduce. If the moderation team feels your plugin or app is a derivative of someone else's work because of the way AI was used, we may enforce the relevant licensing requirements, the same as we would for any other derivative.
AI tools are now part of how a lot of VaM content gets made and shown off. Our existing rules cover most of it, but a few gaps have come up. This update closes them.
1. Photographs of people (real or AI-generated)
The Hub has never allowed a resource to present photographs of a real person as the source or inspiration for a model. We've been asked whether an AI-generated photo of a person who doesn't exist gets around that rule. It doesn't.
- Photographs of people, and photorealistic AI-generated images of people, may not be posted anywhere on the Hub. That means resources, the media gallery, forum posts, comments, reviews, and everywhere else.
- It makes no difference whether the person is real or AI-generated. We usually can't tell from the image, and we won't be making that call case by case.
- The only exception is your own profile picture and profile banner.
- Screenshots and renders of VaM content are not photographs and are not affected by this rule.
2. DLSS5 and other AI rendering enhancements
DLSS5 neural rendering uses AI to make a 3D character look more realistic. This section applies to DLSS5 and to any similar AI-based rendering enhancement that comes along later.
We understand why it's popular, and DLSS5 itself is welcome here. The port, guides, and related plugins can be hosted on the Hub like any other resource. What we don't allow is using it to enhance how other content is presented, for three reasons:
- Only users with high-end hardware can take full advantage of it.
- The most common setups are complex or need a paid subscription.
- It changes how content looks enough to misrepresent what a user actually gets when they download the resource.
For those reasons:
- Resources may not require DLSS5 to look or work as presented.
- Images and videos in a resource description may not be captured or enhanced with DLSS5. This applies whether or not the DLSS5 use is disclosed.
- Descriptions of unrelated resources may not promote DLSS5 setups or link to them (for example, "here's how this looks with DLSS5, get it at this link").
In short, what you show in a resource listing must be what VaM produces without AI enhancement.
We have been clearing existing resources by hand. If we missed yours, please fix it as soon as possible, especially if DLSS5 was used and not disclosed.
You can share DLSS5 screenshots in these places:
- Media gallery: in the DLSS5 category only.
- Discord: in the #dlss5-enhanced-screenshots channel only.
- Community Gallery on a resource: select the "DLSS5" category when adding the screenshot. This is the option for creators who want to show their own content running in DLSS5.
3. Fully AI-generated 3D models
The Hub has traditionally not curated on quality, and that is not changing in general. AI-generated 3D models are the exception for now. The examples we've seen so far have poor geometry and poor textures. We expect that to improve as the technology does.
- We may reject AI-generated 3D models that fall below a minimum standard of quality and usability.
- We may also reject AI-generated content if the pipeline behind it appears to involve copyright infringement, for example giving the AI a commercial model and asking for a copy of it.
4. AI-written plugins and apps
If AI was the primary author of your code, please say so in your resource description. This includes "vibe coding" and any workflow where the AI wrote most of the code and you directed it. People deciding whether to use or buy a plugin want to know this, and leaving it out can misrepresent your skills and your ability to support the plugin. We are not asking for disclosure of AI assistance in general, only in this case.
AI and copyright: things you should know
This part is not new policy. More plugins are being written with AI help, and a few misconceptions about copyright keep coming up, so here are the corrections:
"I gave the AI the paid plugin as a reference, but I told it not to use it."
The AI has no "ignore this" switch. Everything you paste in becomes part of what it reasons over, and your instruction is only one more line in that pile. It may avoid copying exact lines, but the original's layout, naming, and approach still steer the result. You can't un-show it something.
"It rewrote everything in its own words, so it's original."
Rewording isn't originality. Copyright can protect how a program is structured and organized, not only its literal text. Building your own plugin that does the same job is fine. Following someone else's implementation with different variable names is not, in the same way that a retold novel is still that novel.
"That was a different chat. This one is fresh."
Not necessarily. Many current AI tools keep memory across sessions and can search your old conversations, and you often can't see exactly what they've kept. Opening a new chat doesn't reliably reset what the tool knows.
None of this means you shouldn't read other people's code. Studying existing plugins is how most VaM developers learned, and we encourage it. The difference is between learning from a plugin and handing it to an AI to reproduce. If the moderation team feels your plugin or app is a derivative of someone else's work because of the way AI was used, we may enforce the relevant licensing requirements, the same as we would for any other derivative.
