Curious Expedition download the new version for mac

If you have an overlay or a visual effect on top of your main game, and you can just update that without needing to redraw all of your sprites/tiles, that can sometimes be a big performance benefit. Also on that note, don't be afraid to use multiple canvases. In general, don't be afraid to stick generated effects in RAM, because every call you make to Canvas has an overhead. Then for subsequent frames I can render that with a single sprite call, rather than by iterating over every tile.Ĭaching visual effects is huge. At the start of a level, I iterate over the tiles on an offscreen canvas and generate a single, giant image for the entire map. Went back and profiled later and found out it was taking something like 30% of my render time each frame, and refactoring just that one block of code got rid of a bit of stuttering on old hardware. I once stuck in a quick dozen-line block of code before a demo that just drew a couple hundred tiny pixel stars in the background and occasionally randomized their position. For example, if you want to draw something simple like a bunch of boxes on the screen, grab the pixel array from the canvas and manipulate it directly, don't call `ctx.rect` in a for loop. If possible, avoid lots of canvas calls. JS timers are really bad, and they won't sync with monitor refresh rates. Use `requestAnimationFrame`, don't use timers. Not OP, but a few tips from my experience: Of course no need to download or register and works on mobile.

You can play with your friends and people online.

It's a RTS game, where you need to conquer planets. I'd use illustrator instead of Photoshop because you can scale your graphics without losing quality. Pixi just does the rendering part, phaser does a lot of game related things) I usually prefer to start the game multiplayer first and then do single player.Īnother tool useful for game is pixi.js (or phaser if you need what they provide. Another benefit is that you can also make your game single player much easier. Use node.js on the back end so you can do client side and server side validation with the same code. I'd start away from any other language, like coffee script, Ruby. If you're serious about large scale games, you should look into typescript.

Curious Expedition download the new version for mac