R135 Deduplication algorithm bug (now with capx)

0 favourites
  • 4 posts
From the Asset Store
Finding the shortest path through the cells based on the A-star algorithm
  • #UPDATED#

    Link to .capx file (required!):

    Deduplication Bug

    Steps to reproduce:

    1. The first layout is shown when run. Here "gsr" sprite is defined as global but destroyed.

    2. Press Enter (this takes you to the second layout)

    3. This layout creates an instance of the sprite "gsr". Pressing 1 to 6 should play its different animations. These animations will play correctly so all good up to now

    4. Press Enter (this takes you to the third layout)

    5. Since the sprite "gsr" is a global object it should continue functioning. But when alternating its animations using 1-6, youwill find out the first ones are corrupted (the ones beloging to the first sprite sheet).

    Note that this will work FINE on the preview (F5 or F4) you have to export it for the bug to appear (this is the reason I think the bug is in the deduplication).

    Observed result:

    Some animation frames of the sprite are corrupted in the exported version

    Expected result:

    They should display fine mirroring the result of the preview

    Browsers affected:

    Chrome: YES (tested)

    Firefox: YES (tested, corruption seems different but still happens)

    Internet Explorer: UNTESTED

    Operating system & service pack:

    Win7 64 up to date

    Construct 2 version:

    135

    Thanks in advance!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • After a long trial and error session I have finally produced the minimal capx that recreates the problem and "sanitized" it of all my resources.

    Deduplication Bug

    I hope this helps in finding the problem.

    Thanks again

    PS: Remember you will not see any bug if you run it on the preview, you need to export it for it to appear

  • Thanks, good find. I think this should be fixed in the next build.

  • Happy to help, thanks for the quick reply

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