Archive for the ‘Newsletters’ Category

Newsletter 15: The Final(s) Stretch

Newsletter for project Heidegger Week 15 in PDF Format

This Week

As the semester comes to a close, and all projects move toward their inevitable ends, we at Project Heidegger have concerned ourselves equivalently with the dual tasks of preparing for a series of presentations, and with authoring definitive documentation of our work over the past fourish months. It’s been a surprisingly anticlimactic conclusion to a challenging semester, but such is the manner by which most of life’s episodes resolve: with a whisper.

In Detail

Toward the end of last week, we met to form general strategies for our triumvirate of upcoming presentations: one with Rich Hilleman to discuss our project in relation to the OCCO; one with representatives from EA–including members of Visceral Games and the Origin development team–to discuss how our work might enhance their work; and, lastly, our Finals presentation, designed to measure our achievements by ETC project standards. Our approach for Rich was to make the presentation as conversational, concise, and un-presentation-like as possible, as he’s a man of spontaneous inspiration and pontification, whose thought process is one of insightful nonlinearity — which he demonstrated in spades during our meeting with him. For EA, we have more time to present, as well as a static audience (until the post-presentation Q&A), so we’ve structured the presentation more like a pitch to the company, focused on opportunity, and we’ve gone into far more detail about our process, challenges, and recommendations to Visceral and Origin, should they be interested in continuing what we’ve begun, to whatever degree. Concerning ETC Finals, we’ll explain the various iterations of our project throughout the semester, and explain what was difficult, successful, and what we’ve learned from this venture as an academic pursuit. The process of documentation has been surprisingly daunting (though this reality shouldn’t have been a surprise, given the intricate and unfamiliar-to-us nature of our work). Martin is authoring the Level Design and Playtesting Team documentation, Star and Shaveen are coauthoring the Data Team documentation, and Emmanuel and Anabelle are co-authoring the Origin Team documentation: once these individual reports are complete and assembled into a single, exhaustive tome, our final tasks for the semester will be to deliver our remaining and aforementioned presentations.

Next Week

Polishing and rehearsing our EA and Finals presentations will consume Monday and Tuesday (though we’ll be presenting to EA on Monday afternoon), and Wednesday will bring Finals. Shaveen will leave California on Wednesday night, and Nathan on Thursday, and the rest of Project Heidegger shall disband soon after. As producer of the project and author of these 15 newsletters, I want it to be forever known that I’m hugely proud of the team, what we’ve accomplished, and that I’ll miss them, to the last.

Newslettr 14: A Softs Bulletin

Newsletter for project Heidegger Week 14 in PDF Format

This Week

Soft Opening occurred this week, and our shared time and energy was channeled toward ensuring that our project–as gargantuan and abstract as it is–was easily understandable, and that it showcased well. We were heartened to observe the great amount of interest expressed about our project (we had a booth set up within the vast atrium of EA’s 250 building) from passersby from varied departments. The enthusiasm radiated by our hosts here at EA shall sustain us during our final week and a half here in Redwood Shores.

In Detail

Prior to Softs, Emmanuel–whose service and determination I’d like to honor and immortalize here–spent untold hours bearing the burden of editing our two promotional videos, one being three minutes in length, the other being 30 seconds. He also composed the script, and was able to birth his singular creative vision. Your team thanks you, Emmanuel! Concerning Softs, our initial plan was to construct a makeshift playtesting area, in which two members of the public could play our modified Dead Space 3 level cooperatively, as Martin and Nathan conducted live player type analysis. Unfortunately, due to uncertainty as to whether we’d receive the number of televisions necessary for this setup (we ultimately did), and because we weren’t wholly certain whether visitors would be willing to sit, play, and remove themselves from their work routines for times exceeding twenty minutes (they ultimately weren’t), we settled on a more conservative arrangement. In the end, we had one television equipped to run our level, one television running the playtesting demo reel that we’d created for Halves, one television running a slideshow of data processing methods and results, and one monitor which displayed an interactive version of our Origin module. Truly, the visual bombast of four screens simultaneously exhibiting unique information pertaining to our project was an ocular spectacle unlike any other in the history of ETC SV, and persuasively enticing to observers. We’re proud of what we accomplished over the course of the semester, and what we showed during Softs.

