hero/code504: Fix an annotation

This commit is contained in:
Matt Mascarenhas 2018-12-11 03:03:47 +00:00
parent ed384befde
commit 96f8783e1a
1 changed files with 2 additions and 2 deletions

View File

@ -14,7 +14,7 @@
[26:18][Investigate our :camera's positional hiccough][:research]
[28:30][Enable UpdateCameraForEntityMovement() to restart :camera interpolation when the target changes]
[32:32][Try out our newly restarting :camera interpolation, to still see a positional hiccough][:run]
[33:39][Reduce the MaxDistancePerFrame() in UpdateCameraForEntityMovement(), and initialise the hero in at the forest stairs][:camera]
[33:39][Reduce the MaxDistancePerFrame() in UpdateCameraForEntityMovement(), and initialise the hero at the forest stairs][:camera]
[34:13][Take a closer look at our :camera's positional hiccough on the stairs][:run]
[34:34][Continue to investigate our :camera's positional hiccough][:research]
[36:00][Fix UpdateCameraForEntityMovement() to restart :camera interpolation if either the starting or ending positions move]
@ -27,7 +27,7 @@
[44:12][Find that we've fixed the :camera's positional hiccough][:run]
[44:45][:Camera phases: Acceleration, Max Speed and Deceleration][:blackboard]
[46:59][Figuring out our options for getting the target velocity][:camera :"entity system" :research]
[49:00][Initialise the hero at her bedroom][:"procedural generation"]
[49:00][Initialise the hero in her bedroom][:"procedural generation"]
[49:35][Show our current :camera easing][:run]
[49:43][Change UpdateCameraForEntityMovement() to base :camera interpolation on accelerations, rather than start and end positions]
[1:00:21][Differentiating between the acceleration and deceleration regions][:blackboard :camera]