playMaker

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Zombeh

Pages: [1]
1
PlayMaker Help / Re: Array Get Next issue
« on: September 18, 2019, 04:40:11 AM »
Well no idea what the issue was with that previous version, but I made a new more in-depth one that works without trying to rely on Array Get Next to set the bool.

Thanks for the help!

2
PlayMaker Help / Re: Array Get Next issue
« on: September 18, 2019, 03:23:11 AM »
Here's a compilation picture with all the states involved.  Might be a bit hard to read the transitions since Imgur didn't seem to like it's size or something.  I also cut the "blufor" section of the Array Get Next out of the main loop to test, since the "opfor" currently always ends up as the element 0, so I can easily see that it's not resetting from element 1 (only 2 elements in this scene currently), and thus not reflagging the opfor boolean as true.

You'll also see that it says reset flag isn't marked, that's just because I forgot to swap it back on for the screen shots, while I was testing bool reset states in different parts of the FSM.  No matter where I've reset, or even without having reset on, it all seems to work exactly the same.  One run works fine, but second time around it never resets.

Here's the new link:

https://imgur.com/9PhaIVy

3
PlayMaker Help / Array Get Next issue[SOLVED]
« on: September 18, 2019, 01:53:13 AM »
I've been having some issues with Array Get Next.  In the context of this image, I've got another FSM that updates the units inside a trigger to an array using an "on enter/exit".  This FSM then gets the info from that array and is supposed to check the units in it against 2 other arrays (blufor and opfor) to get a true/false as to whether those units are inside the trigger.  If blufor is detected it ticks down an HP bar per second, if both are detected it is supposed to just basically loop every second until they aren't.

Now as far as I can tell, everything within the whole FSM works properly.  The main array is updated properly, the 2 arrays to check against are populated.  Even the first full check sequence seems to work properly, properly tagging both the blufor and opfor objects as being present.  The second go around one second later seems to be the issue, where the result variable within both of the Array Get Nexts stays on the second element in the array.  I'd read up that this was an issue with needing to use the reset flag, but it seems to have no effect.  That include both the regular Array Get Next and Array Get Next 2, with reset flags properly swapping to true.

I feel like I'm missing something simple, but does anyone have any ideas on what could be the issue?

Thanks!  Here's a link to the image of the Playmaker window.  Don't mind the transition naming, unless that somehow is the problem.

https://imgur.com/3wTSBtM

Pages: [1]