Next Week

Next Friday, we’ll deliver an individual presentation to Rich, summarizing our project and explaining our outcomes. Prior to that, we’ll work on authoring our documentation reports for our mini-teams (Playtesting, Data, and Origin), then standardize their formats and compile them into a single report. On Monday, we’ll also begin creating the spine for our three upcoming presentations — one to Rich, one to Visceral/Origin, and one for ETC Finals — in an effort to complete these obligations as early on as possible.

Newsletter 13: The Osprey of hope

Newsletter for project Heidegger Week 13 in PDF Format

This Week

For Week 13, we continued to push toward realizing our miniteam goals of concluding our playtests and databasing our data, analyzing the data we’ve collected, finalizing our algorithm and running our data through it, and creating a functional Origin module. Though we inched ever-closer to these conclusive milestones this week, along with beginning preparation for Softs, we also ventured to the San Francisco Bay for the traditional, evershifting ETC SV field trip: this year, we sailed.

In Detail

Martin and Nathan, the Playtesting Team, concluded their weekly efforts, and effectively captured data from 36 individual testers–a meaningful number given the time and resource constraints of our project. Our final week of playtesting was successfully executed after realizing that we were unable to collect telemetry data the previous week due to procedural conflicts that were a byproduct of the custom Dead Space 3 level being uploaded to our Xboxes. Around these playtests, Martin proceeded to work on the Playtesting documentation report, and Nathan logged all existing data from these sessions into a comprehensive spreadsheet. All in all, we’re proud of our playtesting accomplishments, and both the quantity and quality of our acquired data. Meanwhile, on the Data Team, Vera continued to record and log quantitative data from our playtest videos so they can be included in Star and Shaveen’s parsing work. On Monday, we met with Zachery Anderson from Analytics for the second time this semester, and though we (particularly Star) had hoped to utilize Mahout, Hadoop, or Apriori to find data patterns and outcomes in an automated manner, Zachery stressed that we should instead use simpler methods to guarantee results. Consequently, Star built his own comparison tables to locate broad correlations amid our data (in addition to further researching the feasibility of the more complex algorithms, and assisting with playtesting), and Shaveen constructed, in C++, a simple, custom, classification algorithm based on observation that will be used to predict player types. On the Origin Team, Anabelle, having completed her most pressing art responsibilities for the module, assisted Vera with tabulating video data results. Emmanuel fully implemented the radar chart into the module–complete with seamless, real-time cell phone control integration–and ensured that the module can be fluidly launched instantly from any computer, rather than solely his own. Regarding sailing, Project Heidegger, in conjunction with our faculty and peers here at ETC SV, had a wonderful and relaxing sailing experience on the leisure vessel known as the “Osprey,” which was helmed by the affable (and not fictitious, in this instance) Captain Kirk. We were fed fresh fruit and vegetables–and later lunch and light desserts–and were served our choice of both alcoholic and non-alcoholic beverages as we basked like over-blubbered seals on the Osprey’s deck, romanced by the trifold pleasures of the sun, breeze, and soporific rocking of the waves. Perhaps reality in the wake of our voyage has been but a shared dream, and we all remain in a states of somnolence upon the bobbing Osprey; perhaps the reality in which this newsletter is being written is the truth.

Next Week

Next week will bring with it Softs, on Wednesday, and all SV teams will gather in the grand atrium of the 250 building here at Electronic Arts Redwood Shores, in which we’ll discuss our projects with whomever shall happen by our booths. We’ll make final preparations for equipment acquisition and the showcasing of our work early in the week. Then, after Softs, we’ll begin work on finalizing our project and prime ourselves for our upcoming, semester-closing presentations.

Newletter 12: Going Full-Bartle

