Build and Load Paths

The Build and Load Paths settings of the Content Packing & Loading schema determine where the artifacts for your content builds are created and where the Addressables system should look for them at runtime.

譯：Content Packing＆Loading模式的構(gòu)建和加載路徑設(shè)置確定內(nèi)容構(gòu)建的工件在哪里創(chuàng)建，以及Addressables系統(tǒng)在運(yùn)行時(shí)應(yīng)該在哪里查找它們。

Setting????????????????????????????????????????????????????????????????????????????????Purpose

Build & Load PathsThe Profile path pair that defines where the Addressables build system creates artifacts for this group and where the Addressables system loads those artifacts at runtime. Choose a path pair from the list or select?<custom>?if you want to set the build and load paths separately.譯：構(gòu)建和加載路徑配置文件路徑對，定義Addressables構(gòu)建系統(tǒng)在此組中創(chuàng)建工件的位置，以及Addressables系統(tǒng)在運(yùn)行時(shí)加載這些工件的位置。從列表中選擇一個(gè)路徑對，或者選擇，如果您想單獨(dú)設(shè)置構(gòu)建和加載路徑。

Build PathA Profile variable that defines where the Addressables build system creates artifacts for this group. You can also set a custom string. Use one of the following for the build path:譯：構(gòu)建路徑用于為此組定義Addressables構(gòu)建系統(tǒng)創(chuàng)建工件的配置文件變量。您還可以設(shè)置自定義字符串。對于構(gòu)建路徑，請使用以下之一：

-?LocalBuildPath: use for assets that you plan to distribute as part of your application installation.譯：用于您計(jì)劃作為應(yīng)用程序安裝的一部分分發(fā)的資產(chǎn)。

-?RemoteBuildPath: use for assets that you plan to distribute using a remote hosting service such Unity Cloud Content Delivery or other Content Delivery Network.譯：用于您計(jì)劃使用遠(yuǎn)程主機(jī)服務(wù)（如Unity Cloud內(nèi)容交付或其他內(nèi)容交付網(wǎng)絡(luò)）分發(fā)的資產(chǎn)。

-?<custom>: specify a string as the build path for this group.譯：指定字符串作為此組的構(gòu)建路徑。

Only shown if you set?Build & Load Paths?to?<custom>.Load PathA Profile variable that defines where the Addressables system loads the build artifacts for this group at runtime. You can also set a custom string. Use one of the following for the load path:譯：僅在將Build＆Load Paths設(shè)置為時(shí)顯示。 加載路徑用于為此組定義Addressables系統(tǒng)在運(yùn)行時(shí)加載構(gòu)建工件的配置文件變量。您還可以設(shè)置自定義字符串。對于加載路徑，請使用以下之一：

-?LocalLoadPath: use for assets that you plan to distribute as part of your application installation.譯：用于您計(jì)劃作為應(yīng)用程序安裝的一部分分發(fā)的資產(chǎn)。

-?RemoteLoadPath: use for assets that you plan to distribute using a remote hosting service such Unity Cloud Content Delivery or other Content Delivery Network.譯：用于您計(jì)劃使用遠(yuǎn)程主機(jī)服務(wù)（如Unity Cloud內(nèi)容交付或其他內(nèi)容交付網(wǎng)絡(luò)）分發(fā)的資產(chǎn)。

-?<custom>: specify a string as the load path for this group.譯：指定字符串作為此組的加載路徑。

Only shown if you set?Build & Load Paths?to?<custom>.譯：僅在將Build＆Load Paths設(shè)置為時(shí)顯示。

The build and load path options are defined by variables in your?Profiles. Note that only variables intended for a given purpose should be used for a setting. For example, choosing a load path variable for a build path setting wouldn't give you a useful result.

譯：構(gòu)建和加載路徑選項(xiàng)由Profiles中的變量定義。請注意，應(yīng)僅使用用于特定目的的變量進(jìn)行設(shè)置。例如，為構(gòu)建路徑設(shè)置加載路徑變量不會(huì)給您有用的結(jié)果。

