Collision - 'Add Backdrop' always creates obstacle

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • I have a game working in MMF2 that pastes an Active Object into the background as a Background Object, which I've specified to be "Not an Obstacle".

    When I export to SWF, the newly created Background Object keeps registering collisions, even though it shouldn't be an obstacle. I've tried using the "Paste image into background" and "Add Backdrop" functions with the same outcome.

    Is there a known issue with the SWF exporter that would account for an Active Oject colliding with a non-obstacle backdrop that's been created from an AO?

    .: Nuclear Powered Games :.
    coming soon...

  • It works fine in SWF, I have a game where I do what your saying allot through out the game with no problems.

    Does it do it if you run it as a standard application?

    How is you event setup that paste it into the background?

    Can you upload an example of what your doing?

    Please login to see this link.

  • I think I might know what is going on here. In Flash, you cannot "overwrite" the collisions on the backdrop. Example:

    Laying a floor(with collisions) down, and then laying a "Gap" backdrop object with no collisions works in MMF so long as the Gap is above the background floor. This is because MMF is smart enough to know it doesn't need that part of the floor collisions if another backdrop is on top.

    However, in Flash, the flash game doesn't replace the floor, it simply adds a second backdrop on top. The old floor still exists under the new Gap, and so objects will still collide with the old floor object, even though visually you've set it up the same as the non-flash version.

    Basically, you cannot punch "holes" in a backdrop in flash using the add backdrop or paste into backdrop functions. Flash itself just doesn't support such pixel manipulations for it's objects, it stores the backdrops seperate. If anything on a given stack of backdrops is collidable in flash, no matter the layering, objects will collide.

    The only possible manipulation in flash is to add additional collision backdrops, not "subtract" existing collisions through overlapping. Once something has collisions on that part of the background, that collision sprite will be there forever no matter how much you cover it up with no-collides.

  • I think maybe something else is going on here. As I mentioned before I have a game that I create backdrops from actives then delete the actives.
    My game has been running fine for along time now, I was updating it today and now the actives are not being destroyed.
    I'm thinking it must be an extension that is causing this problem.
    Anybody got any ideas if any of the recent flash extension would cause an issue like this?

    Please login to see this link.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!