For instance, they come out semi-randomly, at slightly different speeds and sizes, and each smoke cloud randomly chooses from 7 separate handmade animations. These are hand-drawn and animated in Toon Boom Harmony, but to make them look extra believable and fun, they are also generated and manipulated programmatically. Spryke generates animated smoke clouds out of her side vent as she moves. Here's a little sample of the sort of optimisation work I've been doing: I've done a lot of benchmark testing to see where I can most beneficially streamline the code, and I'm developing a lot of good habits that I'm going to keep as I go forward.
CLICKTEAM FUSION 2.5 FREE VERSION SUCKS CODE
However, cleaning up after old code is proving so time-consuming that I'm determined to make all my code from now on as optimised as possible.
Though I know so much more now than I did when I started, so it's probably best that I left the fastidious stuff till now. I was never sloppy, but tried not to be too fastidious either. I always knew I'd eventually do a wave of optimisation, so I was never too fussy about how I made my code. Up until now, I'd taken to heart that silly adage about premature optimisation being the root of all evil.
To be honest, I'm getting pretty sick of this process, but it's important, and I know I'll be very grateful to myself when I'm done. And, of course, I've broken lots of little things along the way, so after all this my next step will be to repair all of the 'optimisations' ) I've refreshed a lot of the code already, but I'm still knee-deep in the process. Merely figuring out how it worked was time-consuming, as has been untangling it and reshaping it into something more modular, optimised and manageable. I was getting tired of breaking things when I added a new feature and not even being able to tell how it was broken. This code was visibly inefficient, and all but completely incomprehensible to present-day me. Spryke's unique movement engine) was 3 years old, written when I was a beginner with Fusion. Part of that also means cleaning up the code and getting it into something resembling a publishable state.Īlso, some of the really core code (eg. Not just an assemblage of levels, but an actual game, with a solid skeleton and all the necessary stuff, like proper loading screens, graphical options, robust camera, and so on.
Secondly, I'm determined to make Spryke feel like more of a game this year. Spryke will never be the sort of game that runs blisteringly fast on a tinny laptop with integrated graphics, but I'd certainly like it to run well on anything even resembling a gaming PC. I always told myself that this would be the point where I'd stop and start looking closer at how I'm doing things.
CLICKTEAM FUSION 2.5 FREE VERSION SUCKS PC
Firstly, the performance was starting to creep into an area where even on my relatively high-end gaming PC it would sometimes dip into subpar territory (ie. I've spent the past couple of months overhauling Spryke's code to make it more optimised. It's been a long while since I've written any updates on Spryke, so I figured I'd better hop to it.
0 kommentar(er)
