William Ruoff | Postmortem

Throughout this whole project I have learned a lot of things but the most important thing that I have learned would be that working for a stakeholder cause some issues sometimes. Through the start of the this project we didn’t know what we were going to be working on since the people we were working with were not finished their work or ideas either. There were changes made to the project that we had to make because our stakeholder had made changes to what they wanted to do. Other than some of that and losing a team member in the middle of the project, working with a stakeholder was mostly a positive experience.

Also I had learned that working with new technology in a way that others have not done before can be troublesome. We had to basically figure out on our own how to pull off certain things we had planned for this project and they all needed to get done before the performance. (Mentioning the performance we also had an earlier due date than most of the other senior project teams so that loomed over us a little too.) In the end we pulled it off though and I think fairly well since the stakeholder was happy with the outcome as well.

On my end I had to do some stuff that I haven’t done in a little bit so it was nice to refresh myself in a part of Unity that I had not got to touch for a while. One new thing I learned was how certain sea animals move. I had to research and teach myself how their muscles work and create animations for various sea life. Examples would be fish and jellyfish. I also was learning about how human hands move so that I could animate the god hands we had in scene.

All in all this was a very satisfying project to work on because it took us out of our comfort zone and made us figure out new ways of working with our technology. Chelsea, our stakeholder, our advisor, and the audience all enjoyed it in the end so this project was a success.

Advertisements

Tristan Timblin Postmortem

For our final week on the SymphonyXR project I am going to summarize what I got out of this project.

Throughout the term I’ve been documenting our progress in video and photography. I also went through my entire process to design, develop, and launch a website. I haven’t previously had much video editing experience, but I definitely enjoyed bringing together all the footage taken each term to create one concise story. Photographing our progress was also valuable to me, since I’ve been doing some photo electives over the year, I’ve definitely improved a lot since the fall. Most closely related to my focus of study delivering a website I controlled at every stage was a useful exercise for me as a web developer.

SymphonyXR_Working_IMG_4038

Michael Howard Week 07

This week I shifted my focus to working on our final presentation on our project. I sat with other group members and went over the video of the event that we have. I also worked on our first draft of the team script for the presentation. I’ll be working on script and presentation outline changes for the rest of the week.

Team PPJ, wk07

This week we worked on our presentation more, but for see a lot changing depending on how we want to show the performance footage. The end presentation should be a pretty broken up mix of dialogue and video explanation. SymphonyXR_Working_IMG_4038

 

Tristan Timblin, PPJ, wk07

We were hoping to get the performance footage in time to edit something this week to show in class, but didn’t get that until Monday, so I was unable to put together a video for this week. While I was waiting for that footage I worked on some content bits, doing a mobile nav for the site, and processing photos I took at the show.

SymphonyXR_Working_IMG_4043

Cyrus Majidy, PPJ, Week 06

We all went to Curtis for the performance. I was merely a spectator, but was there from start to finish for the entire session, almost, all day, left only to go to class, then came back.

The performance was a huge success, even Professor Lloyd and Wagner were very happy. Our tech team was able to get up to 9 hololenses working in the same shared environment. Wagner said that he had never seen this done before, a huge technical milestone.

It was wonderful to watch the performance all day. I deeply enjoyed watching Clara Gerdes play the organ, and talking to Chelsea Komschlies who seemed very pleased with the artwork I had done for this project. It really seems that she flet our work brought her vision to life.

Hours worked: 11

Team PPJ, wk06

Performance week! We’ve been working hard at Curtis the last few weeks on our final push before featuring our final product as part of the overarching presentations at Curtis. The big performance was last Tuesday at which we successfully shared our project firsthand with about 80 people.

Running the event was exhausting as we did the same presentation and discussion with ten separate groups. After it was done the general consensus was to take a short break while we waited for the footage fromCurtis to be delivered.

Here’s some shots from Billy and I:

Joshua Megahan | Week 6

The Presentation

– Performance

On the day of the performance, not only did we have this project running, but we also had it running for up to about 8 back to back user groups, of up to 9 people, using this shared experience. The whole process lasting nearly 8 straight hours. This is at least something to be proud of. I spent much of my time monitoring Hololens feeds of the audience for quality assurance purposes, setting up the devices in between shows, and helping the CCI team in anyway possible, including testing minor tweaks that hoped would help any of the minor functional inconsistencies be noticed in any of the performances.
– Last minute Fixes

Before the show started, I was able to assist in fixing some of the last minute we were having including displaced particle effects, scene timer changes that have objects spawning in at appropriate times, and animated effects of the coral. These things have had to be fixed several times leading up the show, due to the lack of communication when sorting merge conflicts and making rollbacks to the project whenever code was mysteriously broken.
– What we learned

In the show, we seemed to still have functional inconsistency with the object occlusion effects and interactable objects responding to user input. Much of this was likely due to the limited range of progressive scanning for the Hololens, combined with relatively dark lighting conditions. It it should have been foreseeable but we had limited slack in moving the the users around since we had predefined spaces the users were intended to be sitting in, and not enough landmarks in the real world environment to allow us to adjust the user starting position relative to the anchor points. If the CCI team cares to continue making adjustments then we will see about getting these issues fixed. Now that we’ve made it past the performance and have less fear about breaking anything last minute, we can take some time to address some polish and minor functionality issues before the Senior Showcase. There’s lots of things that would greatly benefit the art and visuals like including physics systems for more dynamic floating objects, more intuitive transitions between the elemental scenes, and tweaks to the flocking patterns of the fish and such that coudl really bring things to life a little more. At the very least, we’ll need to adjust for the new environment that we’ll be working in for the Showcase which may have us using multiple stories of the building, requiring new environment maps and object placement at the very least.

Michael Howard Week 06

This week was the performance, so most of my time went towards tasks on that day. I set up some of the equipment during the performance and monitored what was going on remotely. I recorded video that we will be able to use for our final presentation as well.