With the recent update (beta 203.2), the bugs in the Tween behavior were supposed to have been fixed. Either there is still an unresolved issue that got overlooked or I'm dealing with a separate matter...

I'm using Tween behavior to adjust elements of the HUD map system. Each element (Quadrant, Hallway, Boss room, and Sector) share the same exact instance variables per a Family.

Depending on where in the environment the Player is, the elements of the HUD map Tween to their new size and position according to the values of their copies of the instance variables.

So the map will look something like this when in action:

When the Player moves from one area to the next, whichever area is occupied has its map counterpart expanded to its relative size of the actual area. The origin point of each HUD map element is in the top left. So, in the image above, the top-right Quadrant would Tween from its current position to a number of pixels to its left. At the same time, its size would expand at the same Tween rate that it moves. (Some objects, like the top-left Quadrant, would have the same X/Y values all the time or only part of the time depending on which area is accessed. And the same for the sizes, as well...some values will change while others will not.)

This system was working perfectly prior to the recent update. Even after the apparent Tween behavior bug fix, the problem persists. However, the ONLY thing I changed recently has been the VALUES of the instance variables. Because I reduced size of EVERYTHING - layout, objects, etc - I had to update where the HUD elements appear on the HUD layer. I also had to update the X/Y and size values that the elements Tween to. That's it.

The problem is that, when I Tween to certain areas, the size of the element will START at a value GREATER than it was at before the Tween. For example, if I'm moving from Quadrant 2 (top-right) to Quadrant 1 (top-left), the width will Tween to its correct size but its height will start out at more than double its original size prior to the Tween (and its height isn't even supposed to change!).

The max size any element will reach is 45x45 pixels. The minimum is 15x15. But I'm seeing cases where the height and/or width starts out at as much as 90. In other cases I'm seeing where it will Tween from a smaller size to its target size when it shouldn't have changed sizes at all. As per my illustration above, moving left to right will keep the top two Quadrants the same height. But the Quardant 1 element will Tween from 15 pixels to 45. But I have quadruple checked the values for the instance variables to confirm that it shouldn't be Tweening to or from anything different.

Here is the .c3p file: https://drive.google.com/file/d/11fTotgPQCiQDkq5UtETuYOpfyLBgkuI9/view?usp=sharing

CONTROLS:

- WASD to move

- MOUSE to move the targeting reticule (make sure it's around the middle of the screen

In the project window, look for the HUD_Elements Family to find the variables being referenced here.

The event lines are on the "E Gameplay" event sheet and are at event lines 218-230.

That agrees with what I seem to have discovered, too... Except when I had removed the behavior from the individual objects alone. Maybe I missed one. Ah well. It's working now.

UPDATE: I don't know what the issue was, but after going back to what I initially had with the objects in the Family, deleting all actions referring to the behaviors for the individual objects, and then also deleting the behaviors assigned to each object, AND THEN adding the same behaviors to the FAMILY...it all seems to work. I don't understand the conflict as I've been able to add the same behavior to an object AND to the Family the object is a part of and it just said "Behavior2" when I did that.

Ashley, are you and your team aware of this?

I'm just not sure why this is an issue when I've been able to add behaviors to Families even when the individual objects, themselves, already had the same behavior.

Before I go and post this as a potential bug, I wanted to ask if anyone else has noticed the inability to add the Tween behavior to a Family of sprites.

Initially, the individual sprites, themselves, had the Tween behavior. I know that you can add the same behavior to the Family and it'll be something like "Behavior2" because of the existing Behavior to the objects that make up the Family.

But after adding these objects to their Family, I found that the Tween behavior wasn't in the list of options for the Family, itself. All other applicable behaviors were, however.

I tried removing the Tween behavior from the individual objects of the Family, deleting this Family and then creating an entirely new Family with the same sprites I'm working with. Even with the Tween behavior not existing in the sprites with this new Family, I still could not add the Tween behavior to the Family, itself.

Am I missing something or are others experiencing the same thing?

Yeah, I did that but I couldn't find how to retrieve that info when I hit F12.

Well, I tried the Log Console deal and I couldn't find ANYTHING related to the log.

But you were partially right - it was related to a variable issue. I re-worked it a bit and now it's all good.

Well THAT is something I wasn't aware of. That makes a whole lot more sense... *testing* ...and, well, it doesn't set the layer scale to 0. Now it just doesn't adjust the scale at all.

I made a couple adjustments, including the one you suggested, but what I get is that the scale variable I use to track the Tween value still reads as 1 (the starting value).

I discovered that, having set the Value of the Tween to the ShakeTheGround variable, the Tween goes from 1 to 0 even though I set the end value as 0.5. The Tween is completely bypassing the end value.

I've reviewed the Tween behavior page in the Documentation and everything I'm doing seems to check out. So I don't understand why it goes from 1 to 0 and not 1 to 0.5 as I had set it.

Okay, I did that...hit F12 and selected the Console tab. But I don't see anything relevant. I checked through the other tabs, too, and didn't see where I could find the info that's supposed to be logged.

What I'm attempting to do is use Z-Elevation to make an object appear to leap up above the layout and slam back down into the ground. THAT MUCH WORKS.

The immediate effect following the object slamming into the ground is to make the layout scale down in size then "spring" back to its original zoom setting. The object hits with such a "force" that the effect is that it pushes the environment down away from the camera just a bit.

The first half of this - "pushing" the ground away from the camera - which is to scale the layer smaller isn't working. I can't get it to progressively show the layer getting smaller. Instead, it appears as 0. Like it's not there. However, obviously, the Player object still moves around normally...just invisible.

I've run some tests and I can set the layer to 0.5 through a separate action line. So it seems to be the way I'm trying to use the Tween that is the problem. Can someone help?

Ashley - Oooh okay. So my illustration of taping two pieces of paper together were accurate. Understood. Thank you. :)