For the past couple weeks, we have been learning how to use the Unity Engine, not over winter break fortunately. Unity is a game-making engine, which lends itself to being dependent on what you are making. In class, we're using the tutorial on Unity Learn, which is to say, kinda slooooooooooooow.
Mini-review for the videos, they are meant for people that's first time coding is with this program. With previous experience in script AND tutorial watching, the videos feel so drawn-out and obvious. Many steps can be condensed into one video, without losing cohesion, and I just do not enjoy them. The only important part is the information we need, and slow videos are good for understanding. The only part that felt like coding was the challenge, which was the only part we were really graded on, so that's fair. The software itself is very similar to 3DS Max, with it's 3D controls and axis based transformations, the only difference is the camera and modifiers, which are still similar. Now you can attach a camera to an object, instead of hook up points like 3DS Max animation, and assign keys for movement. The main difference between making a scene and a game is the coding, scripts are an integral part of making anything do something, more so than modelling. Almost everything is made because of it, making it the main focus of what we do in Unity. The software we use for coding is the default, Visual Studio. It gets the job done, it has each line and has text, it's not detrimental for coding to have the basics, especially with the average project being three scripts for one or two commands. So, starting out in already familiar territory helps in using Unity, while the tutorials are useful for people that either kinda know what coding should be or don't know any aspect of it at all. Altogether it is pretty fun so far.
0 Comments
|
JamesHe aspires to be a game designer, let's just hope he gets there. He also happens to goes to DSA. Categories
All
Archives
August 2021
|