[Faerdan]

Thanks Blaze. 🙂

[Faerdan]

Hi all,

We’re at a point in the project now were I can, and am, posting regular development progress updates on our forum. You can follow the progress on the Engineering UI, which I am currently implementing in-game, and give your feedback and suggestions for it.

Here’s the Power Wheel as of today’s update:

If you every wanted to help shape a bridge sim, which is being built for you, this is your opportunity. I would love to hear and discuss your feedback and suggestions.

Thanks!

Mark

• This reply was modified 8 years, 2 months ago by Faerdan.

[Faerdan]

Hey all,

Here is our first in a series of bi-weekly video DevLogs: https://www.youtube.com/watch?v=6NB2bd_pLU0

We discuss some of UNION’s history, and demonstrate the Power Wheel.

Thanks!

[Faerdan]

My pleasure. We haven’t had a chance to build up a community around UNION yet, so I don’t get to chat about it with others very often.

We’re starting to work on that now though, our forums should be live later tonight, along with our first video devlog.

If you’d like to ask any more questions, I’d be happy to answer them.

[Faerdan]

Hey Blaze,

Thanks for the excellent feedback, all of your points are spot on.

After Engineering I am redesigning a lot of the Tactical screen as I feel like it just became too busy. I will take your points into consideration when doing that.

Text alone isn’t clickable on the UI, everything clickable is a shape of some sort. I leave enough room between these clickable elements to allow for touch based control.

You were right, the “Forward Left Turrets” was a typo. Turrets do need to be recharged if you have power them down.

I’ve already begun work on highlighting valid nodes when you start dragging a connection. There is going to be way more feedback added to the UI over the next week, with animations when things happen, like when equipment is used (it’s icon pulses yellow) or when it takes damage (it’s background pulses red).

I really like the idea of using the keyboard and scrollwheel to adjust the power while dragging, that is totally in. You will be able to click on already-created connections and adjust their power using arrows (and how using scrollwheel or the keyboard also).

I currently intend for the position of the reactors and equipment to be fixed, however there will be a number of variants to choose from for each ship, to suit your play style (more/less power available to particular systems etc.).

Each equipment section on the power wheel is actually an equipment slot. Each slot has a type (turret, engine, sensors, shield etc.) and a class (which designates the power requirement of the equipment).

Each piece of equipment has it’s own performance graph, and can have different behaviours. Like directed energy vs ballistic turrets.

In early releases you will have a selection of equipment to install on your ship before a mission, however we have detailed plan for a persistent dynamic campaign, where you will purchase equipment at stations, salvage them from wrecks, and get them from missions. These equipment will be generated procedurally.

Clicking on equipment will give you a detailed view of it on the top left of the screen, including the graph. The graph picture above is actually a graph from the game (albeit an earlier test version).

Good call on the operational heat (dark red) being hard to see, I will experiment with the colours.

On the subject of maps, ours will support a maximum size of just over over 17 billion x 17 billion kilometres (using a chunk system, similar to Minecraft’s).

Early versions of the game will have single missions, set in it’s own map, which you can load and play. The size of the map will be up to the mission creator.

As I said above we have plans for a dynamic campaign map, with procedurally generated missions and events, where the gameplay is much more like Elite.

I hope I have covered everything, and thanks again for the response.

Mark

[Faerdan]

Hi all,

I know I’ve been very quiet these past few months, but only because I’ve been neck deep in UNION development.

I’ve been working on the simulation systems for the game which, in combination with them being fully networked, are rather complex.

I’ve also implemented a vector-based XML (XAML) UI system, which will allow modders to make significant alterations to the UI. In most cases you could recreate a whole UI from scrath, turning it into something like LCARS.

Anyway, I’m here today to talk about Engineering and power management. I have huge respect for you guys, and I would love to get your input on it.

This video shows the working “Power Wheel”, where you drag connections from “reactor nodes” to “equipment nodes” to power them: https://www.youtube.com/watch?v=-Qz3DoYp_9Y&feature=youtu.be

Please note: This is still a work in progress. For example, in the final version you won’t have to drag and drop every time you want to increase/decrease power across a connection, and there are many animations to go in to increase feedback. On a whole though it is fully functional. It is also not the full UI, but just the power wheel portion of it.