Newsletter for project Heidegger Week 12 in PDF Format

This week

Project Heidegger made continued, steady strides this week in all three of our mini-teams–Playtesting, Data, and Origin–and we’re gearing up to represent our effort at Softs in the most assured manner possible. Although this week saw no major victories or travails, we steadfastly forge ahead, toward our milestones, and we strive to elevate each other from amid these post-Halves/post-GDC gulleys of exhaustion. Thus far, we are succeeding!

In Detail

We conducted two more lucrative rounds of playtesting this week, and Martin and Nathan have settled into using our custom Dead Space 3 level and Army of Two: The Devil’s Cartel as bases from which to draw their subject player analyses. Further, the inclusion of the online Bartle Types survey at the close of each session has lent invaluable–and almost uniformly affirming–perspective on the veracity of their observational data. Amusingly, Jiyoung volunteered to participate as a playtester this week, and her animated posture when playing, coupled with her shrieks of terror when confronted by necromorphs, should provide extraordinary mirth to whomever on our team processes the video of her session. And surprisingly, given Jiyoung’s purported inexperience, she was able to coordinate and strategize successfully enough with her partner to so very nearly clear the most vicious of our level’s choke points. Bravo, Jiyoung! Additionally, Martin authored a comprehensive summary of our playtesting findings to this point for submission to Ben. On the Data front, Vera has been working to composite the three simultaneously recorded camera feeds (front, side, and gameplay capture) of each of our playtesting subjects into a single, frame, and then manually tabulate the significant metrics from each session that Martin and Nathan are unable to in real time when administering the playtests; Shaveen and Vera have also been assisting with this task, and we aim to have 12 fully processed videos completed by Monday of next week. Shaveen has further been refining the database and parser scripts he created last week so that they can be used harmoniously with the algorithms to which Star has devoted his time. Though Star had previously been solely investigating the usefulness of Hadoop and Mahout, their complexity has turned him toward Apriori, an Eclipse-based frequent item set mining algorithm. We’ve been attempting to run a sample batch of processed data through one algorithm for the past couple of weeks, but the elaborate nature of these algorithms–which Star has never before used but has,most impressively, learned solely for the sake of this project–has prevented us from doing so: next week, however, we are on target for conducting this test. In working as a liaison for the Data Team, Emmanuel installed both Hadoop and Mahout on a computer that will be utilized singularly for algorithm exploration, as we intend to use one or both of these libraries in conjunction with Apriori; previously, Star had to reboot his computer and run Unix when experimenting with Hadoop or Mahout, and Emmanuel’s logistical contribution here will streamline Star’s process. Further, Emmanuel, for his Origin Team responsibilities, finished designing the radar chart for use in our module, and set up the web server which will allow that chart to be updated dynamically. Anabelle, in addition to assisting Vera wtih video processing, worked with Ben to secure a final graphical design for the aforementioned radar chart.

Next Week

Next Monday, we’ll consult again with Zachery Anderson, who we met with very early in the semester, so the Data Team can receive feedback on their pipeline and the type of data that we’ve been collecting. As mentioned, we’ll also be running a preliminary batch of data through one algorithm to test outcome results. Emmanuel, Shaveen, and Anabelle will also be working together to create team promotional videos in preparation for our Soft Opening, which is the week after next.

Newsletter 11: System Shock 2

Newsletter for project Heidegger Week 11 in PDF Format

Week Overview

This was a week of relative quiet for the project, a useful respite after the pressure of Halves and the successive blitzkrieg of networking and education that was GDC. Though convalescent, this week saw us make substantial progress in all departments toward our ultimate goal.

Anabelle, cagily working on a radar chart.

In Detail

On the playtesting front, Blade was able to upload the custom Dead Space 3 level he’d built for us into the development Xbox 360s we’re using to collect telemetry data from during our testing sessions. Martin and Nathan were able, at last, to play through and evaluate the level, and we’ve implemented it into our playtesting routine for this week’s round. It affords us a much wider range of in-level “beats,” or points from which we can reliably gather information pertinent toward making Bartle Type predictions, than the release level with which we’ve been testing, as well as the opportunity to collect deeper telemetry data. Beginning this week, we’ve also incorporated the retail version of Army of Two: The Devil’s Cartel (the third game in the series) into playtesting, as it is now commercially available; to this point, we’ve been using Army of Two: The 30th Day (the second game). We’ve also modified our end-of-session survey process: we’ve included an interactive Bartle Type survey that players take so as to help verify Martin and Nathan’s subjective predictions, and, based on Star’s recommendation, a questionnaire concerning genres of games that testers enjoy most, which will aid us in making more complex recommendations to them via our Origin module that will hopefully exceed simply whether or not they’ll enjoy Army of Two as deduced from how they played Dead Space 3. The Data Team was also busy this week. Shaveen devoted his time and energy toward creating scripts in SQL and PHP to, respectively, store the telemetry data the we’re gathering from our Dead Space 3 tests, and then parse the data so that it can be easily collected and exported in a convenient format for the algorithm that Star is in the process of finalizing. Additionally, Star, Shaveen, and Vera met several times during the week (and once with Ben) to solidify the metrics to be gathered by Vera from the video captures of our playtesting sessions–a process that she’s begun this week. The Origin Team has continued their work on beautifying and expanding the functionality of our module. Anabelle created mockups of the radar chart which will be used to visualize for players their specific type, and is polishing them so that Emmanuel can then implement this feature. And Emmanuel came to the important realization that, given the time constraints of our project, it will be impossible to replicate all the cosmetic elements of actual Origin in our module (such as the ability to drag the sidebar). Concerning the aforementioned radar chart, Emmanuel’s been experimenting with the Tornado Web Server, the utilization of which will allow us to change the values of the charts in real time, and with little effort.

Next Week

In the week ahead, we plan to, of course, continue playtesting, parsing data, and refining the Origin module, but, perhaps most excitingly, we hope to run an initial batch of data through Star’s algorithm by Wednesday. Needless to say, we are eager to behold the results.

Newsletter 10: GDC 2013

Newsletter for project Heidegger Week 10 in PDF Format

Week Overview

This week was the 2013 Game Developers Conference in San Francisco, and all members of Project Heidegger were in attendance. Due to the madcap pace of the conference, and because it necessitated that most of us be away from the OCCO for the majority of the week, progress on our project all but halted, as it did for all other ETC project teams. Regardless, we each attended panels and discussions which proved inspirational for either our goals on the project, or our careers (and, in some cases, both).

Hideo Kojima, father of Metal Gear, as captured by Shaveen

In Detail

Martin saw Jason VandenBerghe from Ubisoft deliver a talk about his highly specified player type research, which is similar to the focus of our project, and which validated our direction. As a result of this talk, Martin suggested that we incorporate a 30-question Bartle Type survey into our playtesting process, so as to better support the subjective predictions we’re making about each player. Concerning videogame storytelling, Anabelle was impressed by much of what she saw during the Narrative Summit in its GDC San Francisco debut, but was perhaps most moved by Japanese developer Kotaro Uchikoshi’s discussion about Virtue’s Last Reward, a visual novel available on the PlayStation Vita and Nintendo 3DS. Uchikoshi’s concept that game narratives should be driven by discomfort stuck with Anabelle, who is currently creating a visual novel game for her independent study. Further, she thought Uchikoshi adorable (as did Nathan, who was also present). Jenova Chen’s lecture about the design of Journey (which won six Game Developers Choice Awards this year) made Star more conscious of the emotional capacity of videogames as an art form, and made him consider the potential of genres beyond the standard fare of FPS, RTS, MMO, MOBA, and so forth. The GDC Awards were the most memorable conference event for Shaveen, who was charmed by the hosting prowess of Tim Schafer, and who was vitalized by the enthusiasm and passion displayed by the winning developers during their acceptance speeches. Emmanuel was fascinated by a talk delivered by Luke Muscat, CCO of Halfbrick, who found that a new game he was prototyping caused his friends to conspire against each other in reality. For Emmanuel, this was an illustration of how powerful games can be, and that game design comes with some responsibilities. Vera received most from the Career Expo, and was able to gather much useful information about Kojima Productions–one of her dream companies–in both Tokyo and Los Angeles. Last, Nathan found the three Japanese developer talks, about Tokyo Jungle, Dragon’s Dogma, and Virtue’s Last Reward, respectively, to be refreshingly antithetical in both tone and intent to those delivered by Western developers, and restored his hope that humility and creativity can co-exist within the industry.

