#studioiv

[lachlanbctsmith]

Laser Cutting Logo

[alyssabct]

[krouxbct]

Skill me Up Scotty...

The name of the game this semester has been Up Skilling. Up Skilling is when you focus on a particular skill in an effort to become better and more experienced in it. This means that the majority of the learning that I have done has been technical modelling skills which have improved greatly over the course of the semester. One thing that is clearly evident of this is the multiple iterations that out main NPC Kevin has gone through.

Kevin went through two rapid prototypes. Initially based off of the Animal Crossing style he came out rather cartoon-ish and not exactly what we were looking for. After receiving feedback and making a few more attempts he ended up in a passable state and stayed that way for a few weeks while other work took priority. However as the semester went on and we made more design decisions around our characters style he started to look very outdated and unfit for the final project. This is why I had another run at making Kevin and settled on this design which the group agreed was a much improved state than what he originally was. I went through a long process of iteration at every step ( this is Version 26 of Kevin) and managed to show a process of learning through experience as well as receiving peer feedback.

The final Kevin (missing eye texure) which is much more inline with our other characters:

[taliabct]

Final Fabrication Reflections

Week 13: 22-26/10/18

The whole fabrication process has been super hectic, stressful and challenging. Here is what I learnt:

1) You got to plan for the unplanned

While I did a pretty thorough construction plan and basic timetable, things still went wrong which ended up eating more time.

Things take time

Before heading into final construction, I had completely forgotten about the prototyping phase for construction. While I had done cardboard mock-ups, I still had to do iterations on how that would translate into the final materials. So, although I had planned to leave a month for final fabrication, the prototyping phase took up about 3 weeks of that. Thus, in the end I was left with about 1 week for final fabrication. At the time, I thought that would be just enough time, now I realise that this was not enough time at all because things took longer than I expected.

On top of that, my design has a lot of complex components and I didn’t fully realise was how long each component would take. Especially regarding the mass production of the blocks. Making a few blocks was a very quick process, however, making about 120 was a very long process. And upon reflection, to save time I could’ve worked a bit smarter. E.g. instead of cutting up all the blocks and then gluing them, I could’ve glued the arcs all together and then cut them up once they had dried.

Thus, in future, I’ve should slightly over-estimate how long each element takes so that I leave sufficient time for each.

Planning a Plan B is important

Before going into construction, I didn’t create a plan B. So, when things got behind, I had to think on the spot about what I should prioritise next. Upon reflection, as a result, I may not have made the most informed decision compared to if I had considered this beforehand. For example, when I was running out of time near the end of the week, I pushed the first coat of stain to Friday afternoon. Now, I realise I should have prioritised the functionality of the design over the aesthetic, and I could have left the staining till Saturday afternoon/Sunday morning.  Had I planned for this earlier, this would have bought me 2 more hours in the 3D lab to really work on the slider mechanism.

Thus next time, I should make a contingency plan of some sort as well as fully prioritise what is necessary to fulfilling the purpose. Which leads onto…..

2) Going back to the purpose.

Amidst the whole process of sorting out the fabrication, it was easy to lose sight of the overall purpose of the project. Thus, it was a matter or prioritising the different agents of necessities i.e. functionality vs. aesthetics. I don’t think I did this particularly well because I was rushed and this was reflected in the overall design of the kinetic table.

Upon reflection, there were some aspects of the design that were more complicated than they needed to be. For example, I could’ve fulfilled my purpose in a much simpler way by just creating a rectangular table. While this wouldn’t have necessarily fulfilled my aesthetic desire, in the end I would have more easily gotten a working prototype that people could interact with.  

This then leads onto….

3) Keep it Simple Stupid

Throughout this process, I had to continually consider how I could simplify the design so that it could still achieve the same outcome but in a more efficient way. From this, I was reminded that the first idea generally is not the best idea and that there are other ways to do it. For example, with the sliders, I realised that I didn’t need to use a dowel to support the slider, but I could instead just double the wooden insert leftover from cutting the base board

4) Two is better than One

So many of my friends were so kind and helped me out with my project where they could. This meant so much and really sped up the process. While I have really enjoyed working by myself this semester regarding the idea development and prototyping phase, for the fabrication, I really struggled to do everything by myself.

Shout out to Olivia, Carol, Andrew, Vaani and Sheena. You guys are the best :)

Overall, this has been a rich (and extremely stressful!) learning experience.