The Power Wheel
The main element of the power wheel is creating connections from “reactor nodes” to “equipment nodes”, increasing and decreasing power to equipment.

Each reactor node has a maximum output, on the ship in the video above they all have a max output of 9.

Each piece of equipment has a section on the power wheel, it’s position on the wheel representing it’s position on the ship.

Power connections can only be created between reactor and equipment nodes which have line-of-sight. If a line between them intersects another node or the central circle, it is an invalid connection.

Each piece of equipment has a minimum and maximum “operating power level”. The current operating power level, the amount of power being provided to a piece of equipment, is displayed on the equipment section as a bar of rectangular pips. The first few pips are orange, these represent the power levels below the minimum. Blue pips represent power above minimum. If a piece of equipment is below minimum power, it’s node will change to orange to show that it has not enough power to operate. The equipment node changes to a light yellow when it is at max power.

Increasing the operating power level increases the performance each piece of equipment based on it’s “performance graph”. This allows us to create equipment with it’s own character. In the example pic above, which is for a turret, 17 operation power would get you about 40 damage, whereas just 1 more power would get you 50. We will use this to create things like weapons which have a decent lower power performance, but with no high potential, and weapons which have poor lower power performance, but a large amount of high power damage.

Increasing the operating power level increases the amount of heat generated when the equipment is in-use/used. This heat goes into the equipment’s heatsink. If the heat goes over the heatsink’s capacity, the integrity (health) of the equipment is damaged. Heat is represented by the equipment’s red bar on the power wheel. Bright red is the current heat, and dark red represents the amount of heat that will be generated on next use. If the dark red section goes over the heatsink capacity it shows up on the green integrity bar, showing how much damage that excess heat would cause. Heat is dispersed from heatsinks at a constant rate.

Integrity, represented by the green bar, can be damaged by enemy fire or overheating. Damage to equipment reduces the heatsink’s ability to disperse heat, up to 50% when fully damaged.

When providing power to equipment it is advisable to split the power over multiple connections (from multiple reactor nodes) as this is much more stable. When equipment is hit with enemy fire there is a chance that it will be a “critical hit”, causing an explosion in the equipment. This explosion has a chance of creating an “overload” which travels along power connections to the reactor and potentially out to other equipment, causing temporary loss of function and/or damage. The overload chance is based on the current operating power level of the equipment, but is decreased by providing that power from more than one source (more is better).

Sensors in UNION are based on “energy signatures”. The higher a ship’s (or station’s) energy signature is, the easier it is to detect and the more accurate weapon locks are. Heat is the primary contributor to a ship’s energy signature, though things like active shields and active long range sensor scans can increase an energy signature dramatically. Heat is generated by the reactor nodes, based on their power output, and when equipment is in-use/used.

Sensor strength is based on the sensor equipment stats, and the sensor’s operating power level. Sensor strength decreases with distance, so closing on a target is a good way to get a stronger lock. Stronger sensor locks provide not just more accurate weapon accuracy, but also more detailed information on the ship.

A ship or station below sensor strength will be completely invisible unless within visual range (which is quite close). Ships/stations within visual range but below sensor strength will show up as unknown contacts and cannot be sensor locked.

I think that’s everything for now, I would love to hear your opinions and suggestions.

Thanks,

Mark

• This reply was modified 8 years, 3 months ago by Faerdan.

[Faerdan]

Excellent point ‘re the status being too subtle, I will play around the the colours and see.

Thanks!

[Faerdan]

Nice mockup, thanks Fulvus!

I’m off to bed now but I will implement your change in the morning and see what people think.

[Faerdan]

Ah the alpha release will be a closed release, a public beta release would be in early 2016. I’m not sure if we will do Early Access or not, it really depends on our finances (if we really need the money) and the state of the game (if it’s feature complete).

On each turret the white bar is the current charge. When it is full the turret can fire.

The problem you are thinking about with nodes, while interesting, does not exist. Engineering sets how much power each node gets. So lets say the “Forward Left Thrusters” power node is getting 3 MW of power per second. If both turrets, T1 and T2, are active they will each get 1.5 MW per second. If however the tactical officer disables T1 then T2 will be getting the full 3 MW per second.

