I felt compelled to this time, because it’s been awhile, and I suspected my eye for detail might have suffered a bit from the sabbatical.
So I guess I shouldn’t complain when it turns out I was right. There are some glitches and visual unpleasantries that I just plain missed, or overlooked. And the only way to fix them is to go back and re-render selected bits of source footage, after having remedied the Moviestorm glitches. This late in post, that’s a bummer.
Those on my panel who noticed the glitches were very forgiving, acknowledging that they are Moviestorm issues and there’s probably not much that can be done about that. The onus being on Moviestorm to fix those things.
For the past week, I’ve been chewing on that. Trying to determine, can I live with that?
To at least some degree, I have to. Moviestorm is where I’ve invested my time, it’s the tool I know how to use. And as I put it in a comment of my own to the panel, I’ve probably got more stories to tell than I have time on this earth to tell them. So right now, starting over with a whole new kit just isn’t in the best interests of my long term goals.
But I don’t have to live with imperfections that I *can* fix. Sure, it would be easy to just say, ah well, I’ll just release this one as-is and try to do better next time.
No. Not anymore. If I’m not going to give this my best – and that means taking the time to go back and fix what is fixable – then I shouldn’t be doing this at all. Yes, there will be things I can’t make Moviestorm do. Yes, I’ll have to take caution to not get caught in the endless improvement loop that leads to ridiculous release delays.
But these animation and lighting issues… I can do better. And I’m going to. Not just next time. This time.