Devlogs
Journal Entry 5
Activity:
- Setting up Unity on Windows
- Going trough scripting tutorials 3 and 4
Invested hours(I'm counting only hours at home):
- Setting up Unity: 30 min
- Scripting tutorial 3 (majority done in practicals): 30 min
- Scripting tutorial 4: 3 h
Outcome:
- WebGL build of a platformer game in Project T with scripting done from tutorials 3 and 4
Notes:
- I decided to not debug why Unity editor was crashing in some scenarios (mainly when I was trying to edit level visuals or animations) on my Fedora system, but I decided to set it up on Windows (I have dual boot). It didn't crashed even once, but I noticed that it takes way longer (2-3 times) to load the Unity editor, and the performance is overall worse, but it works now so I'm fine with that! ... :)
- Migrating project to my Windows setup was straight forward, no issues there, just copied the directory and Unity made it's magic, the first load was very long (around 10 mins) but I didn't interfier in any way and it just worked
- Scripting tutorials were great, a lot of interesting stuff. Sometimes I got lost, mainly because I read that too fast... I was like: Why it doesn't work?? Oh I skipped this step... In the end everything works. It's great that we tried multiple approaches. For me tutorials were quite time consuming, but I'm really trying to understand what am I doing.
- Unity system as a whole starts to make some sence for me, in the beggining I was quite confused why is it designed in this way, it's better now. The whole concept of components was new for me so I needed to get used to it. I was used to OOP approach.