[SOLVED] Wargame Map Object - Inconsistency with HTML5

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.
  • [SOLVED] See the last post.

    Hello Clickers,

    by using the Wargame Map Object I'm experiencing some annoying behaviour inconsistency between Windows and Html5 engine.

    Here two screenshots. It should be an easy straight vertical path. In windows works, in Html5 does not:
    Windows:
    Please login to see this attachment.


    Html5:

    Please login to see this attachment.


    A question: is the Wargame Map Object someway broken in Html5 ? If this is the case, will it be fixed in the next build ?
    I just wanted use it in my RTS game. I find the Wargame Map Object a good alternative to a classical path finding, because each waypoint cost can be changed on the fly.

    I would be more than glad to test any JavaScript patch/workaround that could fix this issue :)

    Attached the related project file.

  • Problem solved !
    Thank you tobydavis and phi ( discord ) for your great support !
    For the ones that may be interested to the solution (quoting tobydavis/phi ) :

    just replace line 229 in WargameMap.js, which looks like this:
    var g = gCost[current] + this.map[next];
    with this:
    var g = (gCost[current] || 0) + this.map[next];

    The WargameMap.js file is in the Data/Runtime/Html5 folder inside of your Fusion installation directory

  • Just for the sake of completeness, there *is* still a difference between Windows and Html5 behaviour.
    This happens when you search a path from bottom to top.

    In order to show this behaviour, I have slight modified the map deleting two obstacle-diamonds.

    Windows:
    Please login to see this attachment.

    Html5:

    Please login to see this attachment.

    Anyway, I can live with it, and adjusting the map granularity helps to obtain more "straight" paths.
    As said, I just wanted to point it out for the sake of correctness since I was asked to report any other behaviour differences.

Participate now!

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