When you choose a Profile variable, the current evaluation of the path is shown in the?Path Preview. Components of the path in braces, such as?{UnityEngine.AddressableAssets.Addressable.RuntimePath}, indicate that static variable is used to construct the final path at runtime. That portion of the path is replaced by the current value of the static variable when the Addressables system initializes at runtime.

譯：

當(dāng)您選擇配置文件變量時(shí)，路徑預(yù)覽中顯示路徑的當(dāng)前評估。在括號(hào)中的路徑組件（例如{UnityEngine.AddressableAssets.Addressable.RuntimePath}）表示在運(yùn)行時(shí)使用靜態(tài)變量構(gòu)建最終路徑。該路徑部分在Addressables系統(tǒng)在運(yùn)行時(shí)初始化時(shí)由靜態(tài)變量的當(dāng)前值替換。

WARNING

In most cases, you should not change the local build or load paths from their default values. If you do, you must copy the local build artifacts from your custom build location to the project's [StreamingAssets] folder before making a Player build. Altering these paths also precludes building your Addressables as part of the Player build.

譯：在大多數(shù)情況下，您不應(yīng)更改本地構(gòu)建或加載路徑的默認(rèn)值。如果這樣做，您必須在制作Player構(gòu)建之前將本地構(gòu)建工件從自定義構(gòu)建位置復(fù)制到項(xiàng)目的[StreamingAssets]文件夾中。更改這些路徑還會(huì)排除將您的Addressables作為Player構(gòu)建的一部分構(gòu)建。

See?Profiles?for more information.

譯：

Advanced Options

Setting????????????????????????????????????????????????Purpose

Asset Bundle CompressionThe compression type for all bundles produced from the group. LZ4 is usually the most efficient option, but other options can be better in specific circumstances. See?AssetBundle Compression?for more information.譯：資產(chǎn)捆綁壓縮此組生成的所有捆綁包的壓縮類型。LZ4通常是最有效的選項(xiàng)，但其他選項(xiàng)可以在特定情況下更好。有關(guān)更多信息，請參見AssetBundle Compression。

Include In BuildWhether to include assets in this group in a content build.譯：包括在構(gòu)建中是否在此組中包括資產(chǎn)。

Force Unique ProviderWhether Addressables uses unique instances of Resource Provider classes for this group. Enable this option if you have custom Provider implementations for the asset types in this group and instances of those Providers must not be shared between groups.譯：強(qiáng)制使用唯一的提供程序是否Addressables為此組使用資源提供程序類的唯一實(shí)例。如果您對此組中的資產(chǎn)類型進(jìn)行了自定義提供程序?qū)崿F(xiàn)，并且這些提供程序的實(shí)例不能在組之間共享，則啟用此選項(xiàng)。

Use Asset Bundle CacheWhether to cache remotely distributed bundles.譯：使用資產(chǎn)捆綁緩存是否要緩存遠(yuǎn)程分布式捆綁包。

Asset Bundle CRCWhether to verify a bundle's integrity before loading it.譯：資產(chǎn)捆綁CRC是否在加載捆綁包之前驗(yàn)證其完整性。

??Disabled: Never check bundle integrity.譯：?已禁用：從不檢查捆綁包完整性。

??Enabled, Including Cached: Always check bundle integrity.譯：?啟用，包括緩存：始終檢查捆綁包完整性。

??Enabled, Excluding Cached: Check integrity of bundles when downloading.譯：?啟用，不包括緩存：在下載時(shí)檢查捆綁包的完整性。

Use UnityWebRequest for Local Asset BundlesLoad local AssetBundle archives from this group using?UnityWebRequestAssetBundle.GetAssetBundle?instead譯：使用UnityWebRequest加載本地AssetBundle歸檔文件，而不是使用AssetBundle.LoadFromFileAsync。 of?AssetBundle.LoadFromFileAsync.譯：