Next Week

Looking ahead, we plan implement both our custom Dead Space 3 level and Army of Two: The Devil’s Cartel into our playtesting process next week. Our Data Team will be preparing to run our first batch of data through our algorithm, and our Origin Team is making visual refinements to the module as well as expanding its functionality.

Newsletter 9: Halves

Newsletter for project Heidegger Week 9 in PDF Format

Week Overview

This week was defined and singularly devoted to preparation for our Halves presentation, which was unexpectedly rescheduled from Wednesday the 20th to Friday the 22nd due to the resignation of EA’s CEO and the abundance of company-wide meetings that followed. (Incidentally, how very surreal that we were present and working on the executive floor for this episode of corporate politics!) Thankfully, we were able to optimize our presentation with the additional days, and we succeeded in concentrating the complexities of our project into an audience-friendly and approachable review of our progress thus far.

Heidegger half presentation

In Detail

Since last week was our Spring Break, and because no newsletter was produced, it’s first important to note that we conducted one round of playtesting then, and also began the assembly of our Halves presentation. Although we’d created a rough PowerPoint outline during Spring Break, we decided to each create our presentation slides individually for Halves, due to the fact that Shaveen, our resident PowerPoint god (and the party responsible for executing our Quarters slides so splendidly), was attending a conference for most of this week and therefore unavailable. On Monday, the tactical error of this choice was made evident, as it proved difficult to achieve the aesthetic cohesion of our past presentation and realize the quality standard we hoped to meet. Thankfully, Jiyoung and Carl provided us with their reliably useful feedback on Monday, Tuesday, and Wednesday during our team rehearsals with them, and on Thursday–at last–we triumphantly attained visual fluidity. Because the road to that point was arduous, the accomplishment of this rather mundane goal became meaningful. In addition to our PowerPoint presentation, we also created supplementary materials to be displayed at an exhibition table following Halves. Martin and Vera edited a “highlight” reel of a few of our playtesting sessions so that attendees could receive a concrete idea of our process and findings, Star made a posterboard display of our level design and our data collection process, and Emmanuel and Anabelle built an interactive demo of our Origin module. Though attendance at our Halves presentation was impacted by its rescheduling, the audience was still healthy, and we were pleased that a fair number of familiar faces from the OCCO generously took time out of their day to support us: if any of you read this, your encouragement was tremendously appreciated, and we thank you! Concerning the organization of our presentation, Nathan introduced the team and to the project; Martin explained our playtesting process; Star and Vera covered our data progress; Anabelle detailed the development of our Origin module; and Emmanuel discussed our challenges, metrics of success, and milestones. Shaveen also rejoined us, and we were thankful for his presence once more. The delivery of our presentation was catastrophe-free, and we received questions from the audience about the possible future implementation of our process, and about our current usage of Origin. Following Halves, Ben approached and congratulated us on our performance: this was, undoubtedly, the highlight of the day, and the week.

Next Week

Shortly before the composition of this newsletter, we received word from Blade that his initial implementation of our custom level is complete: this is exciting, indeed! Though next week is GDC, and the majority of our Heidegger work will halt due to our commitments there, we’ll be incorporating our fresh custom level into all further playtests.

Newsletter 8: Crysis

Newsletter for project Heidegger Week 8 in PDF Format

This Week

