sqiddster's Forum Posts

  • Event count should not effect performance, unless every event is actually being checked. The profiler will tell you all you need to know about event sheet performance. And having them on one event sheet vs multiple will make no difference.

  • Thanks for your support, everyone! Keep it up!

  • I hate to derail the thread but it looks like you're committing some serious copyright infringement. Probably not a good idea to put a lot of effort in a game like this unless you're *sure* you'll get the rights.

  • There are a few serious problems involving third parties which are currently hampering development of Construct 2 desktop games.

    I'm sure I speak for all the desktop developers when I say we'd be thrilled if you could spend a moment of your time and help bring attention to these issues.

    1. NW.js does not work on mac and linux for large projects

    Yep, that's right, the latest versions of NW.js have a bug that prevents projects with lots of images (so, any big project) from running on mac and linux. While 10.5 still works, there are unfortunately a lot of other problems with 10.5 and bugfixes for version 10.5 aren't going to happen.

    To help out with this issue, leave a comment (or, if you're feeling generous, a bounty) here.

    2. Chrome runs like absolute rubbish below 60fps

    For some reason, any time a C2 game dips below 60fps in Chrome, bad things start happening. 59fps is literally unplayable in a fast-paced action game like Airscape.

    This may or may not be more of an issue on fillrate intensive games, more testing needs to be done here.

    If this issue was fixed it would bring an 100% increase in effective performance in C2 games, as anything from 30-60fps should be perfectly playable.

    To help out with this issue, star/comment on the chrome bug report here.

    Again, thanks for your help, it's very much appreciated.

    Daniel

  • You do not have permission to view this post

  • One thing I will say is do a comprehensive performance test of the 'worst-case scenario' at a high resolution, with lots of particles, layers etc. This won't test the CPU but at least you'll know if the browser can handle it on the GPU side.

  • Yeah it works in most browsers AFAIK

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • No, collision is only checked when you check it. So turning off collisions if you never check it won't have a performance impact.

  • LICEcap has worked OK for me:

    http://www.cockos.com/licecap/

  • Wow, you guys read my mind!

    As for a use case, 'force own texture' guarantees an entire extra screen of fillrate. At 1080p that's HUGE, and having graphical settings in a game to turn some special effects on/off will be critical.

  • —

    The reason functions are good here is because you know for a fact that you'll never have to go to every instance of a call and change it. For example, say you didn't want "SaveSlot" to be a global variable anymore, but a Webstorage/LocalStorage value. You'd simply have to change one reference in the function, and that's that.

    There are a lot of other reasons functions are cool, but the best way to realize how useful they are is to try and use them!

  • — it's an absolute lifesaver when you need to move to a save slots system. All of the webstorage references in Airscape are function calls that pulls the data from the current save slot.

  • You can store arrays in dictionaries! Unpack/pack them during saving/loading.

  • What do you need to save in webStorage that you need a whole array of values?

  • The easiest way to do it is probably:

    1. make a dictionary called 'storage' or something

    2. replace all webStorage references with references to that dictionary (or, if you really want to go the extra mile, replace them all with function calls that then reference the dictionary)

    3. save/load the entire dictionary from LocalStorage at specific times (e.g. on startup, on exit, at the start/end of every level, etc).

    That way, you can keep using storage references without needing to worry about the whole async issue.

    Of course, if you are using webStorage to store MB's of information, this approach might not be the best.