Our new update, Buildbox 3.4.2 is officially live! This latest update features Google’s Android app bundle (AAB format) support to help you stay updated with the new Google Play app publication requirements, starting August 1st for developers. We also added some other fixes and additions for performance improvements! Here’s a quick rundown of Buildbox 3.4.2 New Features! Android App Bundle Support Google is officially switching over from APK to Android App Bundle (AAB) as their default Android app format for all new apps or games. According to Google, app bundles are ideal for games and offer better loading and support for large assets, significantly reducing download size compared to an APK. So, we added AAB format support in Buildbox 3.4.2 to help our creators continue publishing incredible Android-based games. You can learn more about this new format on Google’s Android Developers Blog right here. Android 32-Bit Support In Buildbox 3.4.2, we also added support for Android 32-Bit. 32-Bit apps generally require less memory space to run on mobile devices than standard 64-Bit applications. Previously, Buildbox 3 only supported 64-Bit, but you now have both options with this latest release. You may update within the application or use the links below: For a detailed list of changes, you can view the full changelog below: Change Log: Added: Google Android App Bundle format (AAB) Added: Android 32-Bit support Added: Ability to follow specific asset with camera setPositionFollow() Fixed: An error occurs on Xcode when loading a game that has Use Encryption checked Fixed: Offline mode error crash Fixed: UI Screen Grid Snapping Fixed: Android encryption crash Fixed: If Collide does not update properly in certain setups Fixed: UI Screen Right Click forward/backward options don’t work as expected Fixed: User fails to drag and drop the submarine into the 3d world and proceeds to the next step in interactive tutorial Fixed: An extra obj is added when adding any asset after importing an obj and fbx files. Fixed: Label node: 2 sided mode doesn’t work Fixed: UI Joystick Move node has inconsistent max values Fixed: Changing the resolution after maximizing the preview window shows a black screen Fixed: The “Inherit color” parameter in the debris node is not functioning as intended. Fixed: When ground object is selected with Multitool, it becomes impossible to select other entities via clicking in the center editor view NOTE: The team is also aware and actively working on integrating the new Google Billing Library for Android games with in-app purchases into Buildbox in the coming months, so stay tuned. In the meantime, only new games that add in-app purchases may be affected. We appreciate your patience as we continue to update Buildbox. Feel free to reach out to our support team for further questions or guidance at support@buildbox.com. Thanks so much for your continued support and feedback. We’ll be working hard on future updates to make improvements and bring more of the features and functionality that you want to see to the platform. We can’t wait to see what you create with Buildbox 3.4.2!
Whhaaaattt better android support! Requests: Ability to press F to focus cam on object again.So, it used to be that when you select object from left side menu, you can press F and cam will jump to it. Now, you MUST click the object in the world to do it. For some reason that option to click object via menu and then press F doesn't zoom cam doesn't work anymore. This new version and past 2 or so versions. Also, Some ability to keep play screen in front. Before it would stay on top of all windows but now when you click BB, it drops behind it. So inconvenient. Not using dual screens so its important to be able to play test and modify without switching screens. Now for speed i just shrink BB to left side of screen and leave just enough room on right for play testing. AND GET BB WORLD ON ANDROID GOSH DERN IT. lol.
This is something that they heard before and are aware of, when the right time comes we will get it but not that soon (or at least that's what I think) The issue that I see is the integration of new frameworks inside bb engine before compiling it to apk
Does this mean that we can export files in AAB format directly from the BuildBox without the need for Android Studio ???
Someone explains to me what the custom ads option means. Is that like my old buildbox versions. You just need to add the admob announcements in the SDK box or you have to add them in the source code. Please.
I want to add my admob in my games to analyze traffic data. Because it helps me when launching advertising. I don't want this ADBOX option. Ps : I have the Plus version of buildbox Thanks.
I thought Buildbox always had AAB support. I've been exporting the games as AAB in Android Studio for the past two years now I think. Build then Generate Signed Bundle instead of APK in Android Studio. I chose to use AAB ever since because from what I understand it saves a few MB since from the AAB Google Play generates more optimized APKs based on the device a user has. Here's a screenshot of me mentioning AAB in the BB discord back in January 2020: Either way, I think this update is great since people would be more aware of Google Play's new policy that accepts only AAB.
A question. Before when I exported and created the abb or apk with android studio, it generated the app in the right size. Now it generates the same games in higher dimensions like a 50mb app becomes 400mb. I don't understand why. Even doing the exported test and compiling a test app exceeds 100mb. Could you tell me if I'm wrong in something? Thank you.