Many people involved with the computer science and Digital Media and Animation major are hearing more about the Unity game engine; a free game engine for indie and professional developers. Much like other programs, it can be over whelming to learn a new program. To help solve this issue for the basics, a Unity seminar was held in SET 440 at 7PM. The event was hosted by Stephon Barrett with Michael Girard, Maria Frascella and myself assisting when needed. All participants were asked to install the newest version of Unity before the seminar began so they could all dive right in.
The topic of the seminar was a variety of sub-topics that had to do with the basics of using Unity. The first topic covered was the basics of the UI layout. This included the View settings so that people could select their favorite UI layout. This would allow people to find a format to use the software in which they are most comfortable. After learning a bit about the Unity layout and getting everything organized, we then moved onto the basics of creating shapes such as cubes and spheres. Everyone was then taught how to create materials to apply to the shapes. Stephon then instructed everyone on how to create a script to allow the cube to be parented to the camera and allow the camera to move based on the user’s mouse input. Once all of these processes had been covered, Stephon allowed everyone to mess around and try to modify the content we had created to learn how to make changes to our games and learn the software.
Some of the main points that really grabbed my attention had a lot to do with how important organization is. When making a video game or any other type of media for that matter, you’re going to have quite a few files to manage. It is very important to keep these files organized so that not only you remember where they are, but also for any teammates involved to easily find the files they need in an efficient and organized manner. If a person using the program were to just dump all of the files into one folder, others as well as themselves would be able to find the file they were looking for without a headache and in some cases depending on the project, compiling errors. Organization is important with any project and Stephon was able to communicate the importance of this method to everyone. For a Unity project, if you make a material, put it in a folder with other materials. Scripts? Put them in a scripts folder. This applies to everything: keep organized and avoid unnecessary headaches.
I can apply the various things I learned today at the Unity seminar to my work in DMA and this course individually. The most important thing to apply to ALL of my work is one that I am always careful to employ to the best of my ability; organization. Without organization, projects can easily fall apart. Pieces can get lost, ruined and in some cases, you may even forget to create something you need to have for your project because your directory or workplace is so cluttered you think to yourself “that’s not something I’d forget”; and then end up forgetting. Another important piece I have taken away from this seminar to apply to my future projects as well as this course is to double check your resources. What I mean by that is to go over any code you may be working on to check its sustainability and whether or not there are errors. Letting errors stack up can cause other methods to not function correctly and lead to quickly creating more problems.