Then there is the performance for the rendering engine. WebAssembly being now a thing, it’s also a good target for the future to use to power small or large parts of the game engines (collision, etc…) with unmatched performance (almost native).Īll of this discussion is about raw computing performance itself.Speaking of JIT, most recent browser engines (V8 for Chrome, WebKit for Safari) are doing Just In Time compilation of JavaScript functions that are considered “hot”, compiling them to native code bringing really good performance.The issue with SpiderMonkey is that it was a very old version in Cocos2d-JS and was not benefiting of JIT (Just in time compilation) from recent JS engines. I’m unsure about if this is still the case for Cocos Creator game engine (it is based on Cocos2d-JS), in particular I’m unsure if they changed to another JS engine on Android/iOS. Cocos2d-JS is based on a native rendering engine (OpenGL) and the JavaScript source code of the game (including GDevelop game engine) is ran in a JS engine embedded in the game (SpiderMonkey at least on version of Cocos2d-JS).I’d like 4ian to comment so we can have a better overview of this, if possibleĪ few clarifications on performance itself: While this will surely take time, I really would like GDevelop to become very widespread, as I enjoy using it a whole more than Unity or Gamemaker since it allows me to focus on creating the games.Įither way thanks as always for all the hard work! Of course, I know right now the priority is to stabilize the game engine and make it as accessible and usable as possible so i’m sure this feature won’t be worked soon, but even then please consider it! Don’t drop it unless there’s a better alternative. Having an optional “native” target as the original GDevelop (4.x and below) would make GDevelop even more appealing to experienced game developers. Even if your Desktop can handle it, Mobiles have a worse time dealing with these kind of virtualized applications. Even the most advanced JS games have to be ported (rewritten) for consoles and depending on the required performance for mobile devices too.Īs users or developers, we shouldn’t rely on having a “faster” computer or processor to run a simple game, but you can be sure that you need to optimize it when doing a complex game. Regardless of the advances in computer science wrappers can only get so far, Cordova, Electron, and similar technologies, while impressive are not yet ideal. If it’s not going to be continued, I’d like to know what can we do to help it become a reality or to spark interest once more so development can be resumed? Because of this, I wanted to ask what’s the state of this feature and if it’s going to be continued in the near future?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |