First Major QoL Improvement

It's taken me a while, but I figured it out.. I know what the first major QoL improvement needs to be:


When selecting a cockpit mode, either Combat or Analysis, we need to only be able to select fire groups that are Combat-related when in Combat mode, and Analysis-related when in Analysis mode.

This reduces the number of groups we have to cycle through in any given mode. As it stands right now we have to cycle through all of them. If the group selection is set in such a way that only those groups containing matching equipment are cycle-able then this resolves this.

For Example:

Fire Group 1 contains a pair of beam lasers and a multi-cannon (combat).

Fire Group 2 contains the Discovery Scanner and Detailed Surface Scanner (Analysis).

Fire Group 3 contains the Data Link Scanner and Composition Scanner (Analysis)

Fire Group 4 contains Beam Lasers and a Repair Limpet Controller (Mixed)

When cycling groups in Combat Mode only Groups 1 and 4 cycle. When cycling in Analysis Mode, groups 2, 3 and 4 cycle.

Thoughts?
 
Yes, I find more than two fire groups to be a problem. Four or even five to cycle through is far too much. Your proposition would help.
 
This was actually suggested during the first days of beta and the thread was in front page for the entire month. I'd like to get an official response to this, especially since it's such a no brainer.
 
It has been already proposed to FD during beta. No replies or changes.

Yep, this was loudly discussed during beta. Nada response from FDev on this.

Along with multiple HUD modes, each Firegroup needs to be assigned to a mode. And you can only assign weapons/tools to a Firegroup if it's allowed to be used in that mode. Some items should be usable in multiple modes, most would only be usable in a single mode.
 
My thoughts are: this was suggested and discussed to much agreement during the beta, and entirely ignored by Frontier.
 
I love the idea!


Well actually "BETA" generally means feature locked and meant to be a debug/adjustment phase before release.

Well yes... but the feedback on it overwhelmingly wanted OP's idea (or similar) implemented for live release. So why wasn't it (?), given that the whole point of beta is to...
 
I love the idea!


Well actually "BETA" generally means feature locked and meant to be a debug/adjustment phase before release.

lNUh0uV.gif


( Though, an acknowledgement from Frontier would have been appreciated )
 
Back
Top Bottom