Hey Boxers! Hope everyone is doing well. I just wanted to share a quick video update on Buildbox 3.0. We are still focusing heavily on Buildbox 2.3 and making sure it’s stable and reliable for you guys, but I thought you might want to see an update on Buildbox 3.0 as well. Have a great weekend everybody! Keep boxing! Zack Griset - Director of Customer Success
Looks awesome ! Question: with that many elements in a - as you say - super tiny scene, how does this perform on device? I can't imagine a game with the size of Zelda that won't need 2 minutes to load and doesn't lag. One of the main problem of Buildbox games from version 1 and then worse, version 2 always was the lag and low performance. Does Buildbox 3 handle performance related processes differently?
Hey Christoph! So in Buildbox 2.3 we changed our internal way of dealing with data. We rewrote our storage format. That gives you big performance improvements for loading and memory consumption. In 3.0 we are continuing to work on optimization so I hope you will love what we've got for you. To be honest, I haven't made a LOZ sized game yet, so I can't be super specific, but I spoke with the dev team just now and they said that load time is definitely a factor we are focusing on in Buildbox 3.0. Zack
Thats great news. I really think BB3 is going to be a massive game changer in all factors. Not just in game design but how everything is handled at the backend in Buildbox. Looking forward to the beta in 12 days time
So I'm totally over 2.3, had enough of it. So please do just move on with BB3. hahahah. That i will have patience for and defiantly looking forward too. can't wait for it.... looks good.
Looked at the web page source code, my country may not be allowed to open vimeo.com this site, was blocked
May be a problem with my computer, I saw on the phone, wonderful! google admob singup page I can not open, but it can be on the phone, come on
Just to be clear. Its only the very first beta that will be limited. All subsequent betas will be open to all subscribers after that.