Week 25, Year 2 Practice makes progress, not perfect

This was the last week before the Easter break and I had a lot to do before going home. What I wanted to make sure I got done was all my assets were unwrapped and ready to texture. I also had to get the level streaming working on the level but the big thing that happened this week was that I got feedback on my work.

I’m very happy with the feedback I got. On the container city project, I was told that %50 of the work contribution. I don’t know if that means out of me and the other 3 people in my group or if it’s only focused on me. The character project I knew I had done really badly on this project and I was hoping I would get the chance to redo it. Luckily I do get that chance to do it but it mean I’m going to have to take some time off, the off the map (OTM) project because the hand in is for the 24^th April but good thing is that we got a 2 week extension for OTM.

For this week I was working on getting all my assets unwrap before I left so that they could be textured by someone else. I’m ok at UV unwrapping but it not that fun and can be a little tricky to do right.

A problem we have been having with the level is the frames per second (FPS). A good way to improve the FPS is to level stream. Level stream is breaking up the level into smaller parts. Then can have these parts of the level load in and out when you want to. This helps the FPS because the engine does not have to work as hard loading everything in the level. I also got it set up so that when you come to a door that needs to load the next room. The door will not open until it has loaded the next area. 

The problem with doing the level streaming now is that it has broken a lot of the level blueprints because when you make a new level it gives it its own level blueprint and any objects with its own blueprint can now only be reference in that level blueprint. That means all the door locking system and matinees are now not working and have to be put back together.

It did not take me to long to get it all done just a little sad I had to go all back throw all that work.

Week 24, Year 2 To fix all, break something else and then fix it… wait what?

So after last week, not completing the level. The main thing I really wanted to focus on was getting the level working from start to finish. All was left to do was to finish the puzzle in room 3, add an end room to each puzzle area with a chest that gives you part of a key to unlock the finial door, and to add a lock system so the player has to go to room 1 first and only after they completed it, room 2 will unlock

My teammate made a small room that I cloud import into the level and add a chest to it that when the player overlays on a trigger around the chest, it will open. What came out was a particles that showed the play back to the key. I just did this with a matinee. I also link this up with the door locking system. So now when the player finishes the puzzle they unlock the next one all the way to the end door.

Now all was left was getting the puzzle to work in room 3. I ask my team mate to do this part because he had already made part puzzle work. So he has a better understanding of what to do but when he was trying to make the shorter staircase move, it would just teleport to somewhere random on the level. So when he went on lunch he ask me to have a look at it. When I try to test it, it would not move. When I look at both blueprints I could not see anything wrong, only that one node action class was set to the wrong blueprint but when I switch it out everything broke. It was only when I replaced the for each loop node it fix everything and made all the stares work.

So we finally had a working level from the very start. At last, this took a bit longer than it should of but happy we got it done now. Now we can test lighting, add assets, and texture the level. I will need to look at remaking the cut scene at the start because I made a new storyboard that shows off the character off better.

Week 23, Year 2 To know and to know how

So this week was really the same as last week. I just did some touch ups on some of my models and started to unwrap them. It’s really handy now because with unreal 4.7 you can just grab the export of your model and then just drop and drop it into the contents folder in the UE 4 project folder. What has really help speed things up. So when someone has finished a model and puts it into the file, if I have the project open I can import it in for them. No more need for them to have to open the unreal project as well.

I big thing that my team needed to do was make the level work from start to finish. This is still something we have not got done yet. We have got are starting area to work but we still needed to get all the puzzles working and add an end to the level. Luckily we already had 2 puzzles working. We need to get the anamorphic puzzle to work and get the stairs puzzle to work. The problem with the stairs was that we need to make just a new model and make the collision like a wage. So the player think he is going up some stair but really it’s just a slope.

The real problem was the anamorphic puzzle. The idea is that, when the play is in the right place they could look around and when they look at the right place it would trigger a door to open. James (another member in my team) had already try to make it, he had got the trigger to work. So that when the player is in the right spot, the area you have to look at become active. If the player in not in the spot and looks at the area then it will not trigger. Sounds like an easy idea right… well sadly not because to make this work it need to be in 2 different blueprints and not in the level blueprint.

So the problem was that I need to tell the look at Activator, when the player was in the trigger or not. The trigger blueprint had a variable in it that told it if the player was in it or not. I had to find a way to get that variable into the Activator blueprint so it knew what to do but you can’t just copy a paste it, and that what I know in my head what I have to do, but to know how to do it I had no idea. I did come across this document on the unreal engine website 

(https://docs.unrealengine.com/latest/INT/Engine/Blueprints/UserGuide/BlueprintComms/index.html) 

It talks about how to get to blueprints to communicate between each other. I knew that I had found what I was looking for but I found it hard to understand how it works. After many tries by me and James we could not get it to work and really that’s all because we only knew how it should work but we did not have the knowhow to make it work. Lucky for us we knew someone that had the know and the know how to make it work for us.

To know how something should work is one thing but to then know how to make it work is something very different and this really goes for unreal blueprints. There are many tutorials that can show you how to do thing and from them you get the know-how but some of these tutorials will miss out, the how it works. So if you try and try and make something new you may not know what to do because you don’t have the know how it should work. This is the problem I had but the other way round, I knew how it should work but I did not have the know-how to make it work in the blueprints.

What I do know now is that I need to learn more about the different nodes in the blueprints and how they all work with each other. So I can get the know-how.