Request TimeoutThe timeout interval for downloading remote bundles.譯：請求超時(shí)：下載遠(yuǎn)程捆綁包的超時(shí)時(shí)間間隔。

Use Http Chunked TransferWhether to use the HTTP/1.1 chunked-transfer encoding method when downloading bundles.
Deprecated and ignored in Unity 2019.3+.譯：使用Http Chunked Transfer：在下載捆綁包時(shí)是否使用HTTP / 1.1分塊傳輸編碼方法。?在Unity 2019.3+中已棄用并忽略。

Http Redirect LimitThe number of redirects allowed when downloading bundles. Set to -1 for no limit.譯：Http重定向限制：下載捆綁包時(shí)允許的重定向次數(shù)。將其設(shè)置為-1表示沒有限制。

Retry CountThe number of times to retry failed downloads.譯：重試次數(shù)：重試下載失敗的次數(shù)。

Include Addresses in CatalogWhether to include the address strings in the catalog. If you don't load assets in the group using their address strings, you can decrease the size of the catalog by not including them.譯：在目錄中包含地址：是否在目錄中包含地址字符串。如果不使用地址字符串加載組中的資源，則可以通過不包含它們來減小目錄的大小。

Include GUIDs in CatalogWhether to include GUID strings in the catalog. You must include GUID strings to access an asset with an?AssetReference. If you don't load assets in the group using AssetReferences or GUID strings, you can decrease the size of the catalog by not including them.譯：在目錄中包含GUID：是否在目錄中包含GUID字符串。如果使用AssetReference訪問資源，則必須包含GUID字符串。如果不使用AssetReferences或GUID字符串加載組中的資源，則可以通過不包含它們來減小目錄的大小。

Include Labels in CatalogWhether to include label strings in the catalog. If you don't load assets in the group using labels, you can decrease the size of the catalog by not including them.譯：在目錄中包含標(biāo)簽：是否在目錄中包含標(biāo)簽字符串。如果不使用標(biāo)簽加載組中的資源，則可以通過不包含它們來減小目錄的大小。

Internal Asset Naming ModeDetermines the identification of assets in AssetBundles and is used to load the asset from the bundle. This value is used as the internalId of the asset Location. Changing this setting affects a bundles CRC and Hash value.
譯：內(nèi)部資產(chǎn)命名模式：確定AssetBundles中資產(chǎn)的標(biāo)識(shí)方式，并用于從捆綁包中加載資產(chǎn)。此值用作資產(chǎn)位置的internalId。更改此設(shè)置會(huì)影響B(tài)undle的CRC和Hash值。

Warning: Do not modify this setting for?Content update builds. The data stored in the?content state file?will become invalid.譯：警告：不要為內(nèi)容更新構(gòu)建修改此設(shè)置。內(nèi)容狀態(tài)文件中存儲(chǔ)的數(shù)據(jù)將變?yōu)闊o效。

The different modes are:
-?Full Path: the path of the asset in your project. This mode is recommended to use during development because it allows you to identify Assets being loaded by their ID if needed.譯：完整路徑：項(xiàng)目中資產(chǎn)的路徑。在開發(fā)過程中推薦使用此模式，因?yàn)樗试S您根據(jù)需要通過其ID標(biāo)識(shí)正在加載的資產(chǎn)。

-?Filename: the asset's filename. This can also be used to identify an asset.?Note: You cannot have multiple assets with the same name.譯：文件名：資產(chǎn)的文件名。這也可以用于標(biāo)識(shí)資產(chǎn)。注意：您不能具有相同名稱的多個(gè)資產(chǎn)。

-?GUID: a deterministic value for the asset.譯：GUID：資產(chǎn)的確定性值。