[ultra-oh-carol]

This is my reflection and method that went towards my framing. This is also a photo of the final setup and the video trailer Vaani made.

Method

My contribution to the group involved working on the Augmented Reality research and implementation, as well as the app development and 3D modelling. I used Google’s HelloAR as a base, to further develop and learn AR development in Unity.

https://developers.google.com/ar/develop/unity/tutorials/hello-ar-sample

I used ‘SpeedTutor’ to understand the basics of building the app, including learning to import UI, making the buttons, implemented the AR models and resizing them to fit the screen, as well as scripting the music to run throughout the play mode.

https://youtu.be/FrJogRBSzFo

At first, Vaani and I tried using MapBox SKD for the geolocation aspect of the app, although we didn’t end up using it, we still would have liked it in our app. During the holidays, I looked at many tutorials to follow them, to have a map that in order to have a map that displays the accurate location of the user during the time of use. This was a difficult process and required more time and research, which why we postponed learning this aspect. Instead, we decided to have a still image of the map that highlights the three locations using a 'location pin,' to inform the users to walk to that site.

https://www.mapbox.com/

 Techniques used:

·         Unity: I used this software for the App and AR development/building

·         Fusion360: This was used to create the 3D models for the AR section.

·         S8 prototyping: I’ve used the S8 Samsung phone to a prototype version of the app/AR/Stories.

·         Mapbox: I used the Mapbox SDK for Unity to learn the geolocation part of the app.

Reflection

 Reflection

  This Semester I built an app with the help of my team members.  I utilised Unity as my main tool for building the app and used ARCore to develop the Augmented Reality aspects. ARCore requires the use of a compatible phone which meant I had to purchase one. Using this technology meant our AR had a more interactive quality to it and was easier to use in Unity. This meant I had an easier time learning how to use ARCore.  Unity has a lot of online tutorials, utilising these resources meant I could rapidly prototype in unity to test what could work. We changed from Unreal to Unity which was one of the best decisions we made as a group. We tried using geolocation with Mapbox and while it didn’t end up working it still taught us a lot. We used MapBox to build our static map and postponed using geolocation in this version of the app. If we were to continue building on this app I would implement geolocation.

I used Fusion 360 to build my 3D models. While I was able to create models fast and efficiently I could not export with the fusion textures. This is a fusion problem, but I should have thought about this and tried building these models in blender where I could add UV maps.

My blogging this year was always late as I never knew what to include. I spent a long time trying to write the perfect bogs and this meant I took a much longer time then I should have written them. Next year I hope to keep a constant stream of well-written blogs posted on time so I can follow what I had done. Taking progress notes and images was also something I forget to do and next year I want to try and keep better notes on my self-reflection during prototyping.

This year’s group dynamics could have been better. At the beginning of the project we had good communication within the group and everyone was kept in the loop. After the mid-semester break, everything fell apart. We didn’t communicate so there where miscommunication within and that led to hurt feelings and verbal fights. On the cusp of the biggest fight between group members, we decided to try and solve this with a private meeting where we could sort out everyone’s grievances. While we came to a mutual understanding, feelings were permanently hurt, and the group couldn’t function as well as it once had. I believe that this leads to a halt on the process and meant we didn’t get things done in the way we wanted to. In hindsight, I believe that because of poor communication during the break we stopped behaving as a group. Next time I work in a group I would have to work on my communication skills. While this I liked this project as a whole there are things I could have done differently to achieve maximum productivity.

[vaanibct]

Studio IV - Showcase 2018

The night of the Showcase was very important for Carol, Shades and I, as we wanted to express our project in a positive light. Although we didn’t win any awards for our App, we were still proud to present what we have achieved over the course of one Semester. This would be included in our Portfolio to show the Creative Industry our skills and ideas, and maybe help towards our future job seeking in the creative field.

Some pictures from the Showcase:

Overall, the night went superbly. We had many people taking interest in our Project, and wanting to try the app. I tried my best to “sell” the App and properly explain the conceptual ideas behind our Project, however I think I should have practiced more beforehand. I also realised that the Augmented Reality aspect was much popular amongst little children, while the adults were more interested in the storytelling and map side of the App. In conclusion, I believe that our night was a success because our Project was functioning properly and we had FUN!

Until next year, Vaani OUT 🎤  [hypothetical mic drop]

———————————————————————————————————————————

[synergybct]

We need more posters for our studio wall.

