W1: Getting Started w/ Maya
When first getting started with Maya, I was extremely overwhelmed. After the first round of tutorials, I felt slightly more comfortable. The first 3D chair video was a huge learning curve. It felt like every step I did something wrong. Once I had completed that first video, I became much more comfortable.  I quickly learned that if I tried to work ahead, that I would run into some issues. Below are some things I ran into issues with.  I do not feel like I would be able to recreate this without the help of the tutorials just yet. With time and practice I am sure it'll become easier. 

W2: Getting Started w/ Unity
This activity was fun and interesting. I was able to become slightly more comfotable with this compared to maya. 
W3: Audio, Images, and Video 
In this workshop we learned how to add photos, videos, and audio into our unity workspace. I found adding images in unity to be easier than adding it in maya. The only frustrating part was that the images are sometimes cropped. The only way to solve this is by putting the image in as texture in maya. I really enjoyed putting in videos. It was simple. i was confused at first when the videos didnt automatically play but it was because my screen was in pause. Adding audio is simple because you can just add it to an object such as a cube. 
W4: Testing & Development
This week we learned how to hook up the oculus headset to unity to preview our project. I struggled with this. Sometimes my computer wouldnt reconize the headset or would forge the login info for the class account. It was frustrating to get set up but once it was ready to go it was quite easy to use and was extremely helpful. 
W05A: Locomotion
In this workshop we learn how to allow players to move around the virtual environment. The ACCAD Player Rig is basically a camera with other interactive components. "Flow" allows us to navigate around. The blue space shows us where the player is able to move about. You do not want to use the same game object in both the main scene and side scene. Avoid this by making a new game object. The term "bake" is new to me. This allows us to map onto our new plane. This was quite easy for me to understand and easy to complete.
Areas in blue= can move about in
Areas in gray: players cant move about
W05B: Interaction
Allow users to pick up a game object. Place the grabbable cube under custointeractables into the hierarchy panel so it can become intractable. Be sure under visuals that the new object is correct under renders and element 0. This had a a few trouble spots but I quickly overcame them and became comfortable with the topic.
W6: User Interface 
This teaches us how to have a "touch to play" button that allows audio or video play or stop. Can be used in 2 ways: as raycaster which is pointing at a button then interacting or touchbased input where when we touch the button the clips (audio or video) play. Begin by creating a plane and add a video to it. Two options that come from this are button ray container (point) and ButtonPoke Container (touch). We are focusing on the poke. I like how easy this is to connect to other interactions. It is a simple duplicate that allows us to make this happen. To edit what sounds play or other to happen when touching the button, go into when selected hovered to connect what is needed. The video will play on loop unless directed otherwise. This can be changed within scripts. I found this workshop easy because of previous workshops of inserting videos into a plane. This was easy to catch on and I feel confident. 
W7: Animation & C# Scripting
We learned how to create simple animations. I was exposed to the animation and animator pannels. The animation pannel is where we create our animation clips. Once opened, we add the drawer opening animation to our 3D model pannel. We then choose add property to open the start and end keyframes. You then hit record and perform the action that you want. Must be specific (one animation for open and another for close). Once that is ready to go we head into the animator pannel. Once there, go to parameters and add New BooI. We then are able to make transitions between our different animations. You are able to add conditions that allows drawers to close if opened. You must be specific because if not the drawers will open and close automatically. This can be changed by turning off the loop. We are now able to connect a button to make this drawer open by players command. I really really liked this section. It reminded me of after effects and other projects ive been working on in my animation minor. This was fun to learn and easy to comprehend. The only thing i am slightly iffy on is scripts because its just something I havent worked with much. 
W8: Pre-Made Scripts
We learn how to use pre-made scripts to create more interaction into our scenes. Player trigger event script which is used to tirgger interaction from users location within the scene. We use "TriggerEnter", "TriggerStay", and "TriggerExit". We create a trigger area by inserting a cube. We then adjust it as needed and add player trigger event. Under trigger enter, move the video player under runtime. Choose play video scripts and then videoplayorstopfunction. Do the same for the video stop. This makes sense to me. I would need to follow this tutorial a few more times to become more confident. 
Back to Top