Remind me again which issue it is you are referring to?
Aha! It seems like a sign to me I should back to my gui-only “color by number” prototype
And… any news about D8
on Android?
D8 support is still on hold for a little while.
By increasing the build tool number for Android, internal addresses started to increase well above the 47 bit range supported by LuaJIT 2.0.3 beta. Which means we need to update to a much newer LuaJIT version, which is now a task we need to be done first.
Tell me please how’s it going the texture compression question (in particular, to bring back webp_lossy as an option) still working on 1.2.179 because of it… (also I haven’t seen the issue on github about it in to-do section)
Well, other issues have been taking precedence, but we’ll look into it for sure.
Given that we’re adding a new api for our pipeline, I’m more keen to add the WebP functionality there to be honest, rather than putting it back into the core engine.
It’s not an issue. It a feature.
To be serious, maybe a project demo or something like that to help speed up that sprite alpha trimming feature? We really need that since we have 2 projects with a tons of “untrimmed” atlases. One of those projects was put on hold due to many reasons, but sprite trimming was not the least one.
Many thanks!
It’s incredible how the game engine is growing! I think it has surpassed Godot in many aspects! Well, only the editor could see some improvements, besides that, everything looks fine
It’s very good for many indies devs.
Thank you!
We’re currently in the process of securing development time on the editor to handle the most urgent issues. It will take another few months before we see any major changes, but we really do want to be able to give the editor a bit of love!
thanks for all! how about add visual joints editor?
Yes, that would be nice
Saw something similar (not quite). Old project builds & run from editor without errors. But bundle has failed with message:
Possibly related to this?
Nope, that’s c-ares DNS library being removed.
We will push a fix to the beta branch on Monday. It is related to the changes we are doing to the build pipeline. I actually thought we had fixed this on Friday when we fixed a classloader related problem in bob.
There is now a new beta “5a9c358704e7f599cf4b3f33527357ca958735f7” with a fix for the spine related error messages. (@AGulev, @aglitchman, @dmitriy)
We’ve decided to extend the beta period with one week due to some new fixes.
We needed to fix a regression so we moved up the removal of the cares dns lookup library from the engine. This however is a bigger change, so to be cautios we decided to extend the beta period.
We’ve also updated the “–use-vanilla-lua” option to bob.jar, which now allows you to store the Lua/.script files unencrypted in your archive.
Since this last update touches a lot of the network code, it would be good if some of you could try it out one extra time to make sure it still works as expected for you on e.g. iOS/Android.