打包用于发布的最终版本

These settings are used as default (pre-selected) launcher settings. The launcher for the Development build displays more settings than for the Release build.这些设置用作默认（预选）启动器设置。 Development构建的启动器显示的设置比Release构建的启动器显示的设置更多。

GUI-based launcher for the Development BuildDevelopment Build的基于GUI的启动器

Below are the settings used by the tool to generate a launcher for your application.以下是该工具用于为您的应用程序生成启动器的设置。

Type (launcher)	Type of the launcher: GUI-based — executable file with the name <project_name> is created. Running this file opens the GUI with the default launcher settings. These settings are stored in the <project_name>.lconfig JSON file.GUI-based — executable file with the name <project_name> is created. Running this file opens the GUI with the default launcher settings. These settings are stored in the <project_name>.lconfig JSON file. <project_name>.bat (or .sh for Linux) file is created that contains the default launcher settings. In case of the Development build with the project's SDK available, two files are created: <project_name>_development.bat (or .sh for Linux) and <project_name>_debug.bat (or .sh for Linux).<project_name>.bat (or .sh for Linux) file is created that contains the default launcher settings. In case of the Development build with the project's SDK available, two files are created: <project_name>_development.bat (or .sh for Linux) and <project_name>_debug.bat (or .sh for Linux). GUI-based — executable file with the name <project_name> is created. Running this file opens the GUI with the default launcher settings. These settings are stored in the <project_name>.lconfig JSON file.<project_name>.bat (or .sh for Linux) file is created that contains the default launcher settings. In case of the Development build with the project's SDK available, two files are created: <project_name>_development.bat (or .sh for Linux) and <project_name>_debug.bat (or .sh for Linux).启动器的类型： GUI-based — executable file with the name <project_name> is created. Running this file opens the GUI with the default launcher settings. These settings are stored in the <project_name>.lconfig JSON file.基于GUI的-创建名称为<project_name>的可执行文件。运行此文件将使用默认启动器设置打开GUI。这些设置存储在<project_name>.lconfig JSON文件中。 <project_name>.bat (or .sh for Linux) file is created that contains the default launcher settings. In case of the Development build with the project's SDK available, two files are created: <project_name>_development.bat (or .sh for Linux) and <project_name>_debug.bat (or .sh for Linux).创建的<project_name>.bat（或Linux的.sh）文件包含默认的启动程序设置。 如果使用项目SDK的Development构建，则创建两个文件：<project_name>_development.bat（或Linux的.sh）和<project_name>_debug.bat（或.sh）对于Linux）。
Banner Image (banner)	The image to be displayed in the launcher. Available for GUI-based launcher only. To assign an image, drag it from the Asset Browser. 注意 Only PNG images can be used.Only PNG images can be used. Only PNG images can be used.要在启动器中显示的图像。仅适用于基于GUI的启动器。 要分配图像，请将其从资源浏览器中拖动。 注意 Only PNG images can be used.只能使用PNG图像。
Use OpenVR	Check this box, if your project is intended for OpenVR. This will enable OpenVR mode selection in the application launcher.如果您的项目适用于OpenVR，请选中此框。这将在应用程序启动器中启用OpenVR模式选择。
Use Oculus	Check this box, if your project is intended for Oculus. This will enable Oculus mode selection in the application launcher.如果您的项目适用于Oculus，请选中此框。这将在应用程序启动器中启用Oculus模式选择。
Use Varjo	Check this box, if your project is intended for Varjo. This will enable Varjo mode selection in the application launcher.如果您的项目用于Varjo，请选中此框。这将在应用程序启动器中启用Varjo模式选择。
	注意 Necessary VR modes (three options above) for the console mode are specified in the configuration file as follows (list the ones you need): 源代码 "vrmodes": [ "OpenVR", "Oculus", "Varjo" ] 控制台模式所需的VR模式（上面的三个选项）在配置文件中指定如下（列出所需的模式）： 源代码 "vrmodes": [ "OpenVR", "Oculus", "Varjo" ]
