User Tag List

Results 1 to 4 of 4

Thread: Alterables set in nested fastloop problem or qualifiers in overlap problem?

  1. #1
    Clicker Fusion 2.5 (Steam)Fusion 2.5 Developer (Steam)Android Export Module (Steam)HTML5 Export Module (Steam)iOS Export Module (Steam)Universal Windows Platform Export Module (Steam)

    Join Date
    Feb 2016
    Posts
    21
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Alterables set in nested fastloop problem or qualifiers in overlap problem?

    I have a problem of setting alterables variables/strings in a nested loop.
    3 different active objects.
    One type of objects has a qualifier '0' and used as ground (name 'Q0').
    Other two types of objects have a qualifier '1' - one object as falling block (name 'PushBlock') and second as ground (name 'Q1').

    In all nested fastloop events 'PushBlock' scopped by fixed value and must be only one.
    In nested fastloop event line 9 with condition 'object PushBlock overlap with group 1' I try to set alterables (value and string) before stop loop action. But they do not get the right values.
    Next nested fastloop event line 11 with condition 'object PushBlock overlap with group 0' works fine. Alterables setted and loop stopped.

    Please see example attached.

    Looks like event line 9, when overlap happen, works 1 time and loop stopped by stop loop action, counter 'StopLoopEvent' added 1 but 'PushBlock' alterables don't set.
    If I delete 'PushBlock' qualifier all works fine.
    Or if I set 'PushBlock' qualifier to 0 event line 11 stop to set alterables.

    For me, it's important that both objects have the same qualifier. Different qualifiers can not be used.

    Any suggestions? What happens with setting up alterables?
    Attached files Attached files

  2. #2
    Clicker Fusion 2.5 DeveloperAndroid Export ModuleHTML5 Export ModuleiOS Export Module
    Fusion 2.5 (Steam)
    schrodinger's Avatar
    Join Date
    Nov 2014
    Posts
    3,159
    Mentioned
    28 Post(s)
    Tagged
    1 Thread(s)
    Any particular reason you can't use two qualifiers for the black obstacle and for the falling block?

    Detecting overlap among two of the same can be done with some trickery,
    but requires i.e. using additional "intermediate" objects,
    or storing coordinates and doing math checks,
    generally these solutions are much more inelegant and cumbersome than simply using two qualifiers

    Consider you can give multiple qualifiers to an object,
    so you could give all your "black platforms" the "obstacle" qualifier
    so the rightmost one could have this in addition to the "1" qualifier
    and you would check for overlaps against the "obstacle" qualifier instead of "0" or "1"

    see modified example:

    CollisionGroup_1.mfa

  3. #3
    Clicker Fusion 2.5 (Steam)Fusion 2.5 Developer (Steam)Android Export Module (Steam)HTML5 Export Module (Steam)iOS Export Module (Steam)Universal Windows Platform Export Module (Steam)

    Join Date
    Feb 2016
    Posts
    21
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    schrodinger, thanks for the advice.

    But I wanted to understand mechanisms of fusion's work.
    I'm interested, this is a bug in the fusion or I do not fully understand the principles of scope formation?
    The point is to understand why alterables don't get the right values.

  4. #4
    Clicker Fusion 2.5 DeveloperAndroid Export ModuleHTML5 Export ModuleiOS Export Module
    Fusion 2.5 (Steam)
    schrodinger's Avatar
    Join Date
    Nov 2014
    Posts
    3,159
    Mentioned
    28 Post(s)
    Tagged
    1 Thread(s)
    I don't know if we can call it as a bug, this surely is a scoping issue,
    the overlap doesn't trigger in your eventline 9 because it doesn't know which objects to test against.

    When you check among same instances, or same qualifier, it's difficult to scope correctly,
    are you referencing one object or the other?
    And then do you want your actions to perform on an object or on the other? or both?
    So inconstistencies / logical recursion arises.

    Oddly enough, if you take your first example and change it to:



    it works.

    While "1 overlaps block"
    or "block overlaps 1"
    doesn't.

    But I wouldn't trust the picture above much.

    Perhaps "1 overlaps block" and "block overlaps 1"
    both check the scoped instance of the "pushblock" (by fixed value above)
    against any unscoped instance of "1",
    and might (casually) pick itself, thus not working (an object can't overlap itself).

    While "1 overlaps 1" *perhaps* already picks away 1A from the objects pool
    and so it's only left with 1B for the right side, picking another instance --> working.


    But honestly,
    I can't say I know what really happens in such situations,
    and always avoid those to be on the safe side

Similar Threads

  1. Replies: 36
    Last Post: 20th January 2016, 11:19 AM
  2. Problem with overlap
    By Brosephus in forum The Games Factory 2 - Technical Support
    Replies: 0
    Last Post: 10th May 2013, 08:58 PM
  3. Fastloop problem
    By Outcast in forum Multimedia Fusion 2 - Technical Support
    Replies: 18
    Last Post: 17th September 2012, 10:46 AM
  4. nested fastloop question
    By mobichan in forum Multimedia Fusion 2 - Technical Support
    Replies: 7
    Last Post: 7th May 2009, 04:21 PM
  5. fastloop problem
    By maVado in forum File Archive
    Replies: 3
    Last Post: 6th January 2008, 01:14 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •