You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>Most bundled plugins ship with <code>EnabledByDefault</code> set to <code>false</code>, so they cost nothing until you ask for
149
145
them. Enable per project:</p>
150
146
<p><proceduretitle="Enable a bundled plugin" id="enable-plugin">
@@ -166,7 +162,7 @@ <h2 id="enabling-a-plugin">Enabling a plugin</h2>
166
162
Enabling a plugin adds its shader permutations, modules and startup cost to every build. Enable what you
167
163
use; leave the rest off. See <ahref="Shader-Compilation-And-PSO.md">Shader Compilation and PSO</a>.
168
164
</note></p>
169
-
<h2id="plugins-and-debloating">Plugins and debloating</h2>
165
+
<h2id="debloating">插件和 debloating</h2>
170
166
<p>The <ahref="Debloat-Guide.md">debloat suite</a> can strip plugins from the engine tree using
171
167
<code>ExcludedPlugins.txt</code>. That list is aggressive and includes plugins many projects genuinely need —
172
168
<code>GameplayAbilities</code>, <code>ApexDestruction</code>, <code>HairStrands</code> and the NVIDIA plugins among them.</p>
@@ -176,16 +172,14 @@ <h2 id="plugins-and-debloating">Plugins and debloating</h2>
176
172
</warning></p>
177
173
<p>The same list is used by <code>LocalBuilds\CompressBuildSeparate.bat</code> to split plugins into their own archive,
178
174
which is a non-destructive alternative. See <ahref="Installed-Builds.md">Installed Builds</a>.</p>
179
-
<h2id="adding-your-own">Adding your own</h2>
180
-
<p>Project plugins go in <code><Project>\Plugins</code>, as with stock Unreal. Engine plugins that the whole team should
181
-
have go in <code>Engine\Plugins\Runtime\VitePlugins</code> and require an engine rebuild and redistribution.</p>
182
-
<p>If you want a plugin bundled with Vite, it must be compatible with 4.21–4.27. UE5-only plugins are
183
-
out of scope. See <ahref="../Proposed-Plugins/">Proposed Plugins</a> for the criteria and the current candidate list.</p>
184
-
<h2id="see-also">See also</h2>
175
+
<h2id="_5">添加自己的插件</h2>
176
+
<p>Project plugins go in <code><Project>\Plugins</code>, as with stock Unreal. Engine plugins that the whole team should have go in <code>Engine\Plugins\Runtime\VitePlugins</code> and require an engine rebuild and redistribution.</p>
177
+
<p>If you want a plugin bundled with Vite, it must be compatible with 4.21–4.27. UE5-only plugins are out of scope. See <ahref="../Proposed-Plugins/">Proposed Plugins</a> for the criteria and the current candidate list.</p>
0 commit comments