Resolution (selected_res)	The resolution of the application screen. Multiple resolutions can be selected. The resolution that is clicked upon is set as default. 注意 Multiple resolutions for the console mode are specified in the configuration file via the resolutions parameter (list the ones you need): 源代码 "resolutions": [ { "d": 9, "n": 16, "w": 960 }, { "d": 9, "n": 16, "w": 1024 } ] Multiple resolutions for the console mode are specified in the configuration file via the resolutions parameter (list the ones you need): 源代码 "resolutions": [ { "d": 9, "n": 16, "w": 960 }, { "d": 9, "n": 16, "w": 1024 } ] Multiple resolutions for the console mode are specified in the configuration file via the resolutions parameter (list the ones you need): 源代码 "resolutions": [ { "d": 9, "n": 16, "w": 960 }, { "d": 9, "n": 16, "w": 1024 } ] 应用程序屏幕的分辨率。可以选择多种分辨率。单击的分辨率设置为默认值。 注意 Multiple resolutions for the console mode are specified in the configuration file via the resolutions parameter (list the ones you need): 源代码 "resolutions": [ { "d": 9, "n": 16, "w": 960 }, { "d": 9, "n": 16, "w": 1024 } ] 通过配置文件在配置文件中指定了控制台模式的多种分辨率。resolutions参数（列出您需要的参数）： 源代码 "resolutions": [ { "d": 9, "n": 16, "w": 960 }, { "d": 9, "n": 16, "w": 1024 } ]
Fullscreen (fullscreen)	Fullscreen mode:全屏模式: Disabled — application shall run in the windowed modeDisabled -禁用，应用程序应在窗口模式下运行 Enabled — application shall run in the fullscreen modeEnabled -启用，应用程序应在全屏模式下运行 Borderless Window — application shall run in the fullwindow mode, when an application window is rendered without decorationsBorderless Window -当应用程序窗口没有装饰时，应用程序应该在全窗口模式下运行
Binary (binary)	Type of the binary to be selected by default in the launcher, if the selected build type is Development build: Development — optimized binary with Microprofile enabled for performance checkDevelopment — optimized binary with Microprofile enabled for performance check Debug — unoptimized binary with debug informationDebug — unoptimized binary with debug information This setting is available for the GUI-based launcher only. The .bat/.sh launcher will create scripts to run the correpsonding executable files. Development — optimized binary with Microprofile enabled for performance checkDebug — unoptimized binary with debug information如果选定的构建类型为Development build，则默认在启动器中选择的二进制文件的类型： Development — optimized binary with Microprofile enabled for performance checkDevelopment—优化的二进制文件，其中已启用 Microprofile 进行性能检查 Debug — unoptimized binary with debug informationDebug—未调试的二进制文件，带有调试信息 此设置仅可用于基于GUI的启动器。 .bat/.sh启动器将创建脚本以运行相应的可执行文件。
Video Debug (vdebug)	Toggling the debug context of the Graphics API. Available for the Development build type only. 切换Graphics API的调试上下文。仅适用于开发版本类型。
Release App / Development App / Debug App (main_release / main_dev / main_debug)	Path to the corresponding binary to be run. The binary depends on the type of build.要运行的相应二进制文件的路径。二进制文件取决于构建类型。 注意 This option is for the projects that do not use C# Component System.此选项适用于不使用 C＃组件系统的项目。 Note that the binary is defined automatically, if it remains located in the bin/ folder. If it has been moved elsewhere or rearranged in some other way, the path to the file is to be set manually.请注意，如果二进制文件仍位于bin/文件夹中，则会自动定义。如果已将其移动到其他位置或以其他方式重新排列，则该文件的路径将手动设置。
Arguments (args)	Additional start-up command-line options.其他启动命令行选项。

UnigineEditor creates the <project_name>.lconfig file that Launcher uses to run the app. If a user changes any parameters and runs the app, the changes are saved in <project_name>.lconfig. Closing Launcher without running it discards any changes.UnigineEditor创建Launcher用于运行应用程序的<project_name>.lconfig文件。如果用户更改任何参数并运行应用程序，则更改将保存在<project_name>.lconfig中。在不运行启动器的情况下关闭它会丢弃所有更改。

This feature enables you to delete all unused assets from the final build. To turn it on, check the option near the Delete Unused Assets section heading.
本部分使您可以指定要包含在最终版本中的资产。外观如下：