-?Dynamic: the shortest id that can be constructed based on the assets in the group. This mode is recommended to use for release because it can reduce the amount of data in the AssetBundle and catalog, and lower runtime memory overhead.譯：動(dòng)態(tài)：基于組中的資產(chǎn)可以構(gòu)建的最短ID。在發(fā)布時(shí)推薦使用此模式，因?yàn)樗梢詼p少AssetBundle和目錄中的數(shù)據(jù)量，并降低運(yùn)行時(shí)內(nèi)存開銷。

Internal Bundle Id ModeDetermines how an AssetBundle is identified internally. This affects how an AssetBundle locates dependencies that are contained in other bundles. Changing this value affects the CRC and Hash of this bundle and all other bundles that reference it.譯：內(nèi)部Bundle Id模式：確定如何在內(nèi)部標(biāo)識(shí)AssetBundle。這會(huì)影響AssetBundle定位包含在其他Bundle中的依賴項(xiàng)的方式。更改此值會(huì)影響此Bundle及引用它的所有其他Bundle的CRC和Hash。

Warning: Do not modify this setting for?Content update builds. The data stored in the?content state file?will become invalid.譯：要為內(nèi)容更新構(gòu)建修改此設(shè)置。內(nèi)容狀態(tài)文件中存儲(chǔ)的數(shù)據(jù)將變?yōu)闊o效。The different modes are:
-?Group Guid: unique identifier for the Group. This mode is recommended to use as it does not change.譯：Group Guid：組的唯一標(biāo)識(shí)符。推薦使用此模式，因?yàn)樗粫?huì)更改。

-?Group Guid Project Id Hash: uses a combination of the Group GUID and the Cloud Project Id (if Cloud Services are enabled). This changes if the Project is bound to a different Cloud Project Id. This mode is recommended when sharing assets between multiple projects because the id constructed is deterministic and unique between projects.譯：Group Guid Project Id Hash：使用組GUID和云項(xiàng)目ID（如果啟用了云服務(wù)）的組合。如果項(xiàng)目綁定到不同的Cloud Project Id，則會(huì)更改此值的構(gòu)造方式。當(dāng)在多個(gè)項(xiàng)目之間共享資產(chǎn)時(shí)，建議使用此模式，因?yàn)樗鼧?gòu)建的ID是確定性的且在項(xiàng)目之間唯一。

-?Group Guid Project Id Entries Hash: uses a combination of the Group GUID, Cloud Project Id (if Cloud Services are enabled), and asset entries in the Group. Note that using this mode can easily cause bundle cache version issues. Adding or removing entries results in a different hash.譯：Group Guid Project Id Entries Hash：使用組GUID，云項(xiàng)目ID（如果啟用了云服務(wù)）和組中的資產(chǎn)條目的組合。請注意，使用此模式很容易造成捆綁包緩存版本問題。添加或刪除條目會(huì)導(dǎo)致不同的哈希值。

Cache Clear BehaviorDetermines when an installed application clears AssetBundles from the cache.譯：Cache Clear Behavior：確定已安裝的應(yīng)用程序何時(shí)清除AssetBundles緩存。

Bundle ModeHow to pack the assets in this group into bundles:譯：Bundle Mode：如何將該組中的資產(chǎn)打包到Bundle中：

-?Pack Together: create a single bundle containing all assets.譯：Pack Together：創(chuàng)建包含所有資產(chǎn)的單個(gè)Bundle。

-?Pack Separately: create a bundle for each primary asset in the group. Subassets, such as Sprites in a Sprite sheet are packed together. Assets within a folder added to the group are also packed together.譯：Pack Separately：為該組中的每個(gè)主要資產(chǎn)創(chuàng)建一個(gè)Bundle。Sprite Sheet中的Sprites等子資產(chǎn)將被打包在一起。添加到該組的文件夾中的資產(chǎn)也將被打包在一起。

