Request: more choices for hot spot of tilebackground object

0 favourites
From the Asset Store
Be quick and choose the right answer for the shown equation.
  • There are two items -- "Top-left","Center" could be selected in hot spot of tilebackground object.

    Could it have "Center-left" , or some others possible items to be selected?

  • +1

  • +1

    ...and animation frames please!!!!!!!!!

  • Ooopps , I forgot to notify to Ashley .

  • I've been thinking for a while that a tiling mode in the Sprite object would cover all of this, since it already supports custom origins and animations, and means that doesn't need to be reinvented for the Tiled Background. It would however make Tiled Background kind of a redundant object which could be deprecated, but then this is a pretty significant change to a core object which is used in all sorts of videos, tutorials, descriptions etc. all over our own site, manual, and the rest of the web. I'm not sure what to do about this - perhaps we could add a tiling mode to Sprite and keep a somewhat redundant Tiled Background just because lots of people will still expect it to be there?

  • How about merging the two object types, and maybe change the name so people new to Construct would understand that it may be usable both for Sprites as for Tiled Backgrounds?

    I think that is a more elegant solution than keep a redundant object, although it will take a lot of work, because all of the learning material use Sprites and Tiled Backgrounds as very different plugins(as they really are today).

    I don`t know, something like "Animated Image", or "Tileable Sprite"...

  • Ashley ,

    Adding the tilling mode to the Sprite object will be a blast! I think that we should have the option to turn it on/off per animation and globally. That will be more flexible.

    As I understand, the Tilled Background object uses less resources than the Sprite object, so you should keep it as an option for a more CPU friendly solution, whenever animations aren't required.

  • As I understand, the Tilled Background object uses less resources than the Sprite object, so you should keep it as an option for a more CPU friendly solution, whenever animations aren't required.

    No, I don't think that's true, so I don't think it counts as a reason to keep Tiled Background. You should prove that with measurements, because a single frame non-animated Sprite should be identical CPU-wise.

  • It depends on what it would do across the board performance wise.

    Which is heavier sprite, or tiled bg?

    I do remember that tiled bg is worse on ios safari with multiple instances.

  • Sounds great!

    But would this new "Sprite" behave same way in layout editor as tiled background?

    I mean if you create black 8x8 Tbg and resize it to whatever, it will be black from corner to corner.

    While creating and resizing 8x8 black sprite creates quite big blurs, which are a bit confusing when placing objects on layout.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Ashley , I have no reason to doubt you. I thought that at some time I'd read that the sprite object supports more functions, therefore C2 has to calculate more stuff for each and every sprite, so we should use the Tilled Background whenever we can to avoid performance drops. It seams I misinterpreted that, the actual instruction probably was "don't use multiple sprites to create tilled images, use a single Tilled BG..."

    Never the less, the benefits of having animated and fully controllable pivot-wise tilled sprites are too many, weighing the implementation or not of this functionality based on the existence of the now redundant TBG is irrelevant in my opinion. Just Keep the TBG for overall coherency and backward compatibility.

    shinkan , you are right, with tillable sprites this phenomenon should cease to exist.

  • eli0s I think that would be resolved by putting a "tileable"checkbox, so, if it`s tileable it would ignore the collision polygon and just use the bounding box, etc.

    This would resolve shinkan problem also, because the pixels will be tiled, not stretched, as in regular sprites.

  • , I agree. I just think that the "tillable" option should let us choose if we want all animations to be tiled (a global checkbox), or to specify which of them will be and which of them won't be tiled.

  • Its sounding more, and more like a behavior.

  • Its sounding more, and more like a behavior.

    Maybe. Thing is, it wouldn't make sense pairing it with anything other than sprite...so why not just bundle it in with sprite? I like the idea of an enable/disable tiling toggle.

    Just Keep the TBG for overall coherency and backward compatibility.

    Once the tilable option was added and the bugs worked out, TBG could just 'disappear' from the plugin list. However, it would still be in the plugin folder, and loading any old projects would just load it in (though, perhaps C2 could provide a message that TBG's are now obsolete, and highlight TBG object in red or something).

    Any new users going to add TBG's wouldn't be able to, and will head to the forum and find that they can use sprites instead.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)