The Build tool scans all assets of the types specified as wildcards (including location) in the Force-Include list (*.world, *.cs, *.fbx, *.prop, etc.), automatically resolving all dependencies (an FBX asset shall be checked for all meshes, meshes shall be checked for materials assigned to their surfaces and so on...). Thus, all assets in your project that are used by the assets of the specified types are collected and included in the final build.Build工具扫描Force-Include列表中指定为通配符（包括位置）的所有类型的资产（*.world, *.cs, *.fbx, *.prop等），自动解决所有依赖性（FBX资产应 检查所有网格，检查网格中分配给其表面的材料，等等...）。 因此，将收集项目中指定类型的资产所使用的所有资产，并将其包括在最终版本中。

You can add more asset types to the list or remove existing ones by simply right-clicking on the desired line (a new line shall be inserted after the one you clicked on). You can also click Restore Defaults to reset the list to its initial state.您可以在列表中添加更多资产类型，或通过右键单击所需的行来删除现有的资产类型（在您单击的行之后应插入新行）。您也可以单击Restore Defaults将列表重置为其初始状态。

For each type of assets in the list you can specify whether to include runtime or source file. But be careful, as checking only Runtime for .png textures will result in ignoring the ones with the Unchanged option enabled (i.e. having no runtime), they simply won't be included. To check your list against such cases click Check, the following Check List window will open:对于列表中的每种资产类型，您可以指定是包含runtime还是source文件。但请注意，由于仅检查Runtime中的.png纹理会导致忽略启用Unchanged选项（即没有运行时）的纹理，因此根本不会包括它们。要检查这种情况下的列表，请单击Check，将打开以下Check List窗口：

In this window all files found in the process of scanning are listed. The ones in white are ok, but the ones in red require your attention, for example, you may mistakenly choose to include source for an asset that has a runtime. So, be sure to look through red ones. The following options are possible:在此窗口中列出了在扫描过程中找到的所有文件。白色的可以，但是红色的需要引起您的注意，例如，您可能错误地选择为具有运行时的资产包括源。因此，请务必检查所有红色的。以下选项是可能的：

• [Source and Runtime] - both boxes are checked (both source and runtime files shall be added).[Source and Runtime]-选中两个框（应同时添加source和runtime文件）。
• [Source] - when Source is checked and the asset has no runtime (only the source shall be added).[Source]-选中Use Source并且资产没有运行时（仅应添加source）。
• [Source and it has a Runtime] (shown in red) - when Source is checked, but the asset has a runtime (only the source shall be added).[Source and it has a Runtime]（以红色显示）-选中Use Source，但资产具有运行时（仅应添加source）。
• [Runtime] - when Runtime is checked, and the asset has a runtime (only the runtime shall be added).[Runtime]-选中Use Runtime且资产具有运行时（仅应添加runtime）。
• [No Runtime] (shown in red) - when Runtime is checked, but the asset has no runtime (nothing shall be added).[No Runtime]（以红色显示）-选中Use Runtime，但资产没有运行时（应添加无）。

注意

Force-Include List for the console mode is specified in the configuration file as a set of wildcards as follows:

源代码

"delete_unused": [
    {
        "pattern": "",
        "source": "",
        "primary": ""
    }
]

控制台模式的Force-Include List在配置文件中指定为一组通配符，如下所示：

源代码

"delete_unused": [
    {
        "pattern": "",
        "source": "",
        "primary": ""
    }
]

User files are added to the build folder by filling in the table with two columns:通过在表中填充两列将用户文件添加到构建文件夹：

• From (Absolute Path) — an absolute path to a source file or folder. Folders can be specified using wildcards.From (Absolute Path) —源文件或文件夹的绝对路径。可以使用通配符指定文件夹。
• To (Relative Path) — path to the destination folder that is relative of the Build Folder. It can be a folder name where the file or files are copied to, or a folder and a file name, i.e. the copied file can be renamed as well.To (Relative Path) —相对于Build Folder的目标文件夹的路径。它可以是一个或多个文件要复制到的文件夹名称，也可以是文件夹和文件名，即复制的文件也可以重命名。

There are some rules for adding user files to the build folder:将用户文件添加到构建文件夹有一些规则：

