<th
ink>
We are
in the context
of Unity game eng
ine
. The method `BuildPipel
ine
.BuildAssetBundles` is used
to build AssetBundles
.
Let me break down
the parameters:
1. `
Application.stream
ingAssets
Path`: This is
the path to the Stream
ingAssets folder
in the Unity project
. It's a folder that is
included
in the f
inal build and accessible at runtime
. The AssetBundles will
be built
into this folder
.
2
. `assetBundleBuilds
.ToArray()`: `assetBundleBuilds` is a
list (or collection)
of `AssetBundleBuild` structures
. Each `AssetBundleBuild` def
ines
the assets that should
be built
into a specific AssetBundle
. We convert it
to an array
because
the method expects an array
.
3
. `BuildAssetBundleOptions
.None`: This means we are not us
ing any special build options
. We are us
ing
the default
behavior
.
4
. `BuildTarget
.StandaloneW
indows`: This specifies
the target platform as W
indows standalone
.
The purpose
of this method call is
to build multiple AssetBundles (as specified by
the `assetBundleBuilds` collection) and output
them
to the Stream
ingAssets folder for
the W
indows platform
.
Explanation
of parameters
in detail:
- `output
Path`:
The output
path for
the AssetBundles
. Us
ing `
Application.stream
ingAssets
Path` means
the bundles will
be placed
in the Stream
ingAssets folder
.
- `builds`: An array
of `AssetBundleBuild` that descri
bes how
to build
the AssetBundles
. Each element def
ines an AssetBundle name and
the assets that
belong
to it
.
- `assetBundleOptions`:
In this case, `None`
indicates no special options (like compression, etc
.)
. However, note that by default Unity uses LZMA compression for
the entire bundle
. If you want different compression, you would use o
ther options
.
- `targetPlatform`:
The platform for which
the bundles are built (here, W
indows)
.
Important: Build
ing AssetBundles is a common way
to manage downloadable content or reduce
initial download size
in Unity
.
Let's note: This method builds
the AssetBundles and places
them
in the Stream
ingAssets folder
. However, note that
in a real project we might want
to build for multiple platforms and manage
the output
path accord
ingly
.
Example
of how
to set up `AssetBundleBuild`:
Suppose we have two asset bundles: "characters" and "environments"
. We can set up
the builds as follows:
```csharp
List<AssetBundleBuild> assetBundleBuilds = new
List<AssetBundleBuild>();
// For
the characters bundle
AssetBundleBuild charactersBuild = new AssetBundleBuild();
charactersBuild
.assetBundleName = "characters";
// An array
of asset names (
paths)
to include
in this bundle
charactersBuild
.assetNames = new str
ing[] { "Assets/Art/Characters/Player
.prefab", "Assets/Art/Characters/Enemy
.prefab" };
// For
the environments bundle
AssetBundleBuild environmentsBuild = new AssetBundleBuild();
environmentsBuild
.assetBundleName = "environments";
environmentsBuild
.assetNames = new str
ing[] { "Assets/Art/Environments/Forest
.unity", "Assets/Art/Environments/Mounta
in.unity" };
assetBundleBuilds
.Add(charactersBuild);
assetBundleBuilds
.Add(environmentsBuild);
```
Then we call
the build method
.
However, note that
the method `BuildPipel
ine
.BuildAssetBundles` returns a `AssetBundleManifest` object which conta
ins
information about
the built bundles
. We might want
to capture that for fur
ther process
ing
.
Example
of the full call:
```csharp
us
ing UnityEdi
tor; // Note: This
must be in an Edi
tor script
because BuildPipel
ine is part
of the Edi
tor
// We are
in an Edi
tor script, so we can use BuildPipel
ine
public static void BuildBundles()
{
// Prepare
the list of AssetBundleBuild as above
List<AssetBundleBuild> assetBundleBuilds = new
List<AssetBundleBuild>();
//
... populate
the list ...
// Build
the bundles
AssetBundleManifest manifest = BuildPipel
ine
.BuildAssetBundles(
Application.stream
ingAssets
Path, assetBundleBuilds
.ToArray(), BuildAssetBundleOptions
.None, BuildTarget
.StandaloneW
indows);
//
The manifest can
be used
to get all
the bundle names, dependencies, etc
.
if (manifest != null)
{
// Do someth
ing with
the manifest, for example, log
the bundle names
str
ing[] bundles = manifest
.GetAllAssetBundles();
foreach (str
ing bundle
in bundles)
{
Debug
.Log("Built bundle: " + bundle);
}
}
}
```
Note:
The above code
must be placed
in an Edi
tor folder
because it uses `BuildPipel
ine` and `AssetBundleManifest`
. Also, note that `
Application.stream
ingAssets
Path`
in the Edi
tor po
ints
to the project's Stream
ingAssets folder, which is acceptable for test
ing but for a real build we might want
to output
to a different folder and
then move
to Stream
ingAssets
.
Important: When runn
ing
in the Unity Edi
tor,
the Stream
ingAssets
path is
the project's Stream
ingAssets folder
. However, when build
ing
the game,
the contents
of that folder are copied
to the build's Stream
ingAssets folder
. So build
ing
the AssetBundles directly
to Stream
ingAssets
in the project is acceptable if you plan
to include
them
in the build
. But if
the bundles are large, you might not want
them
in the initial build (
then you would build
to a different location and host
them for download)
.
Also note that for
the built game
to load
these bundles, you would use `AssetBundle
.LoadFromFile` or similar APIs at runtime
.
Let's write
the code
in a proper Edi
tor script:
```csharp
us
ing UnityEdi
tor;
us
ing UnityEng
ine;
us
ing System
.Collections
.Generic;
us
ing System
.IO;
public class AssetBundleBuilder : Mono
Behaviour
{
[MenuItem("Build/Build AssetBundles")]
static void BuildAssetBundles()
{
// Ensure
the direc
tory
exists
str
ing output
Path =
Application.stream
ingAssets
Path;
if (!Direc
tory
.Exists(output
Path))
{
Direc
tory
.CreateDirec
tory(output
Path);
}
// Prepare
the builds
List<AssetBundleBuild> assetBundleBuilds = new
List<AssetBundleBuild>();
// Example: Add two bundles
// Bundle
1: characters
AssetBundleBuild bundle
1 = new AssetBundleBuild();
bundle
1.assetBundleName = "characters";
bundle
1.assetNames = new str
ing[] { "Assets/Art/Characters/Player
.prefab", "Assets/Art/Characters/Enemy
.prefab" };
// Bundle 2: environments
AssetBundleBuild bundle2 = new AssetBundleBuild();
bundle2
.assetBundleName = "environments";
bundle2
.assetNames = new str
ing[] { "Assets/Art/Environments/Forest
.unity", "Assets/Art/Environments/Mounta
in.unity" };
assetBundleBuilds
.Add(bundle
1);
assetBundleBuilds
.Add(bundle2);
// Build
the bundles
AssetBundleManifest manifest = BuildPipel
ine
.BuildAssetBundles(output
Path, assetBundleBuilds
.ToArray(), BuildAssetBundleOptions
.None, BuildTarget
.StandaloneW
indows);
if (manifest == null)
{
Debug
.LogError("AssetBundle build failed!");
}
else
{
Debug
.Log("AssetBundle build succeeded!");
// Optionally, pr
int all bundles
str
ing[] bundles = manifest
.GetAllAssetBundles();
foreach (var bundle
in bundles)
{
Debug
.Log("Built bundle: " + bundle);
}
}
}
}
```
However, note that
the above example is a simplified one
. In a real project, you might want
to get
the asset bundle assignments from
the asset database
instead
of hard-cod
ing
.
Now,
to answer
the orig
inal question:
The method call `BuildPipel
ine
.BuildAssetBundles(
Application.stream
ingAssets
Path, assetBundleBuilds
.ToArray(), BuildAssetBundleOptions
.None, BuildTarget
.StandaloneW
indows);` builds
the specified asset bundles and outputs
them
to the Stream
ingAssets folder target
ing
the W
indows platform
.
</th
ink>
### `BuildPipel
ine
.BuildAssetBundles` 作用详解
在 Unity 中，`BuildPipel
ine
.BuildAssetBundles` 用于构建 AssetBundle（资源包），这是 Unity 的资源动态加载机制。你提供的代码如下：
```csharp
BuildPipel
ine
.BuildAssetBundles(
Application.stream
ingAssets
Path,
assetBundleBuilds
.ToArray(),
BuildAssetBundleOptions
.None,
BuildTarget
.StandaloneW
indows
);
```
#### 参数解析：
1. **输出路径 (`
Application.stream
ingAssets
Path`)**
- 将生成的 AssetBundle 文件保存到项目的 `Stream
ingAssets` 文件夹。
- 该路径在运行时可通过 `
Application.stream
ingAssets
Path` 访问（例如：`/Assets/Stream
ingAssets`）。
2
. **资源包定义 (`assetBundleBuilds
.ToArray()`)**
- `assetBundleBuilds` 是一个 `
List<AssetBundleBuild>` 集合。
- 每个 `AssetBundleBuild` 定义了：
- `assetBundleName`：资源包名称（如 "environment"）。
- `assetNames`：包含的资源路径列表（如 `["Assets/Textures/rock
.png", "Assets/Prefabs/tree
.prefab"]`）。
- `
ToArray()` 将列表转换为数组以满足方法要求。
3
. **构建选项 (`BuildAssetBundleOptions
.None`)**
- 使用默认压缩方式（LZMA 算法，高压缩率但加载时需解压）。
- 其他常用选项：
- `UncompressedAssetBundle`：无压缩（加载快，体积大）。
- `ChunkBasedCompression`：LZ4 压缩（平衡压缩率和加载速度）。
4
. **目标平台 (`BuildTarget
.StandaloneW
indows`)**
- 生成 W
indows 平台的 AssetBundle（格式为 `
.manifest` + 无扩展名二进制文件）。
- 需与最终运行平台一致（如 Android 用 `BuildTarget
.Android`）。
#### 完整示例代码：
```csharp
us
ing UnityEdi
tor;
us
ing System
.Collections
.Generic;
public class AssetBundleBuilder
{
[MenuItem("
Tools/Build AssetBundles")]
public static void BuildBundles()
{
//
1. 配置资源包
List<AssetBundleBuild> assetBundleBuilds = new
List<AssetBundleBuild>();
var sceneBundle = new AssetBundleBuild();
sceneBundle
.assetBundleName = "scenes";
sceneBundle
.assetNames = new str
ing[] { "Assets/Scenes/
Main.unity" };
var textureBundle = new AssetBundleBuild();
textureBundle
.assetBundleName = "textures";
textureBundle
.assetNames = new str
ing[] { "Assets/Textures/Icon
.png" };
assetBundleBuilds
.Add(sceneBundle);
assetBundleBuilds
.Add(textureBundle);
// 2
. 确保目录存在
if (!System
.IO
.Direc
tory
.Exists(
Application.stream
ingAssets
Path))
{
System
.IO
.Direc
tory
.CreateDirec
tory(
Application.stream
ingAssets
Path);
}
// 3
. 构建资源包
BuildPipel
ine
.BuildAssetBundles(
Application.stream
ingAssets
Path,
assetBundleBuilds
.ToArray(),
BuildAssetBundleOptions
.None,
BuildTarget
.StandaloneW
indows
);
AssetDatabase
.Refresh(); // 刷新Unity编辑器
}
}
```
#### 生成的文件示例：
```
Stream
ingAssets/
├── Stream
ingAssets
.manifest // 总清单
├── scenes // 场景资源包（无扩展名）
├── scenes
.manifest // 场景包清单
├── textures // 贴图资源包
└── textures
.manifest // 贴图包清单
```
#### 运行时加载示例：
```csharp
// 从Stream
ingAssets加载资源包
IEnumera
tor LoadBundle(str
ing bundleName)
{
str
ing
path = System
.IO
.Path.Comb
ine(
Application.stream
ingAssets
Path, bundleName);
AssetBundleCreateRequest request = AssetBundle
.LoadFromFileAsync(
path);
yield return request;
AssetBundle bundle = request
.assetBundle;
GameObject prefab = bundle
.LoadAsset<GameObject>("Player");
Instantiate(prefab);
}
```
---
本文介绍了解决设置flexbuildpath时出现的Mainapplicationmustbeinthelistofapplicationpaths错误的方法。主要是因为缺少默认的Application配置，解决步骤包括在FlexApplacations中添加并设置主mxml文件为默认。
扫一扫
155
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
