Basic UI design

[SharktasticA]

We'll eventually need some basic UI for reading out statistics such as:

• velocity
• acceleration
• current gravitational pull on the player (mainly for debugging purposes during development)

In time, we might want to add features such as a minimap, angle bearing to objects, in-game time etc. For the mean time, just the three basic statistics will help development. There is no current rush for this right now though, and we'll likely need to continue teaching ourselves on how to implement these features.

[ThallasTV]

A GUI link for future reference https://www.youtube.com/watch?v=kp4SyYHAwcA Health bar system for Planets, enemies & Asteroids https://www.youtube.com/watch?v=5zNDRMJ3_AA Speed indicator https://www.youtube.com/watch?v=7OE9GX8rls0 Damage popup text https://www.youtube.com/watch?v=fbUOG7f3jq8 Health bar above objects with floating damage text https://www.youtube.com/watch?v=bFLtH05SO4M Text on screen, can help with main menu https://www.youtube.com/watch?v=Mzt1rEEdeOI

[SharktasticA]

Could we have an update on the Friday tutorial by any chance?

[ThallasTV]

Decided to import my previous tutorial health bar system, would all of you like a numerical figure for the health/population of the planets?

[SharktasticA]

Whilst personally I do not mind what you chose, a relative percentage would be my pick.

[ThallasTV]

I have made a few updates to the UI of the game.

• Health bar above the planet with placeholder values and script.

• Health bar of the players health which is vertical.

• An indicator for fuel. A concept i thought about is giving the player a limit on how much fuel they have for their ship/probe, a feature that can be easily removed if unnecessary.

• I will be adding a speedometer when i acquire the movement system.

• Floating damage text will be added soon, I will test this with the placeholder code that is on the planet at the moment (Health decrements by 5 when the left mouse button is clicked).

• Damage alert seems fairly simple to include, i will add it depending on how necessary it is for the game.

[SharktasticA]

Nice progress!

In light of the gravity and model changes, the relative size of objects such as planets will be scalled down immensely since it is a necessity for the movement system. Can your health bar be scaled down if needed?

[ThallasTV]

https://www.youtube.com/watch?v=4fYd6-RFp_M - future reference

[SharktasticA]

So for your various UI elements, an API now exists for you to start getting the needed information thanks to the GeneralVariables and ProbeVariables API (PlanetVariables coming soon). You can refer to this for information on how to get access to the information: https://github.com/PlaceholderGames/Team1-2017/wiki/Accessing-variable-classes

ProbeVariables inherits from GeneralVariables, so ProbeVariable has all of GeneralVariables public API as well as it's own.

Relevant interface:

• Health bar - float variable GeneralVariables.Health
• Fuel bar - float method ProbeVariables.GetFuel()
• Speedometer - float method ProbeVariables.GetSpeed()
• Material count - int method ProbeVariables.GetMaterialCount()

[ThallasTV]

https://www.youtube.com/watch?v=TMzXG1u3XAE - Another reference for the health etc

[SharktasticA]

Copy of the UI layout prototype for everyone to see: ![Uploading 27746283_691837204357106_1038420073_o(1).jpg…]()

[ThallasTV]

Decided I will try and utilize UNITFRAMES. I feel it fits better with the style of the game rather than the Diablo style resource hud. Video for what i will be referencing: https://www.youtube.com/watch?v=lcYDf70nDHo

[SharktasticA]

Due to some changes, Variable classes are now Object classes, but are accessed the same way (just a name change). So if you were using ProbeVariables, you'd just change that to ProbeObject. The methods are exactly the same, but the change was due to merging of multiple scripts. All changes are on Physics branch right now. https://github.com/PlaceholderGames/Team1-2017/wiki/Accessing-object-classes

We're also going to need another stat displayed on screen too; Munitions. It can be accessed with GetMunitionsCount(). Its needed for the firing system and basically displays your ammo (max will be about 100).

[ThallasTV]

New .ZIP file has been created due to recent issues with branches.

-Unit Frames or each object/model that will be displayed via Mouse Click. -State health of objects/models within the Unit Frames. -Displaying the current Coordinates of the Player (X,Y,Z Coordinates). -Possible Speedometer and Fuel changes (Visual changes, current & max speed, starting fuel amount). -Could implement a Fortnite inspired "Radar" that could possibly display the X coordinate of which way the ship is facing. -Floating Damage Numbers when the player shoots objects. -Display how much ammo the ship has. -When Ammo <0, state the ship is reloading and refresh the ammo counter. -Possibly specify tasks that should be completed by the player. -Possible Minimap?

These should all be implemented.

[SharktasticA]

Closed since a new thread of the subject exists.