SHIP EQUIPMENT / VISUAL FIELD GUIDE
Power plants: read supply before changing allocation
Separate generated power, system minimums and ship pool limits, then rehearse one reversible change.
01
STEP 1 OF 6
Separate the generator from the power you assign
The named examples are extracted community game-data records for 4.10.2-LIVE.12881860, captured 15 October 2026. Their parameters are references, not measured ship performance. These exercises have not been gameplay tested. Matching size does not establish fitment, access or a better loadout.
A power plant supplies power to the ship’s resource network. The MFD or engineering console distributes available power. Giving a weapon another allocation segment is not the same as increasing the plant’s generation.
What do these words mean?
- Captured example
- The size-1 JS-300 records 17 generated power segments; size-1 Fortitude records 15. These are resource-network parameters, not megawatts or a promise of 17 or 15 assignable weapon segments.
- Minimum and pool
- A system may need a minimum allocation to operate. Weapons, shields and thrusters can have ship-specific pool limits. More source generation does not remove a pool limit.
JS-300Fortitude
Read the complete guide as text
The same published instructions in one readable view. Use the steps above for controls and practice panels.
Separate the generator from the power you assign
The named examples are extracted community game-data records for 4.10.2-LIVE.12881860, captured 15 October 2026. Their parameters are references, not measured ship performance. These exercises have not been gameplay tested. Matching size does not establish fitment, access or a better loadout.
A power plant supplies power to the ship’s resource network. The MFD or engineering console distributes available power. Giving a weapon another allocation segment is not the same as increasing the plant’s generation.
- Captured example
- The size-1 JS-300 records 17 generated power segments; size-1 Fortitude records 15. These are resource-network parameters, not megawatts or a promise of 17 or 15 assignable weapon segments.
- Minimum and pool
- A system may need a minimum allocation to operate. Weapons, shields and thrusters can have ship-specific pool limits. More source generation does not remove a pool limit.
Find the real display and make a healthy baseline
Shared control cards use the site’s inspected 4.9 LIVE defaults compared with 4.10 PTU. Each card keeps its own dated source; they are not newly verified 4.10.2 bindings. Your saved input takes precedence: Options > Keybindings > your device > Advanced Controls Customization. Improve an inaccurate control through this article’s normal edit and independent review workflow.
Park safely. Identify the installed plant, its health or warning state and the power display available from your station. A small hull may use MFDs; a larger ship may expose an engineering console elsewhere. Do not leave a moving ship’s pilot seat to find a console.
Make a baseline before launch
SC Nomads comparison drill
Record your ship variant, fitted weapons, visible power allocations and healthy status. Keep the same view available for the next practice step.
Expected result: You have a reference to compare with a failure.
If it did not work: Do this while parked. If the screen is unfamiliar, ask the owner to identify one known component before changing anything.
Walk the ship before taking a job
Ask the owner to show the engineering console, accessible components, relays, repair supplies and exit routes. Interact with the console while the ship is safely stationary.
Expected result: You can reach the equipment you are expected to service without asking for directions during an emergency.
If it did not work: If a component is not physically accessible, plan around that limitation. A console diagram is not a doorway.
- Ship stationary
- Plant name and condition recorded
- Available power view identified
- Pilot agrees to the drill
Change one offered compatible item, or keep the reference exercise
A size-1 example is not a shopping or compatibility recommendation. While safely stored, record every installed plant or cooler and keep the original available. Multiple installed units and the ship’s own limits remain part of the result.
JS-300 and Fortitude are a same-size reference pair. Only attempt a physical comparison if the actual Vehicle Manager offers the intended part in this ship. A missing option does not establish a game bug, and the website does not fit or buy anything.
Customize the local stored ship
mobiGlas > Vehicle Manager
At the location holding the ship and parts, open Vehicle Manager, select the stored ship and its intended slot, then inspect the offered compatible items. Apply the intended customization and recheck the slot.
Expected result: The intended component is fitted to the intended ship.
If it did not work: Check location, slot size and available item before replacing anything else. Do not assume a more expensive part fits.
- Exact ship and original item recorded
- Current interface offers the intended replacement
- One item changed, other settings retained
- Original remains available
Change one allocation and name what actually changed
Read the current weapon allocation and any minimum or unavailable indication first. Tap the shared increase input once while stationary, then compare the same display. Watch whether another system lost an allocation.
A changed allocation is the result you are checking. No visible change is also useful: record the mode, occupied station and current limit. Do not keep pressing until a needed system loses power. This drill does not measure generated power, weapon damage or plant efficiency.
Increase weapon allocation one step
Flight - Power > Weapons - Increase. Latest inspected CIG default: 4.9 LIVE, compared with 4.10 PTU. Your saved input may differ.
While safely stationary, note the weapon allocation, tap once and compare the display.
Expected result: You can identify the changed allocation.
If it did not work: If nothing changes, stop and inspect mode, pool limits and current inputs. Do not mash the key.
Field note: An extra segment in the source plant record is not a measured extra segment in this ship’s weapon pool.
Distinguish low allocation, a pool limit and a real fault
A grey weapon can be a pool-capacity problem rather than a broken power plant. A damaged component, relay or missing supply needs diagnosis at its actual location; reallocating repeatedly is not a repair.
Name the affected system, current mode, last change and exact warning. Stop the drill if health drops, a fire appears or essential systems become unavailable. Use the repair/fire lesson and a safe service plan rather than deliberately switching off the last working plant.
Read a problem in the Rooms view
Open the console's Rooms view. Locate the damaged or unhealthy area and compare it with your physical position. Tell the pilot which system or room is affected.
Expected result: Your report names a place and condition rather than only saying the ship is broken.
If it did not work: If the display is unfamiliar, identify one known room first. Avoid changing every system while trying to discover what the colors mean.
Change one setting and observe it
With the pilot's agreement, inspect Config or the available power presets. Change only the setting needed for the current problem and watch the resulting power or temperature state.
Expected result: The intended system improves without silently removing power from something the crew needs.
If it did not work: If another system becomes unavailable, report it and restore the prior setting before attempting another change.
Assign diagnosis and hands-on work separately
Read the console, name the failing component or relay, then send an engineer with the appropriate tool or spare. Tell the pilot when you leave a station unattended.
Expected result: The person doing the repair knows the target, access route and intended result.
If it did not work: Do not send two people to change unrelated settings without coordination. Recheck the console after each intervention.
The extra plant generation did not make every weapon available.: Compare the ship’s weapon pool, weapon requirements, allocation and mode. The extracted plant number is not a simulation of this fitting.
The display is somewhere other than the cockpit.: Use the hull’s available MFD or agree a separate engineer. Plan physical access before leaving a station; a component diagram is not a walkable route.
Restore the baseline before deliberately keeping a configuration
Compare your observation with the original question: which displayed system changed, and which did not? Keep the result specific to the tested ship, fitted units, mode and allocation. Neither the source grade nor the larger generation number makes a universal winner.
Reset Assignments changes allocations, not fitted hardware or damage. Refit the recorded original through the same Vehicle Manager flow if reverting. Inspect the final slot and visible system state before departure.
Saving at ASOP is optional and replaces the previous snapshot. Save only the configuration you deliberately intend to keep, after confirming it works. An insured snapshot does not stock ammunition or prove the ship is repaired.
Restore the assigned baseline
Flight - Power > Reset Assignments. Latest inspected CIG default: 4.9 LIVE, compared with 4.10 PTU. Your saved input may differ.
Use Reset Assignments after the experiment, then compare against your recorded state.
Expected result: You can tell whether reset restored the expected allocation.
If it did not work: Reset is not a repair, and it is not proof that a custom crew preset was restored. Report any remaining difference.
Save the retrieved configuration
ASOP > retrieved ship > save icon
After retrieving and checking the configured ship, use the ASOP save icon. Inspect its confirmation. A new snapshot replaces the previous one.
Expected result: The intended configuration is the saved snapshot.
If it did not work: A later insured claim excludes ammunition and missiles. Plan a separate rearm; do not treat an insured ship as automatically stocked.
- Allocation and fitted item checked separately
- Unexplained warning recorded or serviced
- No experimental snapshot saved accidentally
Sources & guide information
4.10.2 extracted examples; dated CIG engineering sources. Not gameplay tested.. Reference information, not a claim of current-patch playtesting.
CIG Engineering Gameplay Guide, includes 4.8 availabilityCIG Set up keybindings for your peripherals, updated 17 February 2026; checked 16 October 2026JS-300: exact extracted 4.10.2-LIVE.12881860 record, captured 15 October 2026Fortitude: exact extracted 4.10.2-LIVE.12881860 record, captured 15 October 2026JS-300 reference image: Weehamster, CC BY-SA 4.0CC BY-SA 4.0 reuse termsCIG Alpha 4.8: ASOP loadout recovery and Vehicle Manager changes; checked 14 Oct 2026CIG input data via Subliminal: 4.9 LIVE cl12248363; 4.10 PTU comparison, 22 Aug 2026