04-03-2020, 10:46 AM
The Future of the Defold Game Engine
<div><p>The <a href="https://defold.com/">Defold</a> game engine is a free cross platform 2D focused game engine from King, we previously covered <a href="https://devga.me/tutorials/defold-crash-course-tutorial/">here</a> and <a href="https://www.gamefromscratch.com/page/Defold-Engine-Tutorial-Series.aspx">here</a> as well as a video tutorial <a href="https://youtu.be/VFh2mfqmiRU">here</a>. The Defold team recently released an update on the future roadmap of the Defold game engine.</p>
<div id>
<h3>iOS </h3>
<p>We will continue to keep the iOS platform support up to date with the latest iOS versions and requirements. Specific iOS tasks in no particular order:</p>
<h5>Metal </h5>
<p>Apple has announced that OpenGL will be deprecated on iOS and macOS, but no date has been announced. We have worked during 2019 to add a new Vulkan based graphics backend. This work is nearing completion and it will allow us to use MoltenVK on iOS and macOS. MoltenVK is a Vulkan Portability implementation. It layers a subset of the high-performance, industry-standard Vulkan graphics and compute API over Apple’s Metal graphics framework, enabling Vulkan applications to run on iOS and macOS. We have worked together with members of the Khronos Group to benchmark our implementation and have received only a few points of improvement.</p>
<h5>Sign in with Apple </h5>
<p>Apple will require that apps that authenticate or set up user accounts must support Sign in with Apple (SIWA). The deadline is June 30, 2020. We will release SIWA support through a native extension in Q2 of 2020. The extension has been developed at King and has already been tested in production.</p>
<h5>Storyboard launch screens </h5>
<p>Apple will require that apps use Xcode storyboards as the app’s launch screen. The deadline is June 30, 2020. We will automatically create a launch screen storyboard from the launch images set in game.project.</p>
<h3>Android </h3>
<p>We will continue to keep the Android platform support up to date with the latest Android requirements. We are collaborating with the Android and Google Play partnership teams to identify important tasks. The top four tasks in order of priority are:</p>
<h5>Billing </h5>
<p>Google Play Billing is a service that lets you sell digital content on Android. We will add support for the new Billing API via the existing <a href="https://www.github.com/defold/extension-iap">IAP extension</a>.</p>
<h5>Google Play Game Services </h5>
<p>We will continue to improve on the existing <a href="https://www.github.com/defold/extension-gpgs">Google Play Game Services extension</a> to ensure that it supports all of the latest features of Google Play Game Services.</p>
<h5>Android App Bundles </h5>
<p>Android App Bundle is a publishing format that includes all your app’s compiled code and resources, and defers APK generation and signing to Google Play. Google Play uses your app bundle to generate and serve optimized APKs for each device configuration, so only the code and resources that are needed for a specific device are downloaded to run your app. We will initially add support for basic bundling of applications using Android App Bundles and then expand upon the feature as needed.</p>
<h5>Google Play Instant </h5>
<p>Google Play Instant enables native games to launch on devices running Android 5.0 (API level 21) or higher without being installed. By allowing users to run an instant game, known as providing an instant experience, you improve your game’s discovery, which helps drive more active users or installations.</p>
<h3>HTML5 </h3>
<p>We will focus on increased performance and reduced application size on HTML5. We will when possible update to newer versions of Emscripten and WebAssembly to achieve this.</p>
<h3>Desktop </h3>
<p>On desktop our only identified focus area is to add the ability to run the engine loop while the window is in the background.</p>
<h3>Editor </h3>
<p>We will mainly focus on performance and stability improvements in the editor. In terms of new features we have identified the following (in no particular order):</p>
<h5>Improved 3D support </h5>
<p>In 2019 we added support for perspective cameras and made some improvements to how collision shapes were visualised. These changes made it easier to work with and place 3D models in a collection, but there are still many improvements to be made to scene navigation when working in a 3D.</p>
<h5>Auto-tiling </h5>
<p>While we did some minor improvements to the tilemap system in 2019 (better tile palette and interleaved layers) we have so far left out auto-tiling. Auto-tiling can really speed up tilemap editing and it is the next big feature to add for the tilemap editor.</p>
<h5>Editor extensions </h5>
<p>We plan to expand the existing system for editor scripts to allow for more complex operations and we will look at how to customize the UI and/or add new UI widgets using editor scripts.</p>
<h5>GUI layouts and templates </h5>
<p>The system with GUI layouts and templates where one or both involve value overrides is fairly complex and hard to work with from a code maintenance perspective. We plan to review the system and possibly simplify it.</p>
<h3>Engine </h3>
<p>In 2019 we made several changes to improve editor stability. Two examples of this were reduced ANRs on Android and a standardized application loop on iOS. In 2020 we will continue to identify and fix stability issues in the engine. Besides stability improvements we will also work on the following features (in no particular order):</p>
<h5>Sound threading </h5>
<p>Sound playback is currently done on the main thread together with the rest of the game loop. This can become a problem if loading large resources while playing sound, resulting in playback stutter. The solution is to do sound playback on a separate thread to avoid stutter when loading content.</p>
<h5>Physics decoupling </h5>
<p>Physics is currently running at the same rate as the rest of the game loop. We will try to decouple the physics simulation from the game loop by running the simulation on a separate thread and optionally with a different number of updates per second.</p>
<h5>Spine as an extension </h5>
<p>We will look into the possibility of using the official Spine runtime as an extension and a replacement for the existing custom made native Spine support. This will allow the use of newer versions of Spine, something that currently is not possible with the existing and custom Spine runtime.</p>
<h5>Physics as an extension </h5>
<p>We will look into the possibility of moving the Box2D and Bullet3D physics engines to a native extension. This will allow the community to update or replace the physics simulation with an update version or completely different implementation.</p>
<h5>Live update </h5>
<p>We’re very happy to see that the live update functionality is used in several different scenarios (from Android Expansion Files to Steam DLCs). We have with the help of the community identified several improvements and we plan to deliver the most critical improvements in 2020.</p>
<h5>Mesh component </h5>
<p>The custom mesh component will be released in Q2 of 2020.</p>
<h5>Vulkan </h5>
<p>We will release support for Vulkan on all systems where it is supported. On Android it will be used by default on newer devices. On iOS it will be used under the hood to be able to use MoltenVK (see iOS above).</p>
<h3>Build server </h3>
<p>The Defold build server for native extensions will be open sourced in Q2 of 2020 to allow developers to build locally or set up their own build servers to cut the dependency to the Defold provided build service.</p>
</div>
<p>You can learn more about the Defold Game engine roadmap in the <a href="https://youtu.be/iaDiOy-eYA4">video</a> below. The tutorial mentioned in the video is open source and <a href="https://github.com/defold/tutorial-platformer">available here</a> on Github.</p>
</div>
https://www.sickgaming.net/blog/2020/04/...me-engine/
<div><p>The <a href="https://defold.com/">Defold</a> game engine is a free cross platform 2D focused game engine from King, we previously covered <a href="https://devga.me/tutorials/defold-crash-course-tutorial/">here</a> and <a href="https://www.gamefromscratch.com/page/Defold-Engine-Tutorial-Series.aspx">here</a> as well as a video tutorial <a href="https://youtu.be/VFh2mfqmiRU">here</a>. The Defold team recently released an update on the future roadmap of the Defold game engine.</p>
<div id>
<h3>iOS </h3>
<p>We will continue to keep the iOS platform support up to date with the latest iOS versions and requirements. Specific iOS tasks in no particular order:</p>
<h5>Metal </h5>
<p>Apple has announced that OpenGL will be deprecated on iOS and macOS, but no date has been announced. We have worked during 2019 to add a new Vulkan based graphics backend. This work is nearing completion and it will allow us to use MoltenVK on iOS and macOS. MoltenVK is a Vulkan Portability implementation. It layers a subset of the high-performance, industry-standard Vulkan graphics and compute API over Apple’s Metal graphics framework, enabling Vulkan applications to run on iOS and macOS. We have worked together with members of the Khronos Group to benchmark our implementation and have received only a few points of improvement.</p>
<h5>Sign in with Apple </h5>
<p>Apple will require that apps that authenticate or set up user accounts must support Sign in with Apple (SIWA). The deadline is June 30, 2020. We will release SIWA support through a native extension in Q2 of 2020. The extension has been developed at King and has already been tested in production.</p>
<h5>Storyboard launch screens </h5>
<p>Apple will require that apps use Xcode storyboards as the app’s launch screen. The deadline is June 30, 2020. We will automatically create a launch screen storyboard from the launch images set in game.project.</p>
<h3>Android </h3>
<p>We will continue to keep the Android platform support up to date with the latest Android requirements. We are collaborating with the Android and Google Play partnership teams to identify important tasks. The top four tasks in order of priority are:</p>
<h5>Billing </h5>
<p>Google Play Billing is a service that lets you sell digital content on Android. We will add support for the new Billing API via the existing <a href="https://www.github.com/defold/extension-iap">IAP extension</a>.</p>
<h5>Google Play Game Services </h5>
<p>We will continue to improve on the existing <a href="https://www.github.com/defold/extension-gpgs">Google Play Game Services extension</a> to ensure that it supports all of the latest features of Google Play Game Services.</p>
<h5>Android App Bundles </h5>
<p>Android App Bundle is a publishing format that includes all your app’s compiled code and resources, and defers APK generation and signing to Google Play. Google Play uses your app bundle to generate and serve optimized APKs for each device configuration, so only the code and resources that are needed for a specific device are downloaded to run your app. We will initially add support for basic bundling of applications using Android App Bundles and then expand upon the feature as needed.</p>
<h5>Google Play Instant </h5>
<p>Google Play Instant enables native games to launch on devices running Android 5.0 (API level 21) or higher without being installed. By allowing users to run an instant game, known as providing an instant experience, you improve your game’s discovery, which helps drive more active users or installations.</p>
<h3>HTML5 </h3>
<p>We will focus on increased performance and reduced application size on HTML5. We will when possible update to newer versions of Emscripten and WebAssembly to achieve this.</p>
<h3>Desktop </h3>
<p>On desktop our only identified focus area is to add the ability to run the engine loop while the window is in the background.</p>
<h3>Editor </h3>
<p>We will mainly focus on performance and stability improvements in the editor. In terms of new features we have identified the following (in no particular order):</p>
<h5>Improved 3D support </h5>
<p>In 2019 we added support for perspective cameras and made some improvements to how collision shapes were visualised. These changes made it easier to work with and place 3D models in a collection, but there are still many improvements to be made to scene navigation when working in a 3D.</p>
<h5>Auto-tiling </h5>
<p>While we did some minor improvements to the tilemap system in 2019 (better tile palette and interleaved layers) we have so far left out auto-tiling. Auto-tiling can really speed up tilemap editing and it is the next big feature to add for the tilemap editor.</p>
<h5>Editor extensions </h5>
<p>We plan to expand the existing system for editor scripts to allow for more complex operations and we will look at how to customize the UI and/or add new UI widgets using editor scripts.</p>
<h5>GUI layouts and templates </h5>
<p>The system with GUI layouts and templates where one or both involve value overrides is fairly complex and hard to work with from a code maintenance perspective. We plan to review the system and possibly simplify it.</p>
<h3>Engine </h3>
<p>In 2019 we made several changes to improve editor stability. Two examples of this were reduced ANRs on Android and a standardized application loop on iOS. In 2020 we will continue to identify and fix stability issues in the engine. Besides stability improvements we will also work on the following features (in no particular order):</p>
<h5>Sound threading </h5>
<p>Sound playback is currently done on the main thread together with the rest of the game loop. This can become a problem if loading large resources while playing sound, resulting in playback stutter. The solution is to do sound playback on a separate thread to avoid stutter when loading content.</p>
<h5>Physics decoupling </h5>
<p>Physics is currently running at the same rate as the rest of the game loop. We will try to decouple the physics simulation from the game loop by running the simulation on a separate thread and optionally with a different number of updates per second.</p>
<h5>Spine as an extension </h5>
<p>We will look into the possibility of using the official Spine runtime as an extension and a replacement for the existing custom made native Spine support. This will allow the use of newer versions of Spine, something that currently is not possible with the existing and custom Spine runtime.</p>
<h5>Physics as an extension </h5>
<p>We will look into the possibility of moving the Box2D and Bullet3D physics engines to a native extension. This will allow the community to update or replace the physics simulation with an update version or completely different implementation.</p>
<h5>Live update </h5>
<p>We’re very happy to see that the live update functionality is used in several different scenarios (from Android Expansion Files to Steam DLCs). We have with the help of the community identified several improvements and we plan to deliver the most critical improvements in 2020.</p>
<h5>Mesh component </h5>
<p>The custom mesh component will be released in Q2 of 2020.</p>
<h5>Vulkan </h5>
<p>We will release support for Vulkan on all systems where it is supported. On Android it will be used by default on newer devices. On iOS it will be used under the hood to be able to use MoltenVK (see iOS above).</p>
<h3>Build server </h3>
<p>The Defold build server for native extensions will be open sourced in Q2 of 2020 to allow developers to build locally or set up their own build servers to cut the dependency to the Defold provided build service.</p>
</div>
<p>You can learn more about the Defold Game engine roadmap in the <a href="https://youtu.be/iaDiOy-eYA4">video</a> below. The tutorial mentioned in the video is open source and <a href="https://github.com/defold/tutorial-platformer">available here</a> on Github.</p>
</div>
https://www.sickgaming.net/blog/2020/04/...me-engine/