[noraatheexploraa-blog1]

Final

I’ve made a lot of progress and change since my original first idea conceived at the beginning of the semester and the start of Studio IV. I’ve swapped from thinking about aiming to understand the issue of personality clashes, to understanding why technology is important in the developmental stages for kids in combination with tactile and sensory stimulation. I went from trying to create a game of turning blocks displaying faces of a design made up of materials I’ve kept at home as part of my childhood. In theory that practical idea for the installation was great and created a sentimental and personal connection to my project but in the end, it wasn’t time efficient nor did i have enough materials to accomplish the frame on the scale i was planning. So i up-sized the frame and decided to rethink my installation. Who am i trying to attract, who will my project benefit and why? what am i trying to understand and what am i trying to communicate to my audience? In answering these questions, i realized i needed a whole lot of research in order to understand myself, what my project was based around conceptually and how it was built up contextually. 

Looking at it now, I’ve had to relearn processing codes and arduino circuits, I’ve been required to get my hands dirty and do some work in the wood shop to make the frame and mount it on the T-wall. I’ve needed to focus really hard and pull the second last ditch effort due to my unending indecisiveness and forever changing and evolving of concepts and ideas in trying to improve my project and project my message clearer and more interestingly. 

Reflecting on it all, I wish I had changed my physical installation plan earlier in the semester so i wouldn’t have had to push so hard in the last half of the semester as i was limited to the knowledge of what i knew about processing, arduino, wood, installations, and how to portray my message symbolically and easily to receive as a viewer/user. I had a lot to do and with the kind help of many of my BCT peers, i managed to get it done and bring my vision to reality. 

I have to admit, this semester was very stressful and i definitely could have been kinder to myself had i prepared better but in hindsight i had no idea i would have changed my installation plan so late. The one thing i can say confidently is that i was and still am glad i stuck to my original concept. It was something that i found was easy to relate to as it was an issue i’ve faced personally with my younger sister therefore the issue i was trying to understand through my project was close to home.

When talking to Clint earlier this semester i remember him telling me to chose an issue or topic that is close to home and in most ways possible, i’ve tried to put my personal understanding into the whole of the project to make it what it is. 

I’m not sure if this is the last post of the year but it may be if you dont count a post of pictures showing my installation :)

[tomasjgonzalez]

THE REVENGE OF SPACE, IMAGE AND SOUND #15 (03.09.17)

As stated in yesterdays blog, today we met up in order to lock in our installation idea (our ‘How?’). We pretty much spent the whole day trying to run down our installation idea, but heres a rapid overview. Our theme for the interface of our installation was to be playful and evoke nostalgia from the audience. So we started with the Etch-A-Sketch, then Pac-Man and finally decided to use Snake. Our first goal was to make Snake into a collaborative experience, rather than just a versus game where participants try to win against each-other, since that would have no connection to our purpose and meaning. We realised snakes ‘game objective’ is rather easy and the movement is pretty simple; just X & Y movement. We thought ‘why don’t we split X and Y movement to their own corresponding object, therefore the UP, DOWN, LEFT and RIGHT movement are all separated and can therefore be delegated between members. So here’s the process;

So we started thinking in terms of controllers for the installation and we already had a concrete theme, which was for them to be silly and unique. Here’s an excerpt I wrote down in our teams Google Doc.

“Theme (Silly/funny) : make our controls 'silly' , in order for participants to break that wall of seriousness and remove any bad energy;  I re-watched interactive installation video (the one about the balls) quite a bit, and I pictured myself jumping next to a random person, and I realised you need to ditch your self-image because you are going to end up looking funny maybe, but its compulsory, both participants are in on it, and you feel this sort of connection; ‘He’s doing it right....so why shouldn’t I?’, twos a team, or however that saying goes.”

We were struggling for a while trying to get the perfect controls that would map to the collaborative snake game in the most unique and silly manner, also to find the perfect balance of chaos for our controllers, whether they be input devices or movement oriented, they needed to be not too boring but not too chaotic either. As our inspiration ran dry from looking at images on Pinterest, we decided to go for a quick walk at the Arcade at Queen Street. Although we gained no insight from this trip on our walk back we started thinking in terms of using weird objects to control both the X & Y axis. We wanted to use balls for movement, because you wouldn't think balls have any correlation at all with Axis movement; we wanted participants to bounce corresponding balls to corresponding spots on the floor. Although we quickly realised even though this was a fun and silly idea, it was too chaotic and it’s difficulty would have demotivated the audience from engaging or staying to collaborate with others. We finally decided to map floor pads to the movement; although the floor pad layout has nothing to do with Dance Dance Revolution at all. We wanted participants to work together and decide movement roles by allowing them to move around the pads or even holding them, or coming up with other creative ways to play move the snake and ensure their success or doom. The movement roles are exchangeable, active movement is required and it would be a fun way to play snake, as the controllers emphasise teamwork is needed. 

