Research Record and Conclusion - webpage

 Stage 1 - Backwards Planning. 

The first stage of the 703 unit was to plan, I completed a backwards planning document, where I thought about what the end goals for the project were and where I would like to be 2 months after the end of the MA program. This was a different method than I would usually use when planning as I usually work forwards. The backwards planning method worked much better for me as I was able to see what I want to have achieved and then plan accordingly to get the project done on time. It was also at this stage that I realised my project idea was still overly ambitious. This was a good stage to find this out as opposed to much further along with the project like what happened in 701. 

Backwards planning helped me to identify the different outcomes that I wanted, I then broke each of these down individually into tasks that I would have to complete, I used these tasks to identify skills that I need to learn, the software I need and all other small tasks that I need to complete. 

This task was one of the most helpful that I have done and backward planning is a method that I will continue to use going forwards whenever I start a new unit or project as it allowed me to see right at the start that the project was too ambitious and then adjust my plan accordingly.  

A full breakdown of this can be found at: https://emma-ma-animation.blogspot.com/2022/10/backwards-planning-to-start-703-unit-i.html

Stage 2 - Project presentation 

As part of the 703 unit I presented my project Idea to the new group of full-time MA animation students. Completing this task was helpful to do so early as it allowed me to clearly define my idea. Making the presentation about my project for a group of people who had no idea what I was doing, really helped me refine all the ideas and context of the project until it was clear and understandable. Not only was I able to articulate my idea to the group but it also helped me get the project clearer in my own head. I was able to briefly explain what my project was, the context behind it, the aims of the project, the testing and learning stages along with the software that I had identified, the methodologies, and the final goals of the project. I was also able to demonstrate where the theories from my dissertation linked to the practice tests that I would complete and how I would use the tests to prove the theory that I had outlined in it.  

This presentation can be seen on the 703 project overview page

Stage 3 - refining

The third stage of the 703 unit involved me further refining the tasks that I had identified in stage 1. Here I first looked at software, I had a very very large list of different software that I had identified could be used in the production pipeline, I took some time at the start of the 703 unit to refine these down into software that I knew already, the software I only need to upskill with, software that I had access to (to keep costs down) and software that fulfilled multiple requirements (e.g Maya can be used for modelling and animation as opposed to one that can only be used to model like 3DsMax) This research allowed me to collect a collated list of software that I would use in the testing. From this research I also identified the specific skills that I need to learn in each software, this allowed me to create a breakdown of skills that I need to learn, meaning that I would be able to concentrate on the skills that I need rather than trying to learn everything in 6 new software. 

I also broke down tasks that I had to complete as part of improving my professional network, I broke this down into small manageable jobs (such as getting a new logo) this break down of tasks works for me as they are more manageable, and this stops me becoming overwhelmed by the size of tasks which then leads me to panic and procrastinate.  

I then started researching methodologies that I would use to conduct research and testing. I also outlined the negotiated project work that I would submit for the 703 unit (this is due to the nature of my project not fitting the standard unit format) I finally started to plan my ideas for the tests that I would conduct in 703 and made a more detailed planning document where I outlined the work I needed to do each week of the unit. This all helped me stay on track, and made sure that I did not become overwhelmed as I had done in previous units.  

More details about these stages can be found at: https://emma-ma-animation.blogspot.com/

Stage 4 - interim presentation

In stage 4 I completed an interim presentation which was again shown to the new full-time MA animation students, this presentation outlined the work that I had been doing on the project in the weeks prior, the progression and changes I had made, the intended outcomes for 703, as well as my next steps. This presentation again helped me to clearly articulate my idea. From doing the presentations in this unit, I have found that if I create a presentation for an audience (with the idea in mind that they know nothing about the project or theories behind it) that not only does it help me present the ideas to an audience clearly but it also helps me to keep the project straight in my head. I think this is another method that I will use going forwards as helps me keep on track and stop the project (me) from going off on a massive tangent. 

This presentation can be found at: Interim crit

Stage 5 - research framework 

Stage 5 of the 703 unit was where I started to create my research framework. In this stage I re-read my dissertation and highlighted important points, I then collected all these points and separated them into categories, once I had done this I identified the points that I would look at in the testing stages. To make these theories and tests clearer and show where they linked I created documents that listed the tests I would do, the research method I would use to conduct them, whether they tested pipeline, theory or both and if they tested theory which ones they were. 

