TapTechNews September 30th news, after three months since the last major version update, Unity Engine 1.3.0 was officially released today, covering several major directions such as WeChat mini-games, Unity Engine car version, OpenHarmony, Audio, MuseChat, and code upgrade.
For OpenHarmony, the 1.3.0 version has now upgraded the OpenHarmony SDK to version 5.0 and supports exporting projects or directly packaging with API 12. Subsequent continuous iterative upgrades will be carried out for the new functions in API 12.
In the 1.3.0 version, the support for various functional modules of OpenHarmony has been further improved, mainly with the following additions and optimizations:
Support downloading the recommended version of Node.js in TuanjieHub;
Support configuring deviceType, supportWindowMode, signingConfigs, app_id, and client_id in module.json5 in PlayerSettings;
Support automatically obtaining the compatibleSdkVersion field in the exported project build-profile.json5;
In the default template project exported, the ts file is replaced by ets, supporting developers to reference third-party ets libraries;
Support the Input.backButtonLeavesApp interface and support monitoring escape;
Support the input box to automatically get focus;
Support playing single-channel video sound;
Improve the implementation of SafeArea to reduce the calling cost of the interface;
Optimize the build time of AssetBundle.
The 1.3.0 version also fixed a series of bugs reported by developers, mainly as follows:
Fix problems related to the microphone;
Fix audio/video-related problems such as game audio being interrupted by video calls, problems such as inability to replay/silent/freezing when playing videos;
Fix the problem of misclick in the case of split-screen or modifying the resolution;
Fix the abnormal horizontal screen display problem in the Vulkan mode;
Fix the problem of reporting an error when directly calling the loadurl interface after webview is created;
Fix the problem that CrashReporting cannot report the crash information of sub-threads;
Fix the conflict problem of multiple worker threads;
Change the default value of OpenHarmonyQualitySetting to medium;
Fix the problem that when the camera is disabled, it cannot be manually operated and rendered again;
Modify the openurl path concatenation.
In the 1.3.0 version, two Packages are added to gradually improve the OpenHarmony development toolchain and enhance the development experience, which can be downloaded, installed, and used through PackageManager. TapTechNews summarizes the specific contents as follows:
OpenHarmonyHilog (v1.0.0)
Support TuanjieEditor to connect the real machine on the OpenHarmony platform to view log, memory, restore stack, etc. in real time. The main functions of v1.0.0 include:
Editor supports direct connection to the OpenHarmony real machine;
Support real-time on-demand display/screening of log;
Support restoring the stack to help quickly locate problems;
Support displaying real-time memory usage and support calculating the average consumption within a custom time interval;
Support grabbing the ArkUIDump file.
OpenHarmonySDK Kits (Betav0.0.1)
Help OH developers quickly access a series of commonly used scenario SDKs, defaulting to providing a Settings configuration panel with an in-built DemoScene, integrating the complete API calling process under each scenario, ready to use. The first version has accessed Accout&GameService, IAP, and Push, and will continue to iterate and access more Kits in the future. The main functions of Betav0.0.1 include:
1. Settings panel:
Provide the public configuration items for accessing SDK Kits to fill in and keep synchronous changes with PlayerSettings;
Can tick to access the SDKKit in one click, support custom configuration item filling for each SDKKit, and support one-click opening of the DemoScene to experience the whole access process.
2. DemoScenes:
Account&GameServiceDemo covers initialization, login/logout, binding/unbinding of the Player, verifying Player information and reporting, GamePerformance initialization and update, etc.;
IAPDemo covers verifying the payment environment, querying various types of product information, the complete purchase process, and the complete subscription process;
PushDemo supports obtaining the Token and supports simulating sending and receiving Pushmessages.