WEEKLY NARRATIVE
This week was a roller coaster of events and the start was the going down and the end was the going down and backwards.
There was some going up, slow and nice.
Anyway, this week I populated the levels and united them and put some props around and fixed some bugs.
One of the big issues was doors. Some doors were not aligning correctly.
Not like three weeks ago where they opened weirdly, this is another one.
It had to do with the rotation of the mesh in the world and what the script was taking in.
I had to find out what to do to fix this and well, it's kinda weird now how some levels go from point A to B. JUST SO THAT THE DOORS WORK.
I also imaging no one has touched the x-ray level because the doors are broken there and only there. If it was an easy boolean check anyone could go in and fix it.
I am too exhausted of doing that, so until someone else tells me to do it, I am not touching it(but is not).
CONTENT WITH HOURS
- 1 hour - meeting
- 3 hours - Merging new xray to game + bug fixing it
- 2 hours - Scripted events / level layout / fixing a bug no one saw but can be seen in previous builds
- 1 hour - Level design critique.
- 30 min - Review models
- 8 hours - Adding 3 floor level and scanner challenge 02 and making it fully functional.
- 30 minutes - merging that level.
- 1 hour - adding new enemy prefab.
- 30 minutes - Fixed issues with perforce. twice.
- 1 hour - Adding the enemy to the new levels.
- 6 hours - Merging the levels for the "open" world.
WORKFLOW
Here's an example of a door that is broken. That's the closed stated. It has a rotation of -21.74 degrees. Even if you put 0 in the rotation, the script will still take the -21.74.
This is a scene of a level that I kind of changed since the document said 4 horizontal bookcases but I put 2 big ones and something in the middle to walk (yes, you can dash through a wall to get here).
Positive outcome
- Last week I said I wanted a QA, we got a QA.
Negative outcome
- Perforce is some times dumb.
- We should have a list of what each level requires and how they are built, otherwise it slows down progression because it has to go back.
- People think that a fix to something is just turning a boolean. Is not.
Next Tasks
No clue. We normally don't get information about what to expect next week.
Total hours: 24.5 hours

No comments:
Post a Comment