This stage helped me make sure that all the theories, tests and how they linked were clear, this made sure that going into the tests I clearly knew what I was looking to achieve, and the outcomes that I wanted to collect. Again another useful task was to make sure that at each stage of the unit I had a clear idea of why I was doing something, the context behind it, the research methods that informed it, the outcomes I was looking to collect, ensuring everything was linked and working in synergy. Once again making sure that everything was clear before I moved to the next stages made sure that I did not become overwhelmed in the unit. 

More details about the research framework can be found at: https://emma-ma-animation.blogspot.com/

Stage 6 - testing

Stage 6 of the project was to start the practical testing. This was the stage of the MA that I have enjoyed the most so far, finally being able to try something new and learn new practical skills was the reason I started the MA, so finally starting this was great, it gave me a real boost and I feel more confident in the project as well as in my own ability to complete it than I did before the testing. 

For the testing in 703, I concentrated on learning how to do photogrammetry scans and turn them into 3D models. This meant buying and learning new software as well as different techniques. The tests that I have done have mostly been focused on a dice tower diorama that I made, as well as a test with a doll (in place of a puppet). I have had different levels of success with these tests with some failing completely and others working out quite well with only a few issues (such as shiny surfaces) The tests have allowed me to learn new skills and they have also helped inform the project further. It was through completing the photogrammetry tests that I decided on the outcome for the 705 unit, as well as the further testing that I will continue. 

In the testing I found that the doll (puppet) was the scan I had the most issues with and was also the element that would be the steepest learning curve for the whole project as it will involve: materials testing, making/building, scanning, meshing, rigging, animating and compositing. This stage requires numerous tests and skills to learn as well as the most software to learn. When I found how hard it was to just capture the doll at a good quality, it made me doubt if I would be able to achieve any finished outcome investigating just this area. When I compared this to the tests with the dice tower I had been able to get considerably better results, this lead to my decision for the practical outcome I want to achieve in 705, which is to create a stop motion environment/set as a modular build, each of these will then be captured using photogrammetry, they will be re-meshed, have UV's added and then used to create a 3D digital version of the set. This will be placed in VR and will be presented alongside the physical model at the end of the unit. 

This change means that I can test my theories, learn and refine my skills and pipeline, have a finished outcome at the end of the MA and either conduct the tests with the puppets alongside or propose to conduct these tests in a PhD, in order to advance the project.  This will also enable me to get a better result as the more complex tests will be built on a stronger foundation of skills and knowledge that will have been created through the proposed practical outcome of 705. 

Coming out of the testing phase of 703, I definitely feel more confident about the future of the project and I feel much more ready to dive in and continue testing, and learning software and skills. The testing in this unit has been really helpful in boosting my confidence with the whole project as well as helping me learn new skills. 

More details about the testing stages can be found at: https://emma-ma-animation.blogspot.com/  and Portfolio of tests

Stage 7 - project proposal and next steps 

The final stage of the 703 unit was to create the final outcomes for submission. For submission I had to hand in 3 pieces of work, the proposed work has changed slightly since the start of the unit but is still not too far from the original proposal. The pieces of work to hand in are:

1. Practice-based Research Portfolio - No Change - This will be a copy of my blog as a PDF along with this web page which acts as a way to consolidate all the research into a single clear and reflective document. It will also include a PDF of the presentations given in this unit. 

2. Pitch Bible - Changed - Originally this was proposed to be the methodologies chapter for my PhD proposal, however as I was researching and writing this document it felt too early in the project to fully define this, especially as I had only just started the testing. Instead, this will now be a project proposal document which will outline the project, its goals, the research questions, aims and methods, the skill development, as well as where I intend to be/ produce in the 705 unit going forwards. 

3. Animatic - No Change - This will be a portfolio of the practical tests that have been conducted in this unit along with a  written reflection on the tests, what I have learnt and what I have achieved in 703. This will evaluate and critically analyse the tests and the outcomes as well as my learning and how it has informed my new theories, and practical experiments going forwards. 

These documents can all be found here:

Practice-based Research Portfolio: https://emma-ma-animation.blogspot.com/

Pitch Bible: Project Proposal

Animatic: Portfolio of Tests

Conclusion - 

Overall this unit has gone very well and I am very happy with the outcomes from it, I have learnt that not all my work need to be perfect straight away and that if I can relax and forget about being perfect then the results I achieve are actually better (and more enjoyable) and it means that I am less stressed, which in turn stops me panicking and then procrastinating, meaning I get more done.  

I have learnt different skills that help me with this such as, backwards planning and refining down further into small, clear and manageable tasks, works well for me as it stops me from panicking by the size of the task and stops my mind from racing about everything it evolves as it is already listed out. 

