- 1 Update Overview:
- 2 Cautions
- 3 Update Schedule and Details
- 4 What Artists Must Do
- 4.1 Confirming Compatibility Issues Using STYLY 2.0 β Version
- 4.2 Unity2019 Compatibility Conversion Process (in case users encounter incompatibility issues when testing their project using the β Version)
With this update, STYLY requires artists to upgrade their Unity to the Unity2019 version.
With this update, STYLY will be upgraded to the latest version of 2.0.
We recommend choosing the Unity2019.3.3f1 for your upgrade to Unity2019.
(Hereinafter, we will refer to the new STYLY System as STYLY 2.0, and the upgraded STYLY Studio as STYLY Studio 2.0.)
Reasons for the Update
Until now, STYLY has been designed to work with the Unity2017. However, as time flows, many STYLY artists wish to utilize the latest evolved functions found in the newest version of the Unity engine.
Understanding this wish, our team has continued to planning, adjusting, developing, and verifying this latest update with which artists can utilize all of the latest functions in Unity2019 to create their artworks in STYLY. As spring approaches, our team has decided to release this new and exciting update for all of our users.
Through this latest update, STYLY’s system will be upgraded thoroughly to the newest version.
With this latest update, artists can not only utilize Unity2019’s latest functions to create their artwork but also quickly load and expand their favorite scene in STYLY Studio, Web Player, and VR Application.
Furthermore, this latest update will also serve as the foundation for the development of further services unique to STYLY, such as the addition of the Studio function in STYLY Mobile Application (available for Smartphones & Tablets AR) or better compatibility with the latest AR/MR glasses currently in development. A new exciting future is waiting ahead.
Regarding the developed scenes (Including scenes being developed)
Most of the uploaded Prefab and Scene, which have been developed using Unity2017, will work correctly in STYLY 2.0. However, a few of these developed Prefab and Scene may encounter compatibility issues with the latest update.
In other words, STYLY Scenes, which have been developed using these Prefab and Scene may appear to be different or may work incorrectly after this latest update.
Our team will provide artists with the β Version (including the VR Application and STYLY Studio) of STYLY 2.0 to test the compatibility of your developed scenes.
After testing with the β Version of STYLY 2.0, artists should immediately convert their developed resources using Unity2019 (hereinafter referred to as Unity2019 compatible conversion) in case any incompatibility issues are found.
Artists and users could find further details regarding the Unity2019 compatibility conversion process and STYLY 2.0 β Version in the “What Artists Must Do” section of this article.
Resources Incompatible with STYLY 2.0
At the moment, our team has confirmed the following types of incompatible issues with the latest STYLY 2.0:
◆ Timeline developed using Unity2017 isn’t working.
→ This issue can be resolved using the Unity2019 compatibility conversion process.
◆ Shader created using Unity2017 sometimes won’t operate as expected.
→ Typically, this issue can be resolved using the Unity2019 compatibility conversion process. However, there are a few cases in which the created Shader is incompatible with Unity2019. In such cases, please kindly consider using a different Shader, which is compatible with Unity2019.
◆ The VR Application continued to crash when loading a specific asset.
→ There is a high probability that this issue can be resolved using the Unity2019 compatibility conversion process.
◆ Some created particles work differently compared to the previous client
→ For example, the size of the generated particles may be incorrectly displayed in case their maximum and minimum size has been specified. Such situations can be resolved using the Unity2019 compatibility conversion process (however, users will have to readjust the particles’ parameters manually using Unity2019).
◆ The shader shows various abnormalities when using MToon Shader together with the Android environment (Daydream/Oculus Go&Quest)
Please understand that there might be other smaller incompatibility issues that our team hasn’t been confirmed yet.
Creating a New Scene
Our team recommends Unity users and artists to use Unity2019 for creating and developing new scenes after this article has been published.
However, please also kindly understand that before this latest update, assets created using Unity2019 may not work correctly under the current platform. Therefore, our team recommends users and artists to refrain from placing these assets in the current STYLY Studio and using the Publish function. Users should retry these functions once the update process has been completed.
There are, however, no issues with placing and developing scenes using assets not created in Unity (for example, STYLY’s presets).
Update Schedule and Details
The latest update will be conducted according to the schedule specified below. (Users can scroll vertically to view the entire table)
Web Player & STYLY Plugin
|STYLY Application (VR)|
|From this article’s publishing date to||
STYLY 2.0’s β Version will be available during the following period
The period during which artists can respond and test compatibility
Testing compatibility using the provided β Version (in addition to the Unity2019 compatibility conversion process)
β Version： Unity2019（※3）
β Version： Unity2019
STYLY 2.0’s Official Release
|―||Official Version：Unity2019||Official Version：Unity2019|
Editing and Publish developed scenes using the Official Version of STYLY Studio
※1 Our team will notify users regarding any changes in the schedule for the system update this time via Twitter and other platforms.
※2 Our team schedules to provide users and artists with STYLY’s old version (compatible with Unity2017) as a separate platform. Our team will notify users with methods for accessing this platform at a later date. However, please kindly understand that this old version will only be available for a set period. Our recommend users and artists to transfer their projects to the new platform as soon as possible.
What Artists Must Do
In this section, we will explain the various steps and methods that artists should and must do before the update, as mentioned in the Caution section.
Confirming Compatibility Issues Using STYLY 2.0 β Version
Before the official release of the latest version, our team would like to ask artists and users to kindly confirm for any compatibility issues, including any errors with the operation and appearances of their current project using the provided STYLY 2.0 β Version.
STYLY 2.0 β Version VR Application
Users and artists can download the application for their favorite platform from the following links:
《Application Download Link》
◆ For PC (SteamVR):
Offered on Steam’s beta branch “2.0-beta
Please open the property of STYLY from the library of Steam and select the beta branch “2.0-beta” to replace the STYLY application installed on the PC.
For more information on how to set up the Steam beta branch, please refer to the “STYLY for Looking Glass beta” article below.
◆For Oculus Go/Quest:
STYLY Studio 2.0 β Version
Users can access the STYLY 2.0 β Version using the following link:
《Link for Accessing STYLY Studio》
※Users who haven’t logged into their STYLY account will be redirected to the original official version after pressing the “Launch” button from the Login screen. In such cases, users can reaccess the β Version from the following link after logging into their STYLY account.
STYLY Plugin for Unity2019 β Version
Please use this beta version of Pluigin if you are going to migrate to Unity2019 or if you are going to create with Unity2019 first.
Unity2019 Compatibility Conversion Process (in case users encounter incompatibility issues when testing their project using the β Version)
After testing their developed scenes using the provided β Version, artists and users should carry out the Unity2019 compatibility conversion process to fix any incompatibility issues such as incorrect operations or abnormalities in appearance should they are found.
Most of this process requires users to reupload the used resources and developed scenes from Unity2019.
The detailed steps and other details will be carefully explained within the manual, which will be included at the end of this article. Users should carefully refer to this manual and carry out the necessary processes to ensure the best compatibility for their project.
《Link to the Manual of Detailed Steps for Compatibility Conversion Process》