The old roadmap forum post was revived yesterday and I promised to collect some information and share with you. We have three overall focus areas:
The new editor (Editor 2)
The Defold web
The Defold engine
Editor 2
The editor team is working hard to fix bugs and implement missing features in Editor 2. The ambition is to replace the old editor as soon as possible, but there’s still a way to go before this happens. I use the new editor more or less daily and despite a few kinks here and there it’s stable and functions well. We do not have an ETA for when we will replace the old editor.
Defold web
The web team is working on the new community pages, known on the forum and internally as Sticky Iron. The work is progressing nicely and we’ve done a few external tests already. A first version should be released well before end of Q2.
Defold engine
The engine team is working in two week sprints/iterations and there are many stakeholders with a claim to their backlog. You guys, the external users, are one group and game teams at King is another. We also have company and partner requirements as an influence. The fourth and final stakeholder is the team itself. With so many things influencing the backlog it’s really hard to make predictions far into the future and it makes us very reluctant to share a detailed list of the things that are currently on the horizon. A couple of things that are fairly certain to happen in Q2 are:
Full platform support for native extensions. This should be done mid-May
Particle effects in gui. Designed by Johan in this sprint. Implementation to follow.
DEF-1150 - Sound: possible to set pitch when playing sounds
DEF-1766 - Redefine input bindings at runtime (PC game critical. Workaround is horrible.)
There are bound to be more/other things shipped in the coming Defold releases. If you feel that a critical bug is being neglected or there’s a missing feature then please make your voice heard in the Bugs or Feature Request sections here on the forum.
Sorry about the vague phrashing, what I was referring to (and what was fixed in 1.2.101) was that the web profiler now also shows the Lua.Ref/Lua.Mem. The leak itself was not fixed in this release.
I was thinking about the forum feature requests and testing related stuff this weekend. I know I was one of the people who requested “DEF-1766 - Redefine input bindings at runtime”, but at the moment I am working around this pretty easily (at least for keys, I haven’t messed with gamepads yet). I generated an input map for every key and made a script that is essentially a second input map to filter out bound keys and pass them on to objects that request them. Maybe this is super inefficient and I shouldn’t do it . . . but so far it seems like an okay workaround.
I want to remind you of an important bug DEF-1733.
Applications tend to lost sound after some time in background (on iOS).
Not all users are know how to restart app (to get sound back), so they likely abandon app after all. Please fix this.
Thank you all for suggesting more issues that you feel should be prioritised! We really appreciate all the feedback we get from you, but I do hope you all understand that there is a limit to the amount of things we have time to fix each release. I can’t promise anything but we’ll certainly consider the additional issues suggested here. Thanks!
I really need them!!! 