We expected Week 8 to be a productive-yet-uneventful, but, because every week holds surprises (that truth is indeed the dominant constant of ETC life!), the fact that some shifts in the direction of our project unexpectedly manifested was not altogether startling. Regardless, we pressed on within our mini-teams and continued to progress toward our persistent goal of establishing a fixed and efficient system of data collection and processing.

Heidegger Halves presentation conceptualization

In Detail

This week’s most significant news was that, on Tuesday, Ben informed us that the role of the custom Dead Space 3 level we’ve been planning on using as the basis of our user testing once Blade implemented our designs will likely be significantly diminished. Instead of using it as a focus of our testing, Ben suggests that we should test the majority of our users with existing Dead Space 3 levels, then have some testers in later sessions play our level, additionally. The rationale behind this thought is that Visceral Games, Dead Space 3’s developer, will be able to use our findings more practically if they stem from the release version of their product rather than a level specific and limited to our experimental effort. Our level might still prove useful to them, however, as we’ll now have the opportunity to share with members of their studio how testers respond to the segments of it designed to stimulate specific player type. Perhaps said information will prove enlightening, and perhaps not, but Ben’s other divulgence was that we’ll now be presenting the fruits of our research to Visceral Games at the end of the semester. We’re all thrilled at the opportunity, and sincerely hope that our work can positively influence future development there in even some modest way! The team’s still discussing and processing the implications of this recent information on our Halves presentation and the project entire, but we’re confident that Ben will assist and guide us to the best of his ability. Concerning more planned-for tasks, our Level and User Testing team executed their first official round of tests this week, and utilized a mixture of players from the public, fellow CMU ETC students, and EA employees. The results, as always, were compelling and revealing, and Martin and Nathan continue to refine the process of data-gathering. On the Data Team, meanwhile, Star sustained his exploration into correlation algorithms, and, with Emmanuel’s help, installed Mahout, Hadoop, and Unix. Shaveen and Vera further collaborated on database construction and refinement, while, respectively, Shaveen sought to better understand how to generate and gather Xbox 360 telemetry data and Vera began editing and processing the behavioral data videos gathered during user testing. Finally, Anabelle and Emmanuel, the Origin Team, presented their lovely and thoughtful recommendation system concepts to the rest of the full team, and to Ben. Individually, Anabelle’s been ensuring the graphical fidelity of our mock-up and its cohesion with Origin’s branding standards, while Emmanuel’s been building the functional HTML core atop which the graphics will be grafted.

Next Week

Though next week is technically Spring Break, we plan to conduct Round 2 of our user tests and make as much headway as possible on both Data and Origin fronts. The week after next is (already!) Halves, and we plan to incrementally build and polish our presentation so that we can begin rehearsals.

Newsletter 7: Mass Effect

Newsletter for project Heidegger Week 7 in PDF format

Week Overview

This week marked our final push of preparation before we ease (hopefully!) into our routine of data collection, data processing, and Origin module construction. Noteworthy events were our second round of individual meetings with Jiyoung and Carl, our dear Silicon Valley faculty, and our first user testing session involving the majority of our equipment and living, breathing, human participants.

A rare moment of cross-team discourse.

In Detail

We were fortunate enough this week to have had more consistently unbroken time than in recent weeks to devote to our project, and we utilized it by pursuing the goals of our mini-teams. Martin and Nathan, the Level Design and User Testing Team, worked to clear the debris from and untangle the kudzu of wires in the RAM Room (it’s named after a specific testing methodology, according to Ben — though, mysteriously, he couldn’t name it), where our tests will take place. Fixing the prohibitive technical issues of the room, such as our inability to establish a network connection and the fact that one of the two necessary TVs in room didn’t function and had to be replaced, took many an hour and much coordination with Ben, who is infinitely patient and responsive to our travails. On Friday, six of our ETC Silicon Valley peers were gracious enough with their time to participate in our final phase of preliminary testing. We were able to not only smooth out the final impediments in our testing procedure and equipment calibration, but we also succeeded in collecting our first batch of analyzable data—a major milestone! The Data Team, meanwhile was equally busy: Shaveen was able, at long last (and after much conversation with various EA tech-contacts), to directly interface Xbox telemetry data from his PC, a significant accomplishment that will allow us to pull recorded data from the development-model Xboxes hosting Dead Space 3 for our user tests. Shaveen and Vera collaborating on the creation of SQL forms and databases for the cataloging and storage of collected data, and Star spent the week researching primary and secondary algorithms we can use in coming weeks for the critical step of data correlation. Regarding our Origin module, Anabelle and Emmanuel conferred on Monday and decided on three exploratory recommendation concepts, which they’ll further develop and share with the full team next week. Additionally, Emmanuel has, using the Origin branding conventions as a touchstone, been painstakingly creating an interactive facsimile of the browser-based Origin service. This way, our recommendation system, once finalized, can be implemented into this mock-up and evaluated by our client in a virtual setting both pertinent and meaningful.

Next Week

Looking ahead, next week will bring our first official round of user testing, the establishment of our data pipeline, and further progress in the development of our recommendation system. After a lengthy gestation period, it’s stirring to witness our mini-teams thrive and the actualization of our long-held plans!

Newsletter 6: SimTeam

Newsletter for Project Heidegger Week 6 in PDF format

This week

Though this week was abbreviated due to the Presidents’ Day, we made substantial progress in our triumvirate of project goals, particularly from an organizational perspective. We set into motion a team restructuring last week, following Quarters, and this week saw the realization of our plans. We decided to divide our team into three mini-teams for the remainder of the semester: Martin, Vera, and Nathan will focus on Level Design & Iteration and User Testing, Star and Shaveen (with Vera assisting) will devote their energies toward Data Collection & Sorting, and Anabelle and Emmanuel will work on designing and implementing our Origin recommendation module.

Blade and Nathan fervently discuss necromorphs.

In Detail

On Monday, in an OCCO office darkened for holiday power- saving reasons and which resembled the desolate and abandoned interiors of a Dead Space starship, Martin, Emmanuel, and Nathan further specified and detailed a “beat-sheet,” or written description of important events, for our Dead Sspace 3 level. This effort bore fruit on Wednesday, when we met with (an unfortunately ill though thankfully patient) Blade. We guided him through the intended path of our level, along the way discussing each modification to his existing level we hoped he could implement, and offering our justification for certain changes with explanations of the metrics we wish to gather from them. Although he wasn’t certain that he could realize all of our level-revisions, he thought that implementing the bulk of what we’d requested would take roughly 10 days, which aligns well with our milestones; he also appeared relieved that we didn’t want him to build anything into the new level from scratch, as such a process would have been very time-consuming for him, and the architectural additions would have also lacked textures, marring the presentation-quality of our level for our testers. Then, on Friday, the team assembled to perform a mock-user test, wherein we set up the various recording equipment we’ll be using in the coming weeks, ran through a few play sessions, and acclimated ourselves to the testing process. This trial was restricted to our team (as well as Ben, who guided our tryout), as we didn’t want to waste the time of any potential testers with the bumbling of inexperienced practitioners. We are now, however, confident in beginning user testing in earnest next week. During this timeframe, Star, Shaveen, and Vera collaborated on research for a data management system, and Shaveen created a preliminary spreadsheet for amassing data from Dead Space 3 YouTube and Twitch.tv playthroughs (as a supplement to our live tests). Meanwhile, Emmanuel and Anabelle busied themselves with refining our project website and researching biometric recording equipment, respectively, and made preparations to embark upon Origin module recommendation-system design discussions next week.

Next Week

We generated a tremendous amount of momentum this week, and though certain elements of the project remain beyond our control — such as when Blade can deliver his first implementation of our level — we’ve now the agency and structure to proceed regardless of external factors. The next week will see the finalization of our testing metrics, our first true user test, and the development of several Origin recommendation concepts: it should, in fact, prove our most gainful week thus far.

Older Entries