-?Pack Together by Label: create a bundle for assets sharing the same combination of labels.譯：Pack Together by Label：為共享相同標(biāo)簽組合的資產(chǎn)創(chuàng)建一個(gè)Bundle。

Bundle Naming ModeHow to construct the file names of AssetBundles:譯：Bundle Naming Mode：如何構(gòu)建AssetBundles的文件名：

-?Filename: the filename is a string derived from the group name. No hash is appended to it.譯：Filename：文件名是從組名稱派生的字符串。不在其后附加哈希值。

-?Append Hash to Filename: the filename is a string derived from the group name with bundle hash appended to it. The bundle hash is calculated using the contents of the bundle.譯：Append Hash to Filename：文件名是從組名稱派生的字符串，附加了Bundle哈希值。Bundle哈希值是使用Bundle內(nèi)容計(jì)算的。

-?Use Hash of AssetBundle: the filename is the bundle hash.譯：Use Hash of AssetBundle：文件名是Bundle哈希值。

-?Use Hash of Filename: the filename is a hash calculated from the a string derived from the group name.譯：Use Hash of Filename：文件名是從組名稱派生的字符串計(jì)算的哈希值。

Asset Load ModeWhether to load assets individually as you request them (the default) or always load all assets in the group together. It is recommended to use?Requested Asset and Dependencies?for most cases. See?Asset Load Mode?for more information.譯：Asset Load Mode：是否按您請求它們來單獨(dú)加載資產(chǎn)（默認(rèn)）或始終一起加載該組中的所有資產(chǎn)。對于大多數(shù)情況，建議使用請求的資產(chǎn)和依賴項(xiàng)。有關(guān)詳細(xì)信息，請參見資產(chǎn)加載模式。

Asset ProviderDefines which Provider class Addressables uses to load assets from the AssetBundles generated from this group. Set this option to?Assets from Bundles Provider?unless you have a custom Provider implementation to provide assets from an AssetBundle.譯：Asset Provider：定義Addressables用于從此組生成的AssetBundles加載資產(chǎn)的Provider類。除非您有自定義Provider實(shí)現(xiàn)來提供來自AssetBundle的資產(chǎn)，否則請將此選項(xiàng)設(shè)置為Bundles Provider。

Asset Bundle ProviderDefines which Provider class Addressables uses to load AssetBundles generated from this group. Set this option to?AssetBundle Provider?unless you have a custom Provider implementation to provide AssetBundles.譯：Asset Bundle Provider：定義Addressables用于加載從此組生成的AssetBundles的Provider類。除非您有自定義Provider實(shí)現(xiàn)來提供AssetBundles，否則請將此選項(xiàng)設(shè)置為AssetBundle Provider。

AssetBundle Compression

Addressables provides three different options for bundle compression: Uncompressed, LZ4, and LZMA. Generally speaking, LZ4 should be used for local content, and LZMA for remote, but more details are outlined below as there can be exceptions to this.

譯：Addressables提供三種不同的Bundle壓縮選項(xiàng)：未壓縮、LZ4和LZMA。一般來說，LZ4應(yīng)用于本地內(nèi)容，LZMA應(yīng)用于遠(yuǎn)程內(nèi)容，但是下面詳細(xì)說明了更多細(xì)節(jié)，因?yàn)榇嬖诶馇闆r。

You can set the compression option using the Advanced settings on each group. Compression does not affect in-memory size of your loaded content.

譯：您可以使用每個(gè)組上的高級設(shè)置來設(shè)置壓縮選項(xiàng)。壓縮不影響已加載內(nèi)容的內(nèi)存大小。

