This project has been a huge journey of learning. It would be easy to say that we are only using one technology in this project, and while it may seem that way, our project is built upon layers and layers of technologies. We are building our game in Unity and Unity, while one software suite, is a giant intermingling of technologies. For example while we are using Unity which already brings a lot together, we are utilizing other technology packages like Tilemaps, Post Processing Effects, Character Controller and about 20 more. Let’s not forget that we are also utilizing Blender to build and color our assets.
To start I think that Unity had the most difficult learning curve. Unity is a powerful tool that can do a ton, and first opening up the editor can be very intimidating. It takes some time to learn where things are, and what each part does. It takes even longer to learn what can be done with the technology. I really enjoy the technology now that I have learned how to use it.
Lately, I have been focusing on working with Unity’s Tilemaps. A Tilemap is a system that traditionally is used to paint 2D sprites and build those 2D games on. The big deal is we are using this 2D tool within the 3D space. It really doesn’t change a whole lot, you still paint the tiles like is done in normally. The difference is changing the 2D objects to 3D objects. Its quite a powerful tool that features allows the developer to accomplish a lot.
If there was anything I could change, I wish it was easier to use GLSL with Unity. The shaders course at OSU is built entirely around GLSL and Unity has built their own language for handling shaders. They have also built a Visual or Node scripting system for their shaders which has abstracted away much of what I am use to working with. For example, I haven’t figured out a way to effectively reference the normals from my own shader scripts, but I can reference them easily in the Visual Editor. While I may find it frustrating, like most things this is a minor issue that can easily be overcome through research and experimentation.
To start I think that Unity had the most difficult learning curve. Unity is a powerful tool that can do a ton, and first opening up the editor can be very intimidating. It takes some time to learn where things are, and what each part does. It takes even longer to learn what can be done with the technology. I really enjoy the technology now that I have learned how to use it.
Lately, I have been focusing on working with Unity’s Tilemaps. A Tilemap is a system that traditionally is used to paint 2D sprites and build those 2D games on. The big deal is we are using this 2D tool within the 3D space. It really doesn’t change a whole lot, you still paint the tiles like is done in normally. The difference is changing the 2D objects to 3D objects. Its quite a powerful tool that features allows the developer to accomplish a lot.
If there was anything I could change, I wish it was easier to use GLSL with Unity. The shaders course at OSU is built entirely around GLSL and Unity has built their own language for handling shaders. They have also built a Visual or Node scripting system for their shaders which has abstracted away much of what I am use to working with. For example, I haven’t figured out a way to effectively reference the normals from my own shader scripts, but I can reference them easily in the Visual Editor. While I may find it frustrating, like most things this is a minor issue that can easily be overcome through research and experimentation.