Coding Tips and System Quirks

-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0\|677\|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Off Topic -> Coding Tips and System Quirks
Mon, 25 Jan 2016, 08:05
Jayenkai	Any quirks you've found whilst developing? Stick 'em here!! Stick to "Power of Two" image sizes. Today I learned that Razer Forge won't do things with a 1280x1280 spritesheet, but is happy to do 2048x2048 ones!! Silly thing. Ensure your .wav files are at least 2048 bytes. PlayJam's "FlarePlay" device will occasionally crash if the .wav is less than 2048 bytes. (Eg for menu beeps, or tick sounds) When drawing a lot of tiles or sprites, I've found that they generally work "a bit" quicker if they're all on the same sheet. Either organise your spritesheets so that similar objects are together, or change your drawing order so that it does all sprites from a single sheet, before moving to the next. (Eg, player, enemy and bullets all on one single spritesheet might seem wasteful, and disorganised, but can occasionally speed your game up if there's a lot going on.) -=-=- ''Load, Next List!''