• Uncompressed - This option is largest on disk, and generally fastest to load. If your game happens to have space to spare, this option should at least be considered for local content. A key advantage of uncompressed bundles is how they handle being patched. If you are developing for a platform where the platform itself provides patching (such as Steam or Switch), uncompressed bundles provide the most accurate (smallest) patching. Either of the other compression options will cause at least some bloat of patches.譯：未壓縮 - 此選項(xiàng)在磁盤上最大，并且通常加載速度最快。如果您的游戲恰好有足夠的空間，那么至少應(yīng)該考慮此選項(xiàng)用于本地內(nèi)容。未壓縮Bundle的一個(gè)關(guān)鍵優(yōu)勢是它們?nèi)绾翁幚肀淮蜓a(bǔ)丁的情況。如果您正在為平臺(tái)開發(fā)，而平臺(tái)本身提供打補(bǔ)丁的功能（例如Steam或Switch），則未壓縮的Bundle提供最準(zhǔn)確（最小）的補(bǔ)丁。任何其他壓縮選項(xiàng)都會(huì)導(dǎo)致某些補(bǔ)丁膨脹。

• LZ4 - If Uncompressed is not a viable option, then LZ4 should be used for all other local content. This is a chunk-based compression which provides the ability to load parts of the file without needing to load it in its entirety.譯：LZ4 - 如果未壓縮不可行，則應(yīng)為所有其他本地內(nèi)容使用LZ4。這是一種基于塊的壓縮，它提供了在不需要完全加載文件的情況下加載文件的能力。

• LZMA - LZMA should be used for all remote content, but not for any local content. It provides the smallest bundle size, but is slow to load. If you were to store local bundles in LZMA you could create a smaller player, but load times would be significantly worse than uncompressed or LZ4. For downloaded bundles, we avoid the slow load time by recompressing the downloaded bundle when storing it in the AssetBundle cache. By default, bundles will be stored in the cache with LZ4 compression.譯：LZMA - LZMA應(yīng)該用于所有遠(yuǎn)程內(nèi)容，但不適用于任何本地內(nèi)容。它提供最小的Bundle大小，但加載速度較慢。如果您將本地Bundle存儲(chǔ)在LZMA中，則可以創(chuàng)建較小的播放器，但加載時(shí)間將顯著惡化，而未壓縮或LZ4則不會(huì)。對于下載的Bundle，我們通過在存儲(chǔ)它們在AssetBundle緩存中時(shí)重新壓縮已下載的Bundle來避免慢速加載時(shí)間。默認(rèn)情況下，Bundle將使用LZ4壓縮存儲(chǔ)在緩存中。

NOTE

LZMA AssetBundle compression is not available for AssetBundles on WebGL. LZ4 compression can be used instead. For more WebGL AssetBundle information, see?Building and running a WebGL project.

譯：LZMA AssetBundle壓縮不適用于WebGL上的AssetBundle?？梢愿挠肔Z4壓縮。有關(guān)更多WebGL AssetBundle信息，請參見構(gòu)建和運(yùn)行WebGL項(xiàng)目。

Note that the hardware characteristics of a platform can mean that uncompressed bundles are not always the fastest to load. The maximum speed of loading uncompressed bundles is gated by IO speed, while the speed of loading LZ4-compressed bundles can be gated by either IO speed or CPU, depending on hardware. On most platforms, loading LZ4-compressed bundles is CPU bound, and loading uncompressed bundles will be faster. On platforms that have low IO speeds and high CPU speeds, LZ4 loading can be faster. It is always a good practice to run performance analysis to validate whether your game fits the common patterns, or needs some unique tweaking.

譯：請注意，平臺(tái)的硬件特性可能意味著未壓縮的Bundle并不總是加載最快的。未壓縮Bundle的最大加載速度受IO速度的限制，而加載LZ4壓縮的Bundle的速度可以受CPU或IO速度的限制，具體取決于硬件。在大多數(shù)平臺(tái)上，加載LZ4壓縮的Bundle是CPU限制的，加載未壓縮的Bundle會(huì)更快。在具有低IO速度和高CPU速度的平臺(tái)上，LZ4加載速度可能更快。始終進(jìn)行性能分析是一種良好的實(shí)踐，以驗(yàn)證您的游戲是否符合常見模式，或者是否需要進(jìn)行一些獨(dú)特的調(diào)整。

