///CacheServer//
Cache Server
Important: Cache Server only supports Asset Import Pipeline version 1. If you use Asset Import Pipeline version 2, use Unity Accelerator instead.
Unity has a completely automatic Asset pipeline. Whenever a source Asset like a .psd or an .fbx file is modified, Unity detects the change and automatically re-imports it. The imported data from the file is subsequently stored by Unity in an internal format.
This arrangement is designed to make the workflow as efficient and flexible as possible for an individual user. However, when working in a team, you may find that other users might keep making changes to Assets, all of which must be imported. Furthermore, Assets must be reimported when you switch between desktop and mobile build target platforms. The switch can therefore take a long time for large projects.
Caching the imported Assets data on the Cache Server drastically reduces the time it takes to import Assets.
Unity caches each Asset import based on:
- The Asset file itself
- The Import settings
- The Asset importer version
- The current platform
If any of the above change, Unity re-imports the Asset. Otherwise, Unity downloads it from the Cache Server.
When you use a Cache Server, you can even share Asset imports across multiple projects (that is, the work of importing is done on one computer and the results are shared with others).
Note: Once the Cache Server is set up and enabled, this process is completely automatic, so there are no additional workflow requirements. It reduces the time it takes to import projects without further intervention from the user.
Enabling a Cache Server
To enable a Cache Server:
- Open the Unity Preferences window (from the main menu: Unity > Preferences on MacOS or Edit > Preferences on Windows and Linux).
- Select Cache Server from the category list on the left. The Cache Server settings appear in the details pane on the right.
- Choose Remote or Local from the Cache Server Mode drop-down box. The properties unique to the selected mode appear.
- Set the Cache Server preferences for the mode you selected.
Tip: It is better to host the Cache Server on a separate computer if possible because of hard drive size limitations.
Note: If you have a local Cache Server with a custom location, and that location becomes unavailable, Unity displays the following warning:
Local cache directory does not exist - please check that you can access the cache folder and are able to write to it
Setting up a Cache Server as an administrator
Administrators need to set up the Cache Server computer that hosts the cached Assets.
To set up the Cache Server on a remote server:
- Download the Cache Server:
- Open Unity’s Download Archive page.
- Locate the Unity version you are using and click the Downloads button for your target server’s operating system.
- Click the Cache Server link to start the download.
- Unzip the file, which looks like this:
- Run the command script that matches your operating system. A terminal window appears, indicating that the Cache Server is running in the background:
Important: The Cache Server needs to be on a reliable computer with very large storage (much larger than the size of the project itself, as there will be multiple versions of imported resources stored). If the hard disk becomes full the Cache Server could perform slowly.
Installing the Cache Server as a service
The provided .sh
and .cmd
scripts
must be set up as a service on the server. The Cache Server can be safely killed and restarted at any time, since it uses atomic file operations.
New and legacy Cache Servers
Two Cache Server processes are started by default. The legacy Cache Server works with versions of Unity prior to version 5.0. The new Cache Server works with versions of Unity from 5.0 and up. See Cache Server configuration, below for details on configuring, enabling, and disabling the two different Cache Servers.
Cache Server configuration
If you simply start by executing the script, it launches the legacy Cache Server on port 8125 and the new Cache Server on port 8126. It also creates “cache” and “cache5.0” directories in the same directory as the script, and keep data in there. The cache directories are allowed to grow to up to 50 GB by default. You can configure the size and the location of the data using command line options, like this:
./RunOSX.command --path ~/mycachePath --size 2000000000
or
./RunOSX.command --path ~/mycachePath --port 8199 --nolegacy
You can configure the Cache Server by using the following command line options:
- Use
--port
to specify the server port. This only applies to the new Cache Server. The default value is8126
. - Use
--path
to specify the path of the cache location. This only applies to the new Cache Server. The default value is./cache5.0
. - Use
--legacypath
to specify the path of the cache location. This only applies to the legacy Cache Server. The default value is./cache
. - Use
--size
to specify the maximum cache size in bytes for both Cache Servers. Files that have not been used recently are automatically discarded when the cache size is exceeded. - Use
--nolegacy
to stop the legacy Cache Server starting. Otherwise, the legacy Cache Server is started on port8125
.
Requirements for the computer hosting the Cache Server
For best performance there must be enough RAM to hold an entire imported project folder. In addition, it is best to have a computer with a fast hard drive and fast Ethernet connection. The hard drive should also have sufficient free space. On the other hand, the Cache Server has very low CPU usage.
One of the main distinctions between the Cache Server and version control
is that its cached data can always be rebuilt locally. It is simply a tool for improving performance. For this reason it doesn’t make sense to use a Cache Server over the Internet. If you have a distributed team, you should place a separate Cache Server in each location.
The Cache Server runs optimally on a Linux or Mac OS X computer. The Windows file system is not particularly well-optimized for how the Cache Server stores data, and problems with file locking on Windows can cause issues that don’t occur on Linux or Mac OS X.
Cache Server FAQ
Will the size of my Cache Server database grow indefinitely as more and more resources get imported and stored?
The Cache Server removes Assets that have not been used for a period of time automatically (of course if those Assets are needed again, they are re-created on next usage).
Does the Cache Server work only with the Asset server?
The Cache Server is designed to be transparent to source/version control systems, so you are not restricted to using Unity’s Asset server
.
What changes cause the imported file to get regenerated?
When Unity is about to import an Asset, it generates an MD5 hash of all source data.
For a Texture, this consists of:
- The source Asset: “myTexture.psd” file
- The meta file: “myTexture.psd.meta” (Stores all importer settings)
- The internal version number of the Texture Importer
- A hash of version numbers of all AssetPostprocessors
If that hash is different from what is stored on the Cache Server, the Asset is reimported. Otherwise the cached version is downloaded. The client Unity Editor only pulls Assets from the server as they are needed - Assets don’t get pushed to each project as they change.
How do I work with Asset dependencies?
The Cache Server does not handle dependencies
. Unity’s Asset pipeline does not deal with the concept of dependencies. It is built in such a way as to avoid dependencies between Assets. The AssetPostprocessor class is a common technique used to customize the Asset importer to fit your needs. For example, you might want to add MeshColliders to some GameObjects
in an .fbx file based on their name or tag.
It is also easy to use AssetPostprocessor
to introduce dependencies. For example you might use data from a text file next to the Asset to add additional components to the imported GameObjects. This is not supported in the Cache Server. If you want to use the Cache Server, you have to remove dependency on other Assets in the project folder. Since the Cache Server doesn’t know anything about the dependency in your postprocessor, it does not know that anything has changed, and thus uses an old cached version of the Asset.
In practice there are plenty of ways you can do Asset postprocessing to work well with the Cache Server. You can use:
- The Path of the imported Asset
- Any import settings of the Asset
- The source Asset itself, or any data generated from it passed to you in the Asset postprocessor.
Are there any issues when working with Materials?
Modifying Materials that already exist might cause problems. When using the Cache Server, Unity validates that the references to Materials are maintained, but because no postprocessing calls are invoked, the contents of the Material cannot be changed when a model is imported through the Cache Server. Because of this, you might get different results when importing with and without the Cache Server.
Don’t modify materials that already exist on disk from an Asset postprocessor because if you download an fbx file through the cache server, then there is no import process running for it. So if you rely on resetting the generated materials to some generated defaults every time the model importer runs, then this Asset postprocessor will not be run when importing a cached fbx file.
Are there any Asset types which are not cached by the server?
There are a few kinds of Asset data which the server doesn’t cache. There isn’t really anything to be gained by caching script files, so the server ignores them. Also, native files used by 3D modeling software (Autodesk® Maya®, Autodesk® 3ds Max®, etc) are converted to FBX using the application itself. The Asset server does not cache the native file nor the intermediate FBX file generated in the import process. However, it is possible to benefit from the server, by exporting files as FBX from the modeling software and then adding those to the Unity project.
Cache Server
Any time an Asset changes, Unity automatically re-imports it. Setting up a Cache Server drastically reduces the time it takes to import Assets. You can set up a Cache Server using remote hosting or stored on your local computer.
Cache Server scope on the Preferences window
Property | Function |
---|---|
New Projects default asset pipeline | Select the default asset pipeline for new Projects. |
Active version | Displays the current asset pipeline version. |
Asset Pipeline v1 (deprecated) | |
Cache Server Mode | Define the Cache Server mode. Local: Use a local Cache Server on this computer. The preferences for Local storage appear. Remote: Use a Cache Server hosted on a remote computer. The preferences for Remote hosting appear. By default the Cache Server is disabled. |
Asset Pipeline v2 | |
Cache Server Default Mode | Define whether the Cache Server is enabled or disabled by default. You can override this per Project in the Unity Editor settings. |
Default IP address | Set the default IP address for the Cache Server to use. You can override this per Project in the Unity Editor settings. |
Check Connection | Click this button to attempt to connect to the remote Cache Server. |
Remote hosting
These preferences are only available when Use Cache Server is set to Remote.
Remote Cache Server preferences
Property | Function |
---|---|
IP Address | Enter the IP address of the dedicated cache server that an administrator set up. |
Check Connection | Click this button to attempt to connect to the remote Cache Server. |
Local storage
These preferences are only available when the Use Cache Server is set to Local.
Local Cache Server preferences
Property | Function |
---|---|
Maximum Cache Size (GB) | Specify the maximum size in gigabytes for the Cache Server on this computer’s storage. The minimum size is 1GB. The maximum size is 200GB. The default cache size is 10GB. |
Custom cache location | Enable this option to specify a location where you want to store the cache. |
Cache Folder Location | Click the Browse button to specify a location for the cache. |
Cache size is … | Message displaying the current size of the cache. Before clicking the Check Cache Size button, this appears as Cache size is unknown. After clicking the button, the calculated cache size appears in the message. |
Check Cache Size | Click this to find out how much storage the Local Cache Server is using. This operation can take some time to complete if you have a large project. |
Clean Cache | Delete the contents of the cache. |
Cache Folder Location | Displays the current cache folder location. |
/Hub //
如何取得UnityHub内旧版本Unity下载链接
1、请在下表中找到你需要的引擎版本,然后 复制 它;
Unity 2020.2(Alpha):
unityhub://2020.2.0a18/4f8709444da6
Unity 2020.1(Beta):
unityhub://2020.1.0b16/70ea0f8c4a3c
Unity 2019.4(LTS):
unityhub://2019.4.4f1/1f1dac67805b
unityhub://2019.4.3f1/f880dceab6fe
unityhub://2019.4.2f1/20b4642a3455
unityhub://2019.4.1f1/e6c045e14e4e
unityhub://2019.4.0f1/0af376155913
Unity 2019.3:
unityhub://2019.3.15f1/59ff3e03856d
unityhub://2019.3.14f1/2b330bf6d2d8
unityhub://2019.3.13f1/d4ddf0d95db9
unityhub://2019.3.12f1/84b23722532d
unityhub://2019.3.11f1/ceef2d848e70
unityhub://2019.3.10f1/5968d7f82152
unityhub://2019.3.9f1/e6e740a1c473
unityhub://2019.3.8f1/4ba98e9386ed
unityhub://2019.3.8f1/4ba98e9386ed
unityhub://2019.3.7f1/6437fd74d35d
unityhub://2019.3.6f1/5c3fb0a11183
unityhub://2019.3.5f1/d691e07d38ef
unityhub://2019.3.4f1/4f139db2fdbd
unityhub://2019.3.3f1/7ceaae5f7503
unityhub://2019.3.2f1/c46a3a38511e
unityhub://2019.3.1f1/89d6087839c2
unityhub://2019.3.0f6/27ab2135bccf
Unity 2019.2:
unityhub://2019.2.21f1/9d528d026557
unityhub://2019.2.20f1/c67d00285037
unityhub://2019.2.19f1/929ab4d01772
unityhub://2019.2.18f1/bbf64de26e34
unityhub://2019.2.17f1/8e603399ca02
unityhub://2019.2.16f1/b9898e2d04a4
unityhub://2019.2.15f1/dcb72c2e9334
unityhub://2019.2.14f1/49dd4e9fa428
unityhub://2019.2.13f1/e20f6c7e5017
unityhub://2019.2.12f1/b1a7e1fb4fa5
unityhub://2019.2.11f1/5f859a4cfee5
unityhub://2019.2.10f1/923acd2d43aa
unityhub://2019.2.9f1/ebce4d76e6e8
unityhub://2019.2.8f1/ff5b465c8d13
unityhub://2019.2.7f2/c96f78eb5904
unityhub://2019.2.6f1/fe82a0e88406
unityhub://2019.2.5f1/9dace1eed4cc
unityhub://2019.2.4f1/c63b2af89a85
unityhub://2019.2.3f1/8e55c27a4621
unityhub://2019.2.2f1/ab112815d860
unityhub://2019.2.1f1/ca4d5af0be6f
unityhub://2019.2.0f1/20c1667945cf
Unity 2019.1:
unityhub://2019.1.14f1/148b5891095a
unityhub://2019.1.13f1/b5956c0a61e7
unityhub://2019.1.12f1/f04f5427219e
unityhub://2019.1.11f1/9b001d489a54
unityhub://2019.1.10f1/f007ed779b7a
unityhub://2019.1.9f1/d5f1b37da199
unityhub://2019.1.8f1/7938dd008a75
unityhub://2019.1.7f1/f3c4928e5742
unityhub://2019.1.6f1/f2970305fe1c
unityhub://2019.1.5f1/0ca0f5646614
unityhub://2019.1.4f1/ffa3a7a2dd7d
unityhub://2019.1.3f1/dc414eb9ed43
unityhub://2019.1.2f1/3e18427e571f
unityhub://2019.1.1f1/fef62e97e63b
unityhub://2019.1.0f2/292b93d75a2c
Unity 2018.4 (LTS) :
unityhub://2018.4.24f1/3071911a89e9
unityhub://2018.4.23f1/c9cf1a90e812
unityhub://2018.4.22f1/3362ffbb7aa1
unityhub://2018.4.21f1/fd3915227633
unityhub://2018.4.20f1/008688490035
unityhub://2018.4.19f1/459f70f82ea4
unityhub://2018.4.18f1/61fce66342ad
unityhub://2018.4.17f1/b830f56f42f0
unityhub://2018.4.16f1/e6e9ca02b32a
unityhub://2018.4.15f1/13f5a1bf9ca1
unityhub://2018.4.14f1/05119b33d0b7
unityhub://2018.4.13f1/497f083a43af
unityhub://2018.4.12f1/59ddc4c59b4f
unityhub://2018.4.11f1/7098af2f11ea
unityhub://2018.4.10f1/a0470569e97b
unityhub://2018.4.9f1/ca372476eaba
unityhub://2018.4.8f1/9bc9d983d803
unityhub://2018.4.7f1/b9a993fd1334
unityhub://2018.4.6f1/cde1bbcc9f0d
unityhub://2018.4.5f1/7b38f8ac282e
unityhub://2018.4.4f1/5440768ff61c
unityhub://2018.4.3f1/8a9509a5aff9
unityhub://2018.4.2f1/d6fb3630ea75
unityhub://2018.4.1f1/b7c424a951c0
unityhub://2018.4.0f1/b6ffa8986c8d
Unity 2018.3:
unityhub://2018.3.14f1/d0e9f15437b1
unityhub://2018.3.13f1/06548a9e9582
unityhub://2018.3.12f1/8afd630d1f5b
unityhub://2018.3.11f1/5063218e4ab8
unityhub://2018.3.10f1/f88de2c96e63
unityhub://2018.3.9f1/947e1ea5aa8d
unityhub://2018.3.8f1/fc0fe30d6d91
unityhub://2018.3.7f1/9e14d22a41bb
unityhub://2018.3.6f1/a220877bc173
unityhub://2018.3.5f1/76b3e37670a4
unityhub://2018.3.4f1/1d952368ca3a
unityhub://2018.3.3f1/393bae82dbb8
unityhub://2018.3.2f1/b3c100a4b73a
unityhub://2018.3.1f1/bb579dc42f1d
unityhub://2018.3.0f2/6e9a27477296
Unity 2018.2:
unityhub://2018.2.21f1/a122f5dc316d
unityhub://2018.2.20f1/cef3e6c0c622
unityhub://2018.2.19f1/06990f28ba00
unityhub://2018.2.18f1/4550892b6062
unityhub://2018.2.17f1/88933597c842
unityhub://2018.2.16f1/39a4ac3d51f6
unityhub://2018.2.15f1/65e0713a5949
unityhub://2018.2.14f1/3262fb3b0716
unityhub://2018.2.13f1/83fbdcd35118
unityhub://2018.2.12f1/0a46ddfcfad4
unityhub://2018.2.11f1/38bd7dec5000
unityhub://2018.2.10f1/674aa5a67ed5
unityhub://2018.2.9f1/2207421190e9
unityhub://2018.2.8f1/ae1180820377
unityhub://2018.2.7f1/4ebd28dd9664
unityhub://2018.2.6f1/c591d9a97a0b
unityhub://2018.2.5f1/3071d1717b71
unityhub://2018.2.4f1/cb262d9ddeaf
unityhub://2018.2.3f1/1431a7d2ced7
unityhub://2018.2.2f1/c18cef34cbcd
unityhub://2018.2.1f1/1a9968d9f99c
unityhub://2018.2.0f2/787658998520
Unity 2018.1:
unityhub://2018.1.9f2/a6cc294b73ee
unityhub://2018.1.8f1/26051d4de9e9
unityhub://2018.1.7f1/4cb482063d12
unityhub://2018.1.6f1/57cc34175ccf
unityhub://2018.1.5f1/732dbf75922d
unityhub://2018.1.4f1/1a308f4ebef1
unityhub://2018.1.3f1/a53ad04f7c7f
unityhub://2018.1.2f1/a46d718d282d
unityhub://2018.1.1f1/b8cbb5de9840
unityhub://2018.1.0f2/d4d99f31acba
Unity 2017.4 (LTS) :
unityhub://2017.4.40f1/6e14067f8a9a
unityhub://2017.4.39f1/947131c5be7e
unityhub://2017.4.38f1/82ac2fb100ce
unityhub://2017.4.37f1/78b69503ebc4
unityhub://2017.4.36f1/c663def8414c
unityhub://2017.4.35f1/e57a7bcbbf0b
unityhub://2017.4.34f1/121f18246307
unityhub://2017.4.33f1/a8557a619e24
unityhub://2017.4.32f1/4da3ed968770
unityhub://2017.4.31f1/9c8dbc3421cb
unityhub://2017.4.30f1/c6fa43736cae
unityhub://2017.4.29f1/06508aa14ca1
unityhub://2017.4.28f1/e3a0f7dd2097
unityhub://2017.4.27f1/0c4b856e4c6e
unityhub://2017.4.26f1/3b349d10f010
unityhub://2017.4.25f1/9cba1c3a94f1
unityhub://2017.4.24f1/786769fc3439
unityhub://2017.4.23f1/f80c8a98b1b5
unityhub://2017.4.22f1/eb4bc6fa7f1d
unityhub://2017.4.21f1/de35fe252486
unityhub://2017.4.20f2/413dbd19b6dc
unityhub://2017.4.19f1/47cd37c28be8
unityhub://2017.4.18f1/a9236f402e28
unityhub://2017.4.17f1/05307cddbb71
unityhub://2017.4.16f1/7f7bdd1ef02b
unityhub://2017.4.15f1/5d485b4897a7
unityhub://2017.4.14f1/b28150134d55
unityhub://2017.4.13f1/6902ad48015d
unityhub://2017.4.12f1/b582b87345b1
unityhub://2017.4.11f1/8c6b8ef6d111
unityhub://2017.4.10f1/f2cce2a5991f
unityhub://2017.4.9f1/6d84dfc57ccf
unityhub://2017.4.8f1/5ab7f4878ef1
unityhub://2017.4.7f1/de9eb5ca33c5
unityhub://2017.4.6f1/c24f30193bac
unityhub://2017.4.5f1/89d1db9cb682
unityhub://2017.4.4f1/645c9050ba4d
unityhub://2017.4.3f1/21ae32b5a9cb
unityhub://2017.4.2f2/52d9cb89b362
unityhub://2017.4.1f1/9231f953d9d3
Unity 2017.3:
unityhub://2017.3.1f1/fc1d3344e6ea
unityhub://2017.3.0f3/a9f86dcd79df
Unity 2017.2:
unityhub://2017.2.5f1/588dc79c95ed
unityhub://2017.2.4f1/f1557d1f61fd
unityhub://2017.2.3f1/372229934efd
unityhub://2017.2.2f1/1f4e0f9b6a50
unityhub://2017.2.1f1/94bf3f9e6b5e
unityhub://2017.2.0f3/46dda1414e51
Unity 2017.1:
unityhub://2017.1.5f1/9758a36cfaa6
unityhub://2017.1.4f1/9fd71167a288
unityhub://2017.1.3f1/574eeb502d14
unityhub://2017.1.2f1/cc85bf6a8a04
unityhub://2017.1.1f1/5d30cf096e79
unityhub://2017.1.0f3/472613c02cf7
Unity 5:
unityhub://5.6.7f1/e80cc3114ac1
unityhub://5.6.6f2/6bac21139588
unityhub://5.6.5f1/2cac56bf7bb6
unityhub://5.6.4f1/ac7086b8d112
unityhub://5.6.3f1/d3101c3b8468
unityhub://5.6.2f1/a2913c821e27
unityhub://5.6.1f1/2860b30f0b54
unityhub://5.6.0f3/497a0f351392
Unity5.6以下版本不支持从Unity Hub中部署,故无法提供链接。
2、将复制好的内容填到浏览器地址栏并按下回车(任何浏览器都行);
在Windows下也可以在运行(Win键+R)菜单中填入
“运行”
如果有弹出窗口,请直接确认!
3、等待UnityHub被唤醒,然后选择需要的模块安装即可!
Unity Hub下面链接下载吧!
Unity Hub - Unity 3Dpublic-cdn.cloud.unity3d.com
unityhub://2017.4.37f1/78b69503ebc4 这种链接地址是哪里知道的?
Unity官网有,本质上是个唤醒链接
后面的字符串id是外网Unity官网下载界面的ReleseNotes页面里最下面的Changeset
///Installing the Unity Hub///
Installing the Unity Hub
The Unity Hub is a management tool that you can use to manage all of your Unity Projects and installations. Use the Hub to manage multiple installations of the Unity Editor along with their associated components, create new Projects, and open existing Projects.
To install the Unity Hub for Windows, macOS, and Linux visit Download Unity on the Unity website.
Unity officially supports the following Linux distributions:
- Ubuntu 16.04
- Ubuntu 18.04
- CentOS 7
Note: If Unity Hub fails to launch while you are using Linux, you might need to give UnityHub.AppImage executable permissions. To do this:
- Open your terminal.
- Go to the directory where UnityHub.AppImage is. This will be the Unity Hub directory.
- Run
chmod +x UnityHub.AppImage
.
To install and use the Unity Editor, you must have a Unity Developer Network (UDN) account. If you already have an account, sign in, choose your licenses type, and proceed to the Installing the Unity Editor section.
If you do not have an account, follow the prompts to create one. You can choose to create a Unity ID or use one of the social sign-ins. For more information on accounts and subscriptions, see Unity Organizations.
Installing the Unity Editor
To install the Editor:
-
Click the Installs tab. The default install locations are:
Windows:
C:\Program Files\Unity\Hub\Editor
Mac:
/Applications/Unity/Hub/Editor
Linux:
~/Unity/Hub/Editor
Note: If you want to change the default installation location, follow these steps:
-
From the top right corner of the Hub window, click the Gear icon.
-
In the Editor Folder Location dialog box, enter the new installation location and click Done.
-
-
Click the Add button and select a specific version of the Editor.
-
-
Hub install screen
-
Click the Next button and select the modules you want to install with the Editor. If you don’t install a component now, you can add it later if you need to. When you’ve selected all the modules you need, click Done.
-
Modules install
If you are installing multiple Editor versions, the first installation starts as soon as the download is complete. Other selected versions download simultaneously and queue to start when the current installation finishes.
The Hub displays the installation location of each Editor under the corresponding version label.
To add modules to an Editor, locate its files, or uninstall it, click the three dots next to that Editor version.
Modifying an existing Editor install
Adding existing instances of the Editor to the Hub
You can add instances of the Editor to the Hub that you installed outside of the Hub.
-
Click the Installs tab.
-
Click the Locate button to find existing installations of the Editor.
-
In the file dialog, navigate to the location of the Editor installation and select the Unity executable. On MacOS this is Unity.app. On Windows this is Unity.exe.
On Windows, the typical location of the Unity.exe is:
C:\Program Files\Unity\Editor\Unity.exe
Or
C:\Program Files\Unity<version>\Editor\Unity.exe
On macOS, the typical location of the Unity.app is:
/Applications/Unity/Hub/Editor/<version>/Unity.app
On Linux, the typical location of the Unity executable file is:
/home/<username>/Unity/Hub/Editor/<version>/Unity
-
Click the Select Editor button.
To remove the Editor from the Hub, click the three dots next to the Editor version. Removing an Editor that you added in this manner does not uninstall it or modify it in any way.
Troubleshooting for Linux
If Unity fails to start, you might need to install a missing dependency
. On Ubuntu-based distributions, use:
sudo apt install libgconf-2-4
On CentOS, you might need to install the mesa-libGLU
dependency. Use:
sudo yum install mesa-libGLU
Support for Editor versions prior to 2017.1
Sign-in status is not shared for pre–2017.1 versions of the Editor opened through the Hub. Performing tasks such as Manage License, Open Project, Create Project, and Sign in opens the Unity Launcher instead of the Hub.
If you attempt to use the Unity Hub to open an Editor version 5 or earlier and you do not have an appropriate license file, the Editor will hang on the splash screen.
To avoid this issue, run the Editor directly, external to the Unity Hub, and the Editor will load correctly even if the license file is not detected.
Using the Unity Installer to install the Unity Editor
The Unity installer is a small executable program (approximately 1 MB in size) that lets you select which components of the Unity Editor you want to download and install.
To install previous versions of the Unity Editor using the Installer, visit the Unity download archive. The archive page provides Unity Installer download links for all released versions of the Editor.
For additional information on installing the Editor using the Installer, see the 2018.3 version of the Unity Manual.
Adding modules to the Unity Editor
Use the Unity Hub to add additional components to installations of the Editor that you originally installed using the Hub.
- Open the Hub.
- Select Installs.
- Find the Editor you want to add the components to.
- Click the three dots to the right of the version label, then select Add Modules. (NOTE: If you didn’t install the Editor via the Hub, you will not see this option. To enable this option, install the Editor via the Hub.)
- In the Add Modules dialog, locate the module to add and tick its checkbox.
- When you have selected all the modules to add, select Done.
///
1. Download the Unity Hub
Follow the instructions onscreen for guidance through the installation process and setup.
Download for Windows
Download for Mac
Instructions for Linux
在使用Unity Hub下载Unity版本的时候 有时候为了方便其他人 需要把Unity的安装文件保存下来 ,需要去这个路径去找安装文件
C:\Users\XXX\AppData\Local\Temp\unityhub-xxx-xxx-xxx-xxx