Timeline for Creating my own kill cam
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28, 2011 at 2:00 | comment | added | Steve H | Please re-read, You save transforms for all appropriate dynamic objects, not just matrices for players. It is also easy enough to save health or hit-point data and other items as well too. The point is, saving too much data consumes game time resources, (bad). You save as little as you can get away with and let your rendering engine do as much of the heavy lifting by interpolation during replay as possible. It is a compromise but what isn't? | |
| Nov 27, 2011 at 22:15 | comment | added | Ali1S232 | there is one problem with storing only transform matrices, not saving anything else! for example if you only save transform matrices for players, animations may go wrong you won't be able to see how much damage enemy took before killing you and when did he fire his gun. there a long list of details you miss using your method that you can easily think about them. | |
| Nov 27, 2011 at 22:05 | history | answered | Steve H | CC BY-SA 3.0 |