More information on Unity's compression selection is available in the?AssetBundle compression manual page.

譯：有關(guān)Unity的壓縮選擇的更多信息，請參見AssetBundle壓縮手冊頁面。

AssetBundle CRC

Different CRC settings are best used depending upon different circumstances. Checking for a change in the file requires the entire AssetBundle to be decompressed and the check processed on the uncompressed bytes. This can impact performance negatively and may not be a worth while trade off. Corruption is likely to only happen during a download, disk storage is generally reliable and unlikely to have corrupted files after saving to disk. if your AssetBundle contains data that may be tampered with such as settings values, then you may want to consider enabling CRC checks on saved AssetBundles.

譯：不同的CRC設(shè)置最好根據(jù)不同的情況使用。檢查文件是否更改需要將整個(gè)AssetBundle解壓縮并處理未壓縮的字節(jié)上的檢查。這可能會(huì)對性能產(chǎn)生負(fù)面影響，并且可能不值得權(quán)衡。損壞可能僅在下載期間發(fā)生，磁盤存儲(chǔ)通常是可靠的，保存到磁盤后不太可能出現(xiàn)損壞的文件。如果您的AssetBundle包含可能被篡改的數(shù)據(jù)，例如設(shè)置值，則可以考慮在保存的AssetBundle上啟用CRC檢查。

For?local?AssetBundles, if the application download performs a check on the download before saving to disk. Then consider setting this to?Disabled?as the download will have already been checked.

譯：對于本地AssetBundle，如果應(yīng)用程序下載在保存到磁盤之前對下載進(jìn)行檢查。然后請考慮將其設(shè)置為Disabled，因?yàn)橄螺d已經(jīng)被檢查過了。

For?remote?AssetBundles,?Enabled, Excluding cache?is a good default. When downloading and caching an AssetBundle to disk, the bytes are decompressed and a CRC calculation is done during file saving. This will not impact performance and the corruption is most likely to occur during this phase from the download.?including cache?is good to use where the data needs to be checked everytime such as settings values.

譯：對于遠(yuǎn)程AssetBundle，默認(rèn)情況下啟用Excluding cache是一個(gè)好的選擇。在下載和緩存AssetBundle到磁盤時(shí)，字節(jié)將被解壓縮，并且在文件保存期間進(jìn)行CRC計(jì)算。這不會(huì)影響性能，而且損壞最有可能在下載期間發(fā)生。包括緩存是在數(shù)據(jù)需要每次進(jìn)行檢查的情況下使用的，例如設(shè)置值。

Asset Load Mode

For most platforms and collection of content, it is recommended to use?Requested Asset and Dependencies. This mode will only load what is required for the Assets requested with?LoadAssetAsync?or?LoadAssetsAsync. Objects are loaded based in the order that they appear in a bundle file, which can result in reading the same file multiple times. Enabling the?Contiguous Bundles?option in?Addressables Build settings?can help reduce the number of extra file reads.

譯：對于大多數(shù)平臺(tái)和內(nèi)容集合，建議使用Requested Asset and Dependencies模式。這種模式只會(huì)加載使用LoadAssetAsync或LoadAssetsAsync請求的資產(chǎn)所需的內(nèi)容。對象是基于它們在Bundle文件中出現(xiàn)的順序加載的，這可能導(dǎo)致多次讀取同一文件。在Addressables Build設(shè)置中啟用Contiguous Bundles選項(xiàng)可以幫助減少額外的文件讀取。

This prevents situations where Assets are loaded into memory that are not used.

譯：這可以防止將未使用的資產(chǎn)加載到內(nèi)存中。

Performance in situations where you will load all Assets that are packed together, such as a loading screen. Most types of content will have either have similar or improved performance when loading each individually using?Requested Asset and Dependencies?mode. This mode sequentially reads entire bundle files, which may be more preferrable in some platforms like the Switch.