Here is an older picture of Engineering:http://images.akamai.steamusercontent.com/ugc/630852732951665789/B208443B3277EE930B3F60816EE2B617A1604788/
In that picture each of the four turret/weapons nodes (the nodes with the three bullets icon) is getting 3 MW per second.

Science/Comms isn’t ready to show yet, but as soon as it is I will post here.

I know it’s difficult to give good feedback with just these static images, but what you can give is very helpful to me.

Thanks!

[Faerdan]

Thanks Cpt. Gomric.

I am genuinely looking forward to playing with you guys.

Right now I am designing the UIs, they will then need to be built within the game itself. It will be later this year, maybe November, before there is an alpha ready to play.

[Faerdan]

Hey all,

I’m sorry I wasn’t able to join you last night, things are very busy at the moment. We will be meeting with a number publishers after Gamescom, to see if they are interested in us and if we are interested in what they have to offer, and we’re busy working on content for that. I do hope to play with you at some stage though.

The Tactical UI is not yet complete, but I have made a good deal of progress on it. I would love to get your impressions: http://i.imgur.com/CfFiMa4.png

Have a look at it before the description below, and see if your first impressions line up with that. Thanks!

Targets (bottom right of the pic):
Each ship has a set number of target slots, in this case it is three. Each has to button on the bottom right of the screen. Target slots are lettered alphabetically.

When a slot is empty (a filled slot can be cleared by clicking on the “X” to the left of the button) clicking on it will ask you to select a contact, from the radar or list, to target.

Once a slot has been filled, clicking on it’s button opens a popup showing whatever information is available on that target. Depending on the scan strength this could range from the type of ship/structure, to the heat and structural integrity of each of it’s systems. If you have information on it’s systems then you can select one of these as a sub-target.

Turrets (top left of the pic):
Turrets are split into Firing Groups, these FG can be configured by the tactical officer.

Clicking on a firing group will allow you to set it’s target (A, B, C etc.) and whether it is in Auto or Manual mode. In Auto mode the Firing Group will fire it’s turrets as soon as one or more of them is “ready”. “Ready” means that the turret is charged and has a the target in sight. In Manual mode the Firing Group will change to a “FIRE” state, clicking on the “FIRE” part of the button will then fire any of it’s “ready” turrets.

To the left of the firing group is the list of turrets on the ship, grouped by the power nodes they are connected to. Turrets connected to a power node (like “Forward Left Thrusters”) share the power going to that node (in this case “Forward Left Thrusters” has two turrets, so each is getting 50% of the power for charging). Clicking on a turret in the list disables it, stopping it from drawing power and causing the other turrets connected to that node to charge faster (in the pic above, disabling turret “T2” will cause turret “T1” to charge 100% faster).

Radar (center right of the pic):
Lastly there is a radar range setting on the bottom of the radar, which allows you to set the radar to a shorter range (effectively zooming in).

That’s it for now, I would love to hear your feedback.

Thanks!

[Faerdan]

Ah ok.

I think filtering the radar and contacts list separately is an advanced feature which I don’t expect many people to use. That’s not to say I won’t implement it, I just have to think about how I can do it without confusing beginners… One way I could potentially do it is a toggle. There would be one list of filters, but you could choose to filter Radar, List, or Both.

Control/keyboard config will definitely be in-game. There will also be control profiles, so you can have a number of different configurations.

Thanks!

[Faerdan]

We have been considering adding input to the Captain’s screen, but haven’t settled on an answer yet.

Either way we will be providing plenty of information to the Captain so that he/she can direct the crew. We will experiment with bearing too, I’m just not sure how useful they will be (yet).

[Faerdan]

It’s my pleasure.

I post a pic again when the UI is much more complete, this has been very useful.

[Faerdan]

And just for people who would like to know the development process behind these UIs.

I draw them as static versions first, as you see in the progress picture. Then I add animations for each element which requires it. Once that is done each element is packed into a texture atlas, and I rebuild the UI in-engine with code. They end up looking pretty much exactly as they are in the mockup.

Thanks for all of your feedback,

Mark

[Author]

Posts