Module priority control: Difference between revisions

m →Example: wording
Line 17: Line 17:
== Example ==
== Example ==


The following is an example of a complete bounty hunter loadout for the [[Vulture]] which, were it not for the module priority control employed as showcased below, would render the ship inoperational due to excessive power draw.
The following table details a rather greedy [[Bounty Hunter|bounty hunter]] loadout for the [[Vulture]], comparing the power usage between two states, deployed and retracted hardpoints.
 
Were it not for the module priority control employed and as showcased below (module priority = 5), this particular loadout would render the ship entirely inoperational due to excessive power draw (power usage greater than 100%).


{| class="article-table" style="text-align: center; font-size: 88%; line-height: 1.3em;" border="1"
{| class="article-table" style="text-align: center; font-size: 88%; line-height: 1.3em;" border="1"
! colspan="3" |  
! colspan="3" style="text-align: center;" | Vulture
! colspan="2" style="text-align: center;" | Power (MW)
! colspan="2" style="text-align: center;" | Power (MW)
|-
|-
Line 139: Line 141:
! style="text-align: center" | 15.35 (99%)
! style="text-align: center" | 15.35 (99%)
|}
|}
As soon as hardpoints get deployed the components with module priority 5 get disabled automatically. The ship's power draw is thus kept within the limits and the ship is prevented from shutting down.


== Notes ==
== Notes ==


* Irrespective of whether module priority control is applied correctly, the player will still receive the mandatory cockpit warning when hardpoints are getting deployed that the power limit was exceeded and modules have been disabled.
* Irrespective of whether module priority control is applied correctly, the player will still receive the mandatory cockpit warning when hardpoints are getting deployed that the power limit was exceeded and modules have been disabled.