Arstechnica have put together the three rules of effective cutscenes as taught by God of War 2.
The rules are…
- Keep it Short, Stupid
- I shouldn’t be Superman in a cut scene but Clark Kent in the game
- If your engine is good enough for the game, it’s good enough for cut scenes
Obviously they go into more detail, but the points themselves are very valid.
My own opinion is basically that cutscenes are boring. It’s well known that a lot of video game artists would love to work in movies, and when cd’s were first used as a storage medium they decided to fill them up with movie clips showing off their talent. The problem was that, whilst technically impressive, the movies just weren’t enjoyable. One of the most important things I have learnt about animation (and I am far from an expert here) is to keep it short and sweet – keep the action flowing – and in video games this is doubly important.
People buy games for the gameplay – if they wanted to watch a film they would buy a dvd.
Cutscenes are something I have been thinking about lately as we are in the process of adding something similar to Gun Wing. However rather than going for the full blown cinematics we opted for a static image and some text. Creating the animations would have taken more work but was entirely possible however, in my opinion, a static screen works better. The static screen prevents interruption of the gameplay flow. Sure, it slows things down a little, but you only have to stop for 1 extra click. Slightly less important but a concern is the download size, not coming on a cd we need to cut corners where possible so that as many people as possible can download the game.
Was it good/ useful/ a load of old rubbish? Let me know on Mastodon, or BlueSky (or Twitter X if you must).
Link to this page
Thanks for reading. I'd really appreciate it if you'd link to this page if you mention it in your newsletter or on your blog.