HUD Text in the Asset Store

[ArenMook]

The disabling of the HUD when it's off-screen should be your game code. Ideally you will want to have a root object that will do this, and this root object will have children, among which is your unit's health bar, any and all on-screen elements (such as Unit's name), and of course -- HUDText. This script will be enabling/disabling only children, leaving itself enabled at all times (otherwise it won't be able to re-enable itself after it gets disabled). This object will also have the UIFollowTarget script on it.

P.S. I'll add this in though, controlled by a boolean flag.

[ArenMook]

http://www.youtube.com/watch?v=diql3UP1KQM

I forgot to boost the volume. Too quiet?

[JRoch]

It's a little quiet, yes.

Also, I had to mod UIFollowTarget with the following:

1.                         pos = transform.localPosition;
2.                         pos.x = Mathf.FloorToInt(pos.x);
3.             pos.y = Mathf.FloorToInt(pos.y);
4.                         pos.z = 0f;
5.                         transform.localPosition = pos;
6.  

This is to prevent the HUD item from jittering if the target object is sweeping through space with the camera rigidly attached.  Little rounding errors of the transform position make the calculated center bounce around +/- 1 pixel if using mathf.round().  Using FloorToInt or CeilToInt prevents that behavior.

[catacomber]

Thank you for the video tutorial-----a little louder would be good. But I was able to follow.   :  )  I was out without my computer today. Only just got a chance to watch it and download the updated HUD Text.

[ArenMook]

Ok I will change it to be "FloorToInt" in the next update, thanks.

[JRoch]

EDIT:  Okay, I definitely need to get a better understanding of the coordinate system translations that are taking place, because the changes below definitely have some wonky behavior.  Ignore for now.


Aren, a bit of a correction, as just using Ceil or Floor doesn't fix it completely.  This does:

1.             // prevent jitter by only moving the object if it's more than one pixel
2.             if (Mathf.Abs(transform.localPosition.x - pos.x) > 1.5f || Mathf.Abs(transform.localPosition.y - pos.y) > 1.5f)
3.             {
4.  
5.                             transform.position = _mUiCamera.ViewportToWorldPoint(pos);
6.                             pos = transform.localPosition;
7.                             pos.x = Mathf.CeilToInt(pos.x);
8.                 pos.y = Mathf.CeilToInt(pos.y);
9.                             pos.z = 0f;
10.                 transform.localPosition = pos;
11.  
12.             }
13.  

It's essentially making sure the delta in pixels in either the X or Y direction is more than one pixel, so that it doesn't jitter.  Might need a little more fine tuning.

[JRoch]

Alright, I think I understand the logic here.  Jumping the camera around was causing the UIFollowTarget script to act weird with the earlier mods because of the Z value not being compared.  Here's what I came up with:

Note:  _lastZPosition is a private float used to track changes in Z between cycles and determine if a significant change requires recalculating the position of the follow.

1.             // prevent jitter by only moving the object if it's more than one pixel
2.             if (Mathf.Abs(transform.localPosition.x - pos.x) > 1.5f || Mathf.Abs(transform.localPosition.y - pos.y) > 1.5f || Mathf.Abs(_lastZPosition - pos.z) > 1.5f)
3.             {
4.                 _lastZPosition = pos.z;
5.                             transform.position = _mUiCamera.ViewportToWorldPoint(pos);
6.                             pos = transform.localPosition;
7.                             pos.x = Mathf.CeilToInt(pos.x);
8.                 pos.y = Mathf.CeilToInt(pos.y);
9.                             pos.z = 0f;
10.                 transform.localPosition = pos;
11.  
12.             }
13.