I also found that if I create clear and refined documents that I have made with the thought of presenting them to an audience, who has no idea about the project, then I am able to collate all the work I have completed in that stage in a way that is clear, concise and organised. This means I have all my ideas and next steps clearly outlined, which not only makes my work clearer to others but also makes it clearer for me. For example, having the project proposal document at the end of 703 will enable me to enter the 705 unit prepared and with a clear set of goals and intentions as well as have a plan of the work that needs to be completed in place. Having this at the start of the unit means I know what I need to do first and will be used to help me make a detailed schedule of tasks that need completing each week meaning I know mostly what to expect and can manage my time more efficiently. 

In 703 I have also learnt that tests won't always work out, but that doesn't mean that they are a complete failure, of all the tests that I have conducted in this unit it is the tests that went wrong that I have learnt the most from and that have really helped me to refine my skills going forwards. Without the tests failing I would not have learnt as much as I have about photogrammetry nor would I have learnt how I can fix it when things do inevitably go wrong. 

I feel like 703 is the unit that I have grown the most in, I have learnt many ways to work better both in terms of production and skills development, but also ways to work with things like my ADHD and dyslexia, which can be incredibly challenging at the time, I feel like these skills will benefit me immensely as I progress, as while this unit has been challenging it is the unit I have felt the calmest and the clearest in because I have employed the methods listed above, and they are all things that I will continue to use going forwards.

Test Progress

 Test 1 - WORKED BUT NOT USEFUL - 360 camera test - Capturing the dice tower diorama using a 360 camera and putting the resulting footage into after effects to learn the VR composition tools. This test worked but after looking at it, it is not suitable to be used in the production pipeline for my project. This is because it is for 2D/2.5D rather than 3D. The footage captured could be used to create a space in VR but it would not be explorable or interactive as I want. This way of collecting the footage and set means that it creates a 2D 360 video which in after effect I could add text, and objects that I could move along the axis as though they were in 3D space, how ever as they are not fully 3D it meant that viewers would not be able to look round them. This method of production would be good to use if the production I was aiming for was similar to “Mad God” however as I am trying to create something that can be interacted with I need the objects in it to be fully 3D. This test has shown that in my production pipeline I need to look at software and methods that are more focused on game play such as unreal engine. 

Test 2 - FAILED - 3D scan using the 3D scan camera on my Wacom mobile studio - the Artec software would not load on the Wacom, I tried to install Artec 17 and activate a trial, but unfortunately, it would not recognise the scanner. I tried to re-calibrate the intel re-sense camera using its own software this also would not work, when I googled this issue there were only a few results and it seems there is an issue with intel update that stops it from working. I tried to fix this for well over an hour with no success, it was at this time that I decided that my time would be better spent by continuing to test using the photogrammetry software that I have so that I can get results. When I have more time at a later date I may try to get this scanner and software fixed but at the moment I do not have the time in this unit to argue with it. 

Test 3.1 - WORKED - photogrammetry test, Capturing the dice tower diorama, worked well, it picked up details of the tower, but it didn't pick up some of the bits of smaller figures that were hard to get into with the camera. 

• Continue testing with other objects and items 

• Make another diorama or object that can be used to test materials but that doesn't have as many surfaces as the dice tower. Make this a modular item that can be scanned and built-in 3D eventually, and try and build a small scene similar to what my finished idea is (a fantasy-themed environment) This could be built at a small scale and scaled up in 3D, I could use this to create a 3D environment in VR that people could go into, the presentation of this could have the diorama displayed and then allow people into it via VR.

• The scene could make it so that participants can enter one of the buildings, if I test this in the unreal engine VR system I should be able to make it so that people can interact with the door and some objects in the scene. 

Test 3.2 - FAILED - Photogrammetry test with a doll, capturing a monster high doll using a photogrammetry scan, the resulting footage will be put into Maya and rigged, it will then be used to conduct a test animation. 

This test failed, the scan didn't pick up the details and led to a really bumpy result, I believe this was due to the doll I used having glittery skin. I did however learn a few points that I need to change when I next try this. These are: use a different doll, take photos closer, and use a ND filter on my lens. I will try this test again and I will use all the things above that I have mentioned. 

I also need to email Mat and ask what methods he used to capture the wind in the willows puppets as this may be a different method that I can use in my work. 

Test 4 - MOVED TO NEXT UNIT -  practical materials test board or test box - shortcomings of photogrammetry with reflective and high specularity (a highlight from lights) surfaces

Practical test reflection