Obviously today we just came up this idea, but hopefully throughout the creation stage we can develop it further. The picture below shows a basic picture of some layouts we have in mind. The white pages are each delegated movement (UP,DOWN,RIGHT,LEFT), again they can be moved to be used in creative ways while playing with other participants.

Tom.G

[sam-hunt-creativetech]

Accessible designs

Studio IV: 7/09/2017

Firstly, I must cover how colourblind may impact a user who is interacting with your project. The most common is red/green color blindness, where sufferers mix up all colors which have red or green as part of the colour.  

Just imagine if this was in an application, say a button:

("Tips for Designing for Colorblind Users | Design Shack", 2017)

In the decisions to creating our styles, I have been referring to a great tool that eightshapes have created which allows you to test for accessibility in accordance to WCAG 2.0 requirements. This tests the contrasts between colours and their choices to determine whether they’re readable or not to those who may suffer from most vision impairments.

This is a living document on our server and I have attached a screenshot to this post to show how it looks. our color choices are strong with the bottom side of the grid being our backing colours and the above all text colours.

Furthermore, I have been playing with stark to quickly see how the design is looking to those who are colourblind to also see outside of the grid whether it’s easy enough to read or not.

I have attached an article in the references which outlines some of the important reasons as to why designing with colourblindness in mind is extremely important and how crucial it is to their experience using your product ("Why all designers need to understand color blindness", 2017). It’s amazing how easy it is to forget about how big of a difference it makes when designing something, I am guilty of this in many projects I do.

References: 

Cat Noone, B. (2017). Stark Plugin for Sketch. Getstark.co. Retrieved 2 August 2017, from http://www.getstark.co/

How to design (in Sketch, Photoshop and Web) for color blind users. (2017). Medium. Retrieved 5 August 2017, from https://medium.com/sketch-app-sources/how-to-design-in-sketch-for-color-blind-users-2b189c0d58fe

Why all designers need to understand color blindness. (2017). 99designs Blog. Retrieved 9 July 2017, from https://99designs.com/blog/tips/designers-need-to-understand-color-blindness/

How to Design for Color Blindness. (2017). Usabilla Blog. Retrieved 6 September 2017, from http://blog.usabilla.com/how-to-design-for-color-blindness/

Tips for Designing for Colorblind Users | Design Shack. (2017). Designshack.net. Retrieved 7 September 2017, from https://designshack.net/articles/accessibility/tips-for-designing-for-colorblind-users/

[kellyroseleecetechnologies]

[STUDIO] - More Testing.

My exploration of materials continued after my first experiments, during which I determined the most effective method for testing out possible fabrics to use (read about this process here). Having a craft/sewing/quilting fanatic for a mother, getting my hands on samples of a range of fabrics wasn’t particularly difficult, and after an afternoon of raiding her impressive collection of fabric, I put together my own collection of a range of fabrics that I could test using the method I’d developed. I started with some basic fabric types - such as a mesh or t-shirt knit - as well as grabbing anything that caught my eye. Most of the fabrics offered an interesting texture that could create a unique experience when my audience touched the sculpture, including scrunched fabrics, other types of lace (nylon blend and cotton) or embroidered fabrics. I looked with my hands during this process, not only considering what the final aesthetic of the piece would be, but also how it might feel to the touch.

I repeated my method across these samples, which concluded in some interesting results. After the first couple of samples, I found that I could pretty easily predict how each sample would behave during the test. I found that some types of fabrics soaked up the glue better than others, resulting in a firmer, stronger end result (and therefore, successful - when considering the structural requirements to produce the piece of work I’m wanting to create), for example. Similar behaviours like these trended across similar fabric types, meaning that I could pretty much touch a sample after a while and accurately predict the final outcome;

Any fabric containing any form of synthetic thread (including elastic and nylon) did not absorb the glue very well and as a result, did not produce a strong outcome. The shape would be held when I removed the sample from the mannequin, but was very easily bent out with minimal force.

