{"author_name":"ComicSans","cat":"LD #29","comments":[],"epoch":1398801360,"likes":3,"metadata":{"p_key":"30181","p_author":"ComicSans","p_authorkey":"21220","p_urlkey":"65651","p_title":"Creating Auger with Vixle","p_cat":"LD #29","p_event":"LD29","p_time":"1398801360","p_likes":"3","p_comments":"0","p_status":"UPD5","us_key":"21220","us_name":"ComicSans","us_username":"comicsans","event_start":"1398384000","event_key":"22","event_name":"LD29"},"text":"

Auger, our LD Jam entry<\/a>, was created with an alpha version of Vixle. \u00a0Vixle<\/a>\u00a0is a voxel-based game development engine that we are also building. \u00a0Here’s an excerpt of the full post-mortem<\/a>:<\/p>\n

Vixle\u2019s First LD<\/strong>
\n When Kit and I discussed whether to compete in the most recent LD, we saw various pros and cons. When Vixle is finished, the ease of use and collaboration aspects will make it an ideal platform for both solo and team participants in game jams. Since it\u2019s still far from finished, it wasn\u2019t clear whether we\u2019d really be learning anything from an attempt to use Vixle. The tools in Vixle are either incomplete (voxel and code editors) or non-existent (animation, texture, and particle editors), so we\u2019d have to use external tools to create most of the assets. We also knew that a lot of our time would be invested in improving the Vixle engine, instead of working on the actual game. Despite all this, we knew our Kickstarter push could only benefit from having a working game. We also hoped that building a game end-to-end would be a trial-by-fire that would tell us a lot about the viability of Vixle in general. \u00a0[more<\/a>]<\/p>\n

\"\"<\/p>","time":"April 29th, 2014 2:56 pm","title":"Creating Auger with Vixle"}