Through these practical tests I have learnt a lot, they have enabled me to upskill and learn new software as well as develop how I approach completing my work. 

Through these tests I have learnt how to use Agisoft Metashape, a photogrammetry software, I have also learnt about how to take photos for this and get the best results. I still need to improve the photos that I get and invest in a ND filter for my camera to stop the issues that I am having with reflective surfaces. But when I take into account the scale of the objects that I have been capturing I am very happy with the results that I have achieved. As part of these tests, I have also started to investigate how to decimate meshes of objects I create and have started to look at how to put the scans into Maya, as I progress with this the next stages of this testing are learning how to edit, create and re-mesh the scans I have and then how to create UVs for my models. 

I have also been able to further refine the list of software that I need to learn and that I will use in my pipeline, which has helped make the project more manageable. As well as this I have learnt various strategies that help my workflow as well as my stress levels. I have found that using backward planning, and refining down from this into small tasks stops me from panicking over the amount of work. That creating clear and concise documents to present to an outside audience, which summarise the project so far, helps to keep the project clearer for me and If I stop worrying about perfectionism then all my workflows smoother with much less stress. 

The practical experiments from this unit have been informed by the research collected in my dissertation, and they start to test some of the theories discussed in it. One example of this is in the photogrammetry scans where I have been creating texture maps, which apply the real word textures of objects to the 3D computer-generated models, this experiment starts to look at how embodied memories and visual haptics can be used to add additional immersive elements to VR. These tests will continue to be developed until I am able to put the models into a VR environment.

Another area of research that I have been looking further into is the discussion about the maker and their role in artwork. I created a practical test piece (dice tower diorama) which I then scanned into the computer and created a digital model of it. I started to evaluate my thoughts about the digital version and assessed my level of connection to the piece. Previously I have found that when I create purely digital work, whether that be drawings, animations or sculpts that I do not feel the same connection to them that I do when I create the same pieces practically, which is one of the reasons that I work in stop motion. However, through these practical experiments, I found that I had the same level of connection to the 3D scanned diorama as I do to the physical version, I believe that because the digital model still retains the remnant of my physical touch on it, the connection also transfers into the digital version. This is an interesting point that I have found as it links to the theories about embodied memories discussed in my dissertation, the piece of work is definitely sparking embodied memories for me as the maker and keeping that connection between physical and digital, the next stages of this idea will be to collect other peoples reactions to the work and see if the piece also sparks their embodied memories. 

When I reflect on the practical tests from the 703, they have all helped me immensely in different ways and being able to identify the point above that has helped me will mean that the next stages of the MA go much smoother.

360 Camera test

 As part of the testing process for this unit I used Michaela’s 360 camera and captured some video footage. Michaela then showed me how to use the VR compositing tools in after effects. While this test was successful I have learnt that the production pipeline using this method is not suitable to use for my project. 

The first part of this test was to use the 360 camera to capture the dice tower diorama, as this was only a quick test we set the camera up on the table and then just recorded 2 short videos so that Michaela could show me how to use the cameras app. This part of the test worked well and we found that It would have been good to have a hole in the diorama for the camera to go in, so that it was essentially placed within the world and was only capturing that world, instead of the tower and library like we had to get for this test. 

Then using these videos I looked at how to use the VR compositing tools in after effects. As I already know how to use after effects the process was easy enough to learn and is more a case of me finding the correct settings and tools. Again this section of the test went well and I learnt how to add titles and objects that can be used in a 3D space. 

It was at the compositing stage that I began to realise this production pipeline would not work for my project. In after effects, the project became 2D or 2.5D, meaning that while the viewer would be fully surrounded by the 360 video and that I could add additional elements and move them in a 3D space that they were not 3D. This means that my audience could not look around an object, go towards objects or touch or interact with them. As these are a large part of my idea, I realised that this test was not going to be a method that I used in my production. If I was making stop motion 360 videos to be viewed in VR like Phil Tippett's “Mad God” experience then this production method would work well as it is only meant to be viewed by a stationary audience, and only has the level of movement available in dome spaces (the audience has a defined area in which they can move, within this area the video doesn't move, you can only go so close to an area before you hit a wall of video, if you move beyond this space there is nothing.) as I want my audience to be able to look around and interact with the world and characters I realised that I would need to follow the production pipeline similar to that of VR game production, meaning that I need to look at building my world in software like unreal engine. 

While this test was successful in the fact that it worked it is not of use in my production, but it has allowed me to narrow down my final pipeline further and identified some more software that I need to focus on.