譯：在需要加載所有打包在一起的資產(chǎn)的情況下（例如加載屏幕等情況）中，大多數(shù)類型的內(nèi)容都將使用請求的資產(chǎn)和依賴項(xiàng)模式逐個(gè)加載每個(gè)資產(chǎn)，這樣可以獲得類似或更好的性能。此模式順序讀取整個(gè)Bundle文件，這在某些平臺(tái)（例如Switch）中可能更好。

NOTE

The examples below apply to Desktop and Mobile platforms. Performance may differ between platforms. The?All Packed Assets and Dependencies?mode typically performs better than loading assets individually on the Nintendo Switch due its hardware and memory reading limitations. It is recommended to profile loading performance for your specific content and platform to see what works for your Application.

譯：注意：以下示例適用于桌面和移動(dòng)平臺(tái)。性能可能因平臺(tái)而異。在Nintendo Switch上，All Packed Assets and Dependencies模式通常比單獨(dú)加載資產(chǎn)表現(xiàn)更好，因?yàn)樗挠布蛢?nèi)存讀取限制。建議對特定內(nèi)容和平臺(tái)進(jìn)行加載性能分析，以確定適合您的應(yīng)用程序的解決方案。

Loading performance can vary between content type. As an example, large counts of serialized data such as Prefabs or ScriptableObjects with direct references to other serialized data will load faster using?All Packed Assets and Dependencies. With some other Assets like Textures, you can often achieve better performance when you load each Asset individually.

譯：資產(chǎn)類型不同，其加載性能可能會(huì)有所不同。例如，包含大量序列化數(shù)據(jù)的資產(chǎn)，如Prefabs或ScriptableObjects，直接引用其他序列化數(shù)據(jù)，使用All Packed Assets and Dependencies可以更快地加載。對于一些其他的資產(chǎn)，如Textures，單獨(dú)加載每個(gè)資產(chǎn)往往可以獲得更好的性能。

If using?Synchronous Addressables, there is little performance between between Asset load modes. Because of greater flexibility it is recommended to use?Requested Asset and Dependencies?where you know the content will be loaded synchronously.

譯：如果使用同步地址，各種資產(chǎn)加載模式之間的性能差異很小。由于更大的靈活性，建議在您知道內(nèi)容將同步加載時(shí)使用Requested Asset and Dependencies。

On loading the first Asset with?All Packed Assets and Dependencies, all Assets are loaded into memory. Later LoadAssetAsync calls for Assets from that pack will return the preloaded Asset without needing to load it.

譯：使用All Packed Assets and Dependencies加載第一個(gè)資產(chǎn)時(shí)，所有資產(chǎn)都會(huì)加載到內(nèi)存中。以后從該包加載資產(chǎn)的LoadAssetAsync調(diào)用將返回預(yù)加載的資產(chǎn)，無需加載它。

Even though all the Assets in a group and any dependencies are loaded in memory when you use the All Packed Assets and Dependencies option, the reference count of an individual asset is not incremented unless you explicitly load it (or it is a dependency of an asset that you load explicitly). If you later call?Resources.UnloadUnusedAssets, or you load a new Scene using?LoadSceneMode.Single, then any unused assets (those with a reference count of zero) are unloaded.

譯：即使使用了All Packed Assets and Dependencies選項(xiàng)加載了組中的所有資產(chǎn)和任何依賴項(xiàng)，但除非您顯式加載它（或者它是您顯式加載的資產(chǎn)的依賴項(xiàng)），否則單個(gè)資產(chǎn)的引用計(jì)數(shù)不會(huì)增加。如果您稍后調(diào)用Resources.UnloadUnusedAssets或使用LoadSceneMode.Single加載新場景，則會(huì)卸載任何未使用的資產(chǎn)（那些引用計(jì)數(shù)為零的資產(chǎn)）。