- Sea Lady -
Because attempting to animate in the purgatory that is a midway between Sai and Photoshop is akin to sawing off your dick with a nail file, I got around to this last week.
The goal is to allow for viewing of wip animations being made in Sai without having to load the project into Photoshop, Flash, or whatever your external timeline of choice is. Essentially, you export each frame as a .png into a folder and then just overwrite them in the same way when you want to update a frame.
On load it defaults to whatever directory it’s sitting in, but if you want to keep it somewhere else you can select the folder source post-load.
Images are loaded alphabetically, so all of these are valid:
- a.png, b.png, c.png
- 1.png, 2.png, 3.png
- Frame1.png, Frame2.png, Frame3.png.
It runs off .png files because I don’t see why you’d use any other format in 2014. If anyone desperately wants .jpeg support or something I can add a toggle though.
Image locations are loaded fresh upon each iteration and held within the program so you can add, update and remove frames without stopping it if you want to. This means you can leave it open on a second monitor and have a looping preview without leaving Sai.
Shit runs on .net 4.5 since C# is cakewalk for stuff like this.
Ib in progress
New friends for my books ♥
Basically, there should come a point when your character doesn’t bounce back any more. Like bending a plastic ruler, it’ll only go so far before it snaps in the middle…
For this kind of thing, it’s how you write the suffering, not what you write.
Generally, I think if you can’t physically imagine how the character would/should respond after several rounds of severe punishment, then the punishment is unnecessary.
My best example of how to explain my meaning is to look at a character like Starscream from Transformers. If you don’t know him, he’s ambitious and frequently tries to usurp his leader, Megatron. Naturally, Megatron is wise to his motivation and punishes Starscream swiftly every time he makes the mistake of plotting against him. It’s not just a sharp telling off either; torture is hinted at throughout several of the universes. Sometimes, Starscream has good intentions but they backfire, which leads to a punishment as well.
So in short, he’s the perfect character to abuse for the sake of evoking angst, which is why you have to take care when writing him. You could say the same about Loki from Thor, too, but sticking with the original example, here are some tips:
Don’t Go Too Far With the Detail
Most of the time, Starscream’s punishments happen off-screen/panel and when they do happen for us to see, it’s directly in response to something he has done to warrant it (and it’s not gratuitous, so a shot to the chest, a single punch/kick).
Gratuitous would be showing every single punishment, complete with begging, injury and crying. A torture scene doesn’t add much to a character (especially not the one on the receiving end), unless you go a la Supernatural and use it to bring out a hidden side to certain members of your cast (or to shine a light on something, for example). Using it for the sake of seeing your character crying and begging through the pain is not the way to go with it.
Apply this reasoning to all the events you choose to brew conflict. If it serves no other purpose but to make a character cry and feel sad, then think about how it can be more than that (i.e., how it affects the character beyond an emotional level, and how it affects the whole story).
So, we don’t see Megatron constantly wailing on Starscream as he cowers in the corner and begs it to stop; at most we see him begging for a second chance before the punishment, or brushing off the dust once the punishment is over. That’s two key points, and there’s a reason these are focused on over the torture scenes.
First off, it shows Starscream’s cowardice and inability to accept responsibility for his mistakes. Sometimes, he deserves to be put in his place because he jeopardises so much with his behaviour (and often betrays the group vision so he can get ahead).
It also shows his determination and his willingness to succeed. Starscream is not a battered and abused victim. He knows and expects the outcome every time, he just doesn’t care enough to allow it to stop him from achieving his true goal. He’s prepared to put up with the punishment, even if – close to the payment – his senses kick in and he realises it’s going to hurt (after all, I personally don’t think he derives enjoyment from being in pain; he just tolerates it).
Basically, he doesn’t learn. The repetition of this scenario throughout the various universes confirms that.
And that’s the bare bones of it.
Of course, this is a very basic look at Starscream’s character… There are always different interpretations to it as the fandom is vast (and the universes multiple), but for the purpose of this response, I think my interpretation serves the point: that suffering should neither force your character(s) to abandon all motivation, nor become gratuitous. The events you impose upon your cast should always further their development, their relationships and the plot as a whole.
Starscream’s antics are frequently used as significant plot points, for example.
Generally, it’s the negative things that keep a story going, so you don’t want to be sparing with the suffering, or let your characters become too content… but they also need to have a reason to keep ploughing on through the bad times. It’s all about balance.
I hope this helps a little…
- HOMELAND’S BRODY: When A Character Suffers Way Too Much
- Too many bad things happening to good characters? | NaNoWriMo (forum discussion)
- Fiction Writing: Conflicts and Characters
You had me at Starscream.
Some Jean happened
|classmate:||what are you reading|
|me:||(holds book up higher to show the cover while continuing to read)|