We’ve fixed a connected download issue between the Visual Studio and Documentation module when one or the other fails.Previously, Visual Studio appeared as uninstalled, even if it had been, when you attempted to install a different Editor version.Text in various areas of the Hub wasn't displaying correctly and was accidentally cut off.When choosing modules to install with an Editor, you can now click anywhere on the row to select instead of having to click the checkbox.Some users reported that they could not create a project if it had "" in the name (where x is a one-digit number or letter).If you come across the ‘Project failed to open’ error modal, you’ll now see a link to the logs folder so that you can quickly view the info-log.json for troubleshooting or to send to support.You'll now see the appropriate submodules. When installing new Editor versions, the Hub occasionally presented incorrect Android submodules for download.We’ve resolved an issue where certain Android modules were marked as installed in the Hub but not detected by the Editor.The Hub will now inform you which Editor versions are compatible with premium packages.After a user’s session expired and they followed the steps to sign in, the “session expired” modal would still appear in the Hub.Your list of installed Editor versions will sort properly based on version number (versus alphabetically).The Hub now surfaces a message informing users which Editor versions are compatible with their Plastic SCM projects and packages.When the Hub is closed during a download, the download will be canceled. The Hub will now display a warning before closing while a download or install is in progress.PlayStation 5 is now listed as build target for those with the required license type.For first time users, the Hub will now recommend the appropriate LTS Editor version for you to install depending on whether you are using an Apple silicon or Intel machine.For some Windows users, the Hub would not start if a user tried to open a project that was located on their NAS drive.For Windows users on Unity 2022.2 and above, the Hub would not detect the installation status of Microsoft Visual Studio 2022.We’ve made improvements to the Hub’s Command-Line Interface (CLI) relating to resolving modules and Editor installations.We’ve fixed a bug that prevented some users from progressing beyond the Hub's loading screen after restarting the application.We’ve corrected an issue where some users reported that certain modules did not load correctly, though the Hub said they did.In some instances, the Hub window would appear as blank after selecting “retry” when an Editor download failed.We’ve made it easier to use your keyboard to navigate dropdown items within context menus.The Hub will now follow your OS preferences related to reduced motion settings.If you see it, please share your feedback! We’ve launched a survey in the Hub to hear what you think about Unity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |