Resolve the issue where Google Play Store requires apps to support 16KB page sizes as mentioned here and Support Android 15 SDK.
depilz has made some improvements with buffering for mesh updates, which will significantly improve performance compared to updating via Lua tables.
With the unpacking alignment, we can now create Image Masks without requiring divisible by 4 size. Additionally, it also fixes pixel padding issues with the bytemap plugin when generating textures of arbitrary sizes.
I donāt know if there were details and comments here about the Solar2D updates, but this post is to be congratulated, itās a simple detail, but it makes all the difference for some.
Yeah, everyone is welcome to discuss the update here, as well as possibly report bugs. This is just a post based on my personal understanding of the updates.
There have been a lot of updates with cool new features recently, I think a lot of people might have missed it.
I remember struggling when I first started learning the engine because I didnāt know image mask layers had to be in multiples of 4. This is a great update.
Thank you @Kan98
It would be very helpful to update the official documentation with these changes. For example, to strike through the requirement text in the mask image.
As I mentioned before, Solar2D is only really known to users who are active on this forum, because many changes and fixes havenāt been documented in the official docs. If we want better support for our engine, updates alone arenāt enoughāitās also crucial to document them.
Iāve always noticed that the fix for using the latest version of Xcode is just updating the Xcode version number in a build.yml file.
Would it be practical to add a workaround where the developer can add their local Xcode version number to a separate file which gets read and overwrites this number? That would let devs use the latest version of Xcode immediately without Vlad/Scott/etc having to update this as quickly. Of course it would then be on the dev to ensure they test their builds thoroughly before releasing.
Or is there some complication that would prevent this from working?
According to my know, Solar2D uses templates to build apps for each platform, these templates (Including the target Xcode version) will be generated when Solar2D builds a new release.
This means, if you need to update your xcode version, you need to rebuild the templates for Apple platform and replace it with your current templates.
Do you have pages in mind that are out of date so we can look into it? Iāve been trying to keep the pages up-to-date for the ones I can track. Iāve probably missed on some but a list could help.
@Kan98 can you tell which of the following requirements are no longer relevant so that I can add a warning as such?
@bgmadclown Different manifestation of the problem, but it was the same faulty mechanism under the hood. (With similar behavior: either an outright crash or weird-looking shortening rows of pixels, when given a ābadā width.) There was a second problem with updatesāafter the texture was created, but for example when setting pixels in a mask-type memory bitmapāthat @Kan98 flushed out and also fixed.
Speaking of ānever got around toā, I do have notes for a lot of 3713+ stuff, and probably a few odds and ends before that. Very rough drafts in many cases, but I suppose itās something. There is a lot of non-API material that wants some love too (maybe it should be in āguidesā), butā¦ well, hasnāt had any.
In the plugin.admob documentation, under the adsRequest(https://docs.coronalabs.com/plugin/admob/event/adsRequest/phase.html) event phases, the closed phase is described as occurring only when an interstitial ad is closed. However, in my testing I found that closed also fires for other ad formatsāexcluding bannersālike appOpen, rewardedInterstitial, and rewardedVideo.
As Kan said, yes, whenever a new version of Xcode is released, a supported GitHub CI runner image is required. Then, Solar2D uses the new Xcode version to compile the template within it and then releases the version. If you want to obtain the engine core compiled with the new Xcode version locally, apart from compiling the source code locally, you can only wait for the new template to be released.
However, it might be possible to accelerate the generation of the new template, for example, by adding a trigger that automatically or manually initiates the compilation upon the appearance of a new GitHub CI runner image, and then obtain the template.
Even further, consider separating the variable content from the release version, such as placing it in a plugin. However, this is generally only applicable to Xcode version updates that do not require manual intervention.
Iām not very satisfied with the current Apple integration, but I canāt start working on it at the moment.
It doesnāt fully support Apple Silicon and the device simulator. The fragmentation of platforms and architectures leads to duplicate code, which could potentially be resolved by using XCFramework or Pods, and the template, also the plugins, should also be reviewed together to make the Apple integration more flexible.
Just sent the PR making the necessary change.