From (Absolute Path)	To (Relative Path)	评论
C:\test\<folder_name>	<another_folder_name>, or \<another_folder_name>, or \<another_folder_name>\<another_folder_name>或 \<another_folder_name>或 \<another_folder_name>\	All files and folders inside <folder_name> will be recursively copied. Thus, it doesn't matter if you use slashes or not.<folder_name>内部的所有文件和文件夹将被递归复制。因此，是否使用斜杠都没有关系。
C:\Pictures\screenshot_alb.png	\folder_with_pictures\, or folder_with_pictures\folder_with_pictures\或 folder_with_pictures	One file with the name indicated in the From column will be copied into <output_folder>\folder_with_pictures\发件人列中指定名称的一个文件将被复制到<output_folder>\folder_with_pictures\
C:\Pictures\screenshot_alb.png	\folder_with_pictures\123.png But: 123.jpg (or 123.png)\folder_with_pictures\123.png 但是：123.jpg（或123.png）	The file will be renamed. However, if the target file extension is written incorrectly (differs from the actual file extension), a new folder with such name will be created instead, i.e. the resulting path of the example destination files will be: <output_folder>\<folder_with_pictures>\<123.jpg>\screenshot_alb.png该文件将被重命名。 但是，如果目标文件扩展名写得不正确（与实际文件扩展名不同），则会创建一个具有该名称的新文件夹，即该文件的结果路径。目标文件示例为： <output_folder>\<folder_with_pictures>\<123.jpg>\screenshot_alb.png

注意

User files for the console mode are specified in the configuration file as follows:

源代码

"rules": [
    {
        "from": "",
        "to": ""
    }
]

控制台模式的用户文件在配置文件中指定如下：

源代码

"rules": [
    {
        "from": "",
        "to": ""
    }
]

When files with the same name are copied to one folder, their content is checked. If it's the same file, it would be copied once without any warning. However, if names are the same but the files are different, the dialog window will pop up to request which file should be copied.将具有相同名称的文件复制到一个文件夹时，将检查其内容。如果是同一文件，它将被复制一次，而不会发出任何警告。但是，如果名称相同但文件不同，则将弹出对话框，要求复制哪个文件。

警告

If a user file has the same name as a engine-related file, the engine-related file is copied to the Build folder with the corresponding warning in the console. The user file should be renamed manually.如果用户文件的名称与引擎相关的文件的名称相同，则引擎相关的文件将复制到Build文件夹中，并在控制台中显示相应的警告。用户文件应手动重命名。

Wildcards can also be used to define the rules for copying user files.通配符也可以用于定义复制用户文件的规则。

From (Absolute Path)	To (Relative Path)	评论
C:\test\<folder_name>\*.tga	<tga_pictures>	All files with the indicated extension from the selected folder will be copied to the specified folder.所选文件夹中具有指定扩展名的所有文件将被复制到指定文件夹。
C:\test\<folder_name>\ab*z.png	<another_folder_name>	All files with the name starting from ab and ending with z.png from the selected folder will be copied to the specified folder.所选文件夹中所有名称以ab开头并以z.png结尾的文件都将被复制到指定的文件夹中。
C:\test\<folder_name>\nn*	<another_folder_name>	All files with the name starting from nn from the selected folder will be copied to the specified folder.所选文件夹中所有名称从nn开始的文件都将被复制到指定的文件夹。
C:\*.ung	///\\\/one\\\\\\////two\\///	Slashes work differently for Windows and Linux. Windows: slashes are transformed to backslashes, all backslashes are merged into one. <output_folder>\one\two\ Linux: all slashes are merged into one, but backslashes are not transformed to slashes. <output_folder>/\\\/one\\\\\\/two\\/ 对于Windows和Linux，斜杠的工作方式有所不同。 Windows: 斜杠转换为反斜杠，所有反斜杠合并为一个。 <output_folder>\one\two\ Linux: 所有的斜杠都合并为一个，但反斜杠不会转换为斜杠。 <output_folder>/\\\/one\\\\\\/two\\/

注意

On Linux, do not use the backslash symbol for defining paths.在Linux上，请勿使用反斜杠符号定义路径。