Tokinsom's Forum Posts

  • Far as I'm concerned, the behaviors and all the built in stuff are to blame. Most other engines have you make your own platform engines and such, as well as level editors, data tools, etc. With C2 you don't really learn much of anything...so if you start with C2 you'll likely always be a "noob". Not to say I don't appreciate behaviors and all, but ultimately we'd be better off with more features to make our own exactly how we want..

  • As I said, the bullet behavior is too buggy for this. It doesn't handle corners well and occasionally bounces in the wrong direction.

  • I made a bouncy ball with the bullet behavior (increase gravity, bounce off solids, etc.) but it's kind of buggy and bounces the wrong way near corners. I'd like to just make one using events but I'm awful at this sort of thing. Anyone mind making or sharing a simple bouncy ball example?

  • Welcome to the wonderful world of browser based gaming.

  • eli0s *shrug* It's a feature that's been requested since the dawn of C2 yet still hasn't been addressed. It would require a decent overhaul of multiple existing object types including a tie in with an animator like sprite objects use, but stripped down. It also doesn't seem to be an insanely popular request with 5+ pages which is what it takes to get big new features these days. Not trying to be rude about it; that's just how it is with a 1 man team.

  • Would be nice to have this for Tiled BG's, SpriteFonts, and Tilemaps as well. That way you only need one per project and can swap between images as needed. Probably not happening though T_T;

  • Yeah global layers are completely different. Perhaps we could have a way to import layers and their properties from one layout to another? This way you can have unique layers for title screens and such, then for levels you can import layers from the first level. Adding or modifying a layer on all of them would still be a problem though..

    Or maybe a new layout property to share layers with other layouts with that enabled. You can then disable it for unique layers or properties.

  • +1 Some way to share layers between layouts has been requested a dozen times and is definitely something we need.

  • +1. Selecting already-placed tiles is often requested as well.

  • Oooh ok. Sorry for jumping the gun on that one ^^; Looking forward to the next release then!

  • I'm just assuming this is everything because there have been 3 releases since that thread. If there are plans to continue with these features then yeah the rendering cells are pretty useful. I personally will be modifying the tilemaps at runtime so I'd still create/destroy them as needed, but they will be good for static backdrops.

    The initial load has crossed my mind. All I can think of is a layout option like "Don't create objects at start of layout" and we can do it ourselves with zones. Maybe it ignores global layers or objects w/ persist behavior or something for HUD elements, player, etc.

  • Ashley recently optimized the destroying of objects specifically for this. Loading on the other hand might cause a slight hiccup if your zones are huge but, as you said, lazying loading can fix that or the dev can put in some sort of transition.

    The creation & destruction of objects is necessary to "reset" them when re-entering a room or zone, and making sure that nothing is going on outside of the current room or zone. What better way than just destroying them and calling them back when needed? Instead we got this new action that doesn't really apply here...

    Layer zone isn't a bad idea either but you'd then have to specify the object types for each layer so that's a no-go.

  • Ashley To my knowledge, Rendering Cells & the new system action "Reset persisted objects" were to address the issues brought up in this thread.

    However, I fail to see how they do so. The consensus was to add a single new action, something like "Reload Layout Zone (x1,y2,x2,y2)" with a button to specify which object types in that zone would be reloaded. This would allow us to dynamically load & destroy portions of a layout, which would be ideal for metroidvanias & open-world type games such as Zelda.

    What I don't get is how "Reset persisted objects" is supposed to solve this, since it only works when you exit and re-enter a layout.

    The rendering cells were also surprising because, with the above solution, "far off cells" wouldn't even exist outside of memory. Instead, the "cells" would be loaded & unloaded as you progress based on distance to the player (or however the dev wants), which would result in a lower average CPU/GPU usage. I suppose they are currently beneficial to GTA-style sandbox games where you have one continual seamless area with no resetting, but that's about it.

    Is there something I'm missing? Is the "Reload Layout Zone" action still on the horizon?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • While we're on the subject...what about making tilemaps center-oriented? Right now you can't resize them without screwing up your tiles :T

  • I'll probably get shot for saying it, but...Multimedia Fusion 2 / Fusion 2.5. Unlike Construct, Game Maker, Stencyl, etc. it's geared towards game AND application development, and is surprisingly powerful in that regard.