- Joined
- Jan 28, 2011
- Messages
- 97,399
Tags: BattleTech; Chris Klimecky; Harebrained Schemes
The BattleTech beta was supposed to start on March 15th, but it appears that Harebrained have run into some serious last minute technical issues. The latest Kickstarter update explains in detail:
Youch. Kudos for the extreme transparency, though. That's how you do crowdfunding.
The BattleTech beta was supposed to start on March 15th, but it appears that Harebrained have run into some serious last minute technical issues. The latest Kickstarter update explains in detail:
Greetings MechWarriors! Klimecky back again with important news about our Backer Beta. A series of unfortunate events prevents us from hitting our target release date and, as promised in our last update, we’re letting you know as far in advance as we can. This change may come as a surprise, given it’s only a few weeks after announcing the target release date but sometimes game development throws us curve balls at just the wrong moment. As a wise man once said, “Shit happens.”
Developers are constantly weighing risks vs rewards during a project, often with incomplete information. In this case we made two big decisions in the leadup to Beta and both turned out to have a bigger impact on the project than we planned for. Here’s what happened:
Now that our technical issues are behind us, the team is focused on quality and on delivering an experience that shows the world why HBS loves BattleTech and why everyone else should, too. As soon as we have a new target date that we can confidently announce, we’ll send out another update. We are dedicated to delivering a great Backer Beta, even if that means taking a little longer with it.
Regarding the final release date for BATTLETECH: As noted during our livestreamed dev Q&As and on our forums, once we unlocked all of our Kickstarter stretch goals, our estimated release date of May was no longer valid. Way back then we said things like "Summer 2017.” Now that we're further along, we're targeting a Late Summer / Fall release of the game - but we won't be announcing a more exact release date until we're much closer in!
Developers are constantly weighing risks vs rewards during a project, often with incomplete information. In this case we made two big decisions in the leadup to Beta and both turned out to have a bigger impact on the project than we planned for. Here’s what happened:
- Our development infrastructure desperately needed an upgrade but the fixes caused lots of short-term headaches. HBS has a history of “toughing it out” and working with sub-optimal back-end tools because we want as much development time as possible to be spent on game features and fun. Eventually however, a system becomes too painful to use and we bite the bullet and pay the development price. In this case, we had two vital systems that required improvement for the Backer Beta, so we decided to “tear off the bandage”, hire a professional IT contractor, and get all the work done at once so our engineers could stay focused on the game.
Unfortunately, the infrastructure upgrade process caused several issues including delays in getting new versions of the game built. This consumed time from our Lead Engineer, our Test Lead, and myself. Without the ability to test our work in new “builds” of the game, progress slowed. It has taken the better part of 3 weeks to get back on track, but we finally feel like we've cleared the hurdle.
- An upgrade to the latest version of Unity brought the game editor to its knees. Unity is the game engine we build BATTLETECH on top of and when the company updates its software, game developers need to take a hard look before deciding to take the plunge and install it. In this case, we determined that the update was required for beta because it contained performance optimizations that would greatly improve the gameplay experience for nearly all our participants and for some, make the game playable at all on their machines.
Now, we know from experience that whenever you update major software in the middle of development things WILL break, so we diligently planned time for integration and bug fixing. Unfortunately, while the upgrade succeeded in improving the game’s performance, the changes in Unity broke a lot more of our systems than anticipated - with these consequences proving more time-consuming to troubleshoot and address than any other Unity upgrade we’ve done in the past (including on previous projects). We were relieved to learn that at 2:30am this morning, our engineering and technical art team removed the final productivity sink and were able to start our Monday with a solid infrastructure and performant game editor.
Now that our technical issues are behind us, the team is focused on quality and on delivering an experience that shows the world why HBS loves BattleTech and why everyone else should, too. As soon as we have a new target date that we can confidently announce, we’ll send out another update. We are dedicated to delivering a great Backer Beta, even if that means taking a little longer with it.
Regarding the final release date for BATTLETECH: As noted during our livestreamed dev Q&As and on our forums, once we unlocked all of our Kickstarter stretch goals, our estimated release date of May was no longer valid. Way back then we said things like "Summer 2017.” Now that we're further along, we're targeting a Late Summer / Fall release of the game - but we won't be announcing a more exact release date until we're much closer in!
Youch. Kudos for the extreme transparency, though. That's how you do crowdfunding.