Any fabric that was thin and/or mesh-like also did not produce firm outcomes, as there was decreased surface area of the fabric to absorb the glue and maintain the structural integrity of the sample. These were the most difficult fabrics to work with, because they often struggled to stick to the mannequin due to a lack of glue absorption, but were then difficult to remove once the glue was set without ripping. It was pretty easily to conclude that these fabrics would not be strong enough for the piece, which was a shame because these samples of gave the most detailed and beautiful illusion of being draped delicately. 

Any fabric that was thicker, and had a higher ratio of natural fibres (including cotton, linen or viscose) produced the most successful outcomes. The natural fibres soaked up the glue effectively, which when paired that the fact that these thicker fabrics had more fibres to absorb the glue and therefore absorb a higher volume of glue than their thinner counterparts, meaning that the thicker layer of solid glue held the shape of the mannequin effectively and with strength. I did have three different fabrics that performed int his way - the original crochet lace, a thick cotton and and embroidered linen. 

My next step is to begin casting the torsos of my models, and then use my casts to create full-scale samples to determined the most effective material for the final piece.

[lachlanbctsmith]

[alyssabct]

#ctec608 ‐ Final Entry ‐ Alyssa Kerrigan ‐ Project Kē

Orthographic View of Mask - Studio

Foam Mask Model - Studio

Group Documentation Guide - Studio

Photography/Video Brief - Studio

Photogrammetry - Studio

Maya 3D Model - Studio

3D Render of Mask - Studio

Progression of timeline/time management - Studio

Cardboard Mask - Studio

Cardboard Stencil - Studio

Showcase Posters - Studio

Mask Assembly - Studio

Spray-painting - Studio

Milliput - Studio

Editing - Studio

Making of Title Intro - Studio

Satin Padding - Studio

Physical Artefact - Studio

Project Video - Studio

Resources:

[1] Basic Helmet Construction with Worbla | Worbla Thermoplastics. Retrieved October 29, 2020, from https://www.worbla.com/?p=8457

[2] Laser Cutting Worbla – Part 1! | Worbla Thermoplastics. Retrieved October 29, 2020, from https://www.worbla.com/?p=7042

[3] Laser Cutting Worbla – Part 2! | Worbla Thermoplastics. Retrieved October 29, 2020, from https://www.worbla.com/?p=7907

[4] Laser Cutting Worbla: Creating a Digital Template | Worbla . Retrieved October 29, 2020, from https://www.worbla.com/?p=8281

[5] Maskmaking Examples with Worbla | Worbla Thermoplastics. Retrieved October 29, 2020, from https://www.worbla.com/?p=7898

[6] Paint a Faux Marble Finish : 4 Steps (with Pictures) - Instructables. Retrieved October 29, 2020, from https://www.instructables.com/Paint-a-Faux-Marble-Finish/

[7] HOW TO USE MILLIPUT PUTTY - YouTube. Retrieved October 29, 2020, from https://www.youtube.com/watch?v=iWT9mnaUy0M&list=LLi_2So1RoTUaqDKyE3NpQxQ&index=4225

[krouxbct]

Learning Through Failure

One key thing I have learnt this semester is that not everything goes to plan and that is alright, as long as you learn from your mistakes. To put it plain and simple, our instrument, something that I was put in charge of, ended up being not operational for our submission. Instead, we will be having a digital mock-up to display what I was planning to create and we will be using a computer keyboard instead for controls. The reason for our instrument not making it to a working stage was not because of one simple failure, but rather a compounding of mistakes and misjudgements that eventually even lead to the project being unfinished, and some of the bits that were completed were completed to a sub-par level. Being the ones without a set job, Jacob and I were originally put in charge of sorting out the instrument. Unfortunately, Jacob went AWOL after semester break, leaving me to create the instrument by myself, something I had no previous experience with and didn’t feel comfortable doing solo. I voiced these concerns to our Oscar (team manager) and where possible he and Max both lent a hand in attempting to create the instrument. Despite their help, the instrument ended up being of poor quality and in the end was not something I would have been proud to show as part of our submission. This was mostly due to my lack of skill in the required areas (woodworking and electronics) but the straw that broke the camel’s back was a failure to get the components ready on time. One major part of the instrument was that the keys would be 3D printed using the 3D labs over at Art and Design. I printed a test key a while ago so that we had something to test with which was quite successful. The problem arose however when I decided to wait to print the rest of the keys until too late, the 3D labs printing queue was so long due to other students work and would be unlikely to get them done by submission time. My reason for delaying the printing was to make sure that we had a working design first however this backfired. We also tried to outsource the printing however the cost fell outside out budget and would only barely get it finished before submission with no time for testing. In all this series of unfortunate events has taught me a few things, firstly that time management is key, if I had started working on things rather than waiting around a solution could have been found. Secondly, that being thrown for a loop is more common than things going well, and I should be better prepared for things to go wrong. Thirdly, splitting myself up into two vastly different tasks (modelling and instrument creating) is not a very efficient way to work. Lastly, I should be more outspoken when I believe I can’t finish a task. Through my upbringing I have learnt to not make my problems someone else’s and to push through a difficult task. This however was detrimental to my team as I gave them too little warning to effectively help me on creating the instrument. There is no way to spin it the instrument was a failure however there is not much point in dwelling on it as that won’t change the outcome, rather I want to look to future projects with the lessons I have learned. Avoid unnecessary delays, work to the best of my ability and take responsibility for my mistakes.

[taliabct]

Slider, Bumps and Blocks

Week 11: 8-12/10/18

This week, I focused on prototyping and playtesting different elements of the design. The above video is a short summary of the playtesting and prototyping I did this week.

This process was really insightful because I was able to learn and practice different methods of fabrication. It also enabled me to test out my ideas in a physical context and from that, iterate on the designs.

Here were the elements that I tested this week:

The Slider and Bump:

I’m really happy with how the slider and bump mechanism work because the slider moves really smoothly. However, the bump may have to be iterated on further so that it works more smoothly with the blocks.

Slider with Bump:

Slider base cut using bandsaw:

The Blocks

This is the element I had most difficulty with this week, and I am yet to solve it. The design of the blocks and slider mechanism is based off the CAM mechanism whereby the bump is the CAM, and the blocks are the followers. To reduce friction, my initial design used a spherical follower. While the roller follower is more extensively used as it creates the least amount of friction, I decided not to use it due to the number of rollers I’d have to buy/make (approx. 120).

(Reference: https://nptel.ac.in/courses/112103174/module4/lec3/2.html)

I decided to test out this mechanism using the second ring of blocks (2nd largest blocks) because if I can get these ones to work, I know I can get the smaller blocks to work.

Prototype 1 with cardboard sides and rounded dowel 

An alternative knife edge follower made from 16mm dowel:

Prototype 2 made by gluing together blocks of wood, and MDF follower base:

The main problem I encountered was that my blocks were experiencing a lot of lateral motion (tipping side-to-side). E.g, Prototype 3:

After doing a few different prototypes with different follower designs, I think the problem is a combination of:

Friction between follower and bump which is causing the block to be pushed sideways, as well as friction between guides and blocks causing them to get caught on the edge.

Loose guides which aren’t supporting the blocks’ upwards motion well enough. (below: testing different guide heights and structures)

Perhaps too heavy because in contrast to my cardboard prototype which works 80-90% smoothly, these blocks don’t rise and fall easily. Moreover, they may be top-heavy which may contribute to them tipping side-to-side.

Amount of Anchorage – I need to ensure that there is enough block length below the table surface so that this anchors the block as it rises above the surface.

Thus, moving forward, I need to iterate on the design so that it reduces friction, is balanced and has sufficient guide structure.

I am beginning to get quite worried about the amount of time I have left for construction (2 weeks!!!!!!). The last thing I want is to create something that is so finicky that it takes away from the purpose of the project. Hopefully I can get the blocks to work ASAP in conjunction with the slider, because I don’t think I have time to dramatically change the design.

[ultra-oh-carol]

week 11

This is a short one.

During the last week, all three of us have another class due very soon (Synthetic Reality’s). Monday the 15 to be precise so it has been a very unproductive week. On Friday a finalized app was to be done by me, but I had to postpone that till next week Tuesday.

What I did do this week is finish building the two AR models, a court desk and a bar. I’ve done these on fusion as I am most comfortable in this program from previous use.

(Models by ME.)

Shades, as she was behind in time the sound recording and editing while trying to finish it off this week didn’t happen so we will be reviewing and ‘playtesting’ the audio next week. Another thing we want to do next week is test out the UI and what people really want to see when hearing the recording.