Practise Rooms, Config and a safe power readback
A docked crew drill through the named console views, one allocation and its restoration.
A docked crew drill through the named console views, one allocation and its restoration.
Authored practice, source review 20 October 2026 against the 4.10.2 reference baseline. Not an in-game tested route, combat result or promise of a working system on every hull. Follow the live HUD and current issue notices.
Source foundation: the engineering console and MFDs expose power distribution; components have health, temperature and power demand. A shield generator supplies shielding. Room and system readouts serve different diagnosis tasks. Do not turn these into a universal combat preset or fixed percentage.
Our docked crew exercise: the pilot can stop the drill immediately. The named Rooms, Engineering (Config) and Preset views below follow the CIG guide checked 20 October 2026; hull access and live labels are not gameplay-verified here. Do not create damage, fire or oxygen loss for practice.
Use the existing named control cards below. They retain their original source and dated binding evidence, not a new claim that every default was checked in 4.10.2. Read Options > Keybindings > your actual device > Advanced Controls Customization if your input differs. Propose corrections through the ordinary guide review workflow.
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.
You can reach the equipment you are expected to service without asking for directions during an emergency.
If a component is not physically accessible, plan around that limitation. A console diagram is not a doorway.
At the available engineering console, open Vehicle Holo / Rooms View (3D View), called Rooms in the existing control card. Identify one familiar room and its component, then report its shown condition and any offline warning to the pilot. Open Engineering View (Config) and select that same system. Read its power assignment, production or consumption, and temperature warning if supplied.
You can point to the component's location in Rooms and its corresponding system in Config; the pilot knows which item you mean.
If the hull offers only an MFD or lacks a view, use the available readout without claiming an absent console feature. If the selected item does not match, return to Rooms and identify it before touching power.
Open Preset View and note the active named profile or record the current allocations if no named profile is shown. Return to Engineering View (Config). With the pilot's agreement, select one nonessential system and change only its available power value. Watch that system's assignment and production or consumption, then ask the pilot for its actual response. Keep life support and essential flight systems supplied; no fixed percentage or universal combat preset is prescribed.
One selected system has a deliberate changed allocation, and you know the exact prior value or profile needed to undo it.
If the control is absent, do not guess a shortcut. If a required system goes offline or a temperature warning appears, undo the change immediately and report it rather than allocating more power elsewhere.
The same published instructions in one readable view. Use the steps above for controls and practice panels.
Authored practice, source review 20 October 2026 against the 4.10.2 reference baseline. Not an in-game tested route, combat result or promise of a working system on every hull. Follow the live HUD and current issue notices.
Source foundation: the engineering console and MFDs expose power distribution; components have health, temperature and power demand. A shield generator supplies shielding. Room and system readouts serve different diagnosis tasks. Do not turn these into a universal combat preset or fixed percentage.
Our docked crew exercise: the pilot can stop the drill immediately. The named Rooms, Engineering (Config) and Preset views below follow the CIG guide checked 20 October 2026; hull access and live labels are not gameplay-verified here. Do not create damage, fire or oxygen loss for practice.
Use the existing named control cards below. They retain their original source and dated binding evidence, not a new claim that every default was checked in 4.10.2. Read Options > Keybindings > your actual device > Advanced Controls Customization if your input differs. Propose corrections through the ordinary guide review workflow.
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.
At the available engineering console, open Vehicle Holo / Rooms View (3D View), called Rooms in the existing control card. Identify one familiar room and its component, then report its shown condition and any offline warning to the pilot. Open Engineering View (Config) and select that same system. Read its power assignment, production or consumption, and temperature warning if supplied.
Expected result: You can point to the component's location in Rooms and its corresponding system in Config; the pilot knows which item you mean.
If it did not work: If the hull offers only an MFD or lacks a view, use the available readout without claiming an absent console feature. If the selected item does not match, return to Rooms and identify it before touching power.
Open Preset View and note the active named profile or record the current allocations if no named profile is shown. Return to Engineering View (Config). With the pilot's agreement, select one nonessential system and change only its available power value. Watch that system's assignment and production or consumption, then ask the pilot for its actual response. Keep life support and essential flight systems supplied; no fixed percentage or universal combat preset is prescribed.
Expected result: One selected system has a deliberate changed allocation, and you know the exact prior value or profile needed to undo it.
If it did not work: If the control is absent, do not guess a shortcut. If a required system goes offline or a temperature warning appears, undo the change immediately and report it rather than allocating more power elsewhere.
Our report format: location or component, observed condition, effect on the ship, action requested and whether you can continue. Report what you saw; a low shield indication alone does not establish which component failed.
Do not use this lesson as a live combat experiment. Test controls safely first. When a real incident exceeds the available tools or safe access, the useful action is a retreat or service decision rather than an unsupported repair promise.
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.
Compare the reported warning with the earlier baseline and the actual tools and access available. Agree whether to restore an allocation, use the existing repair/fire lesson, or return to services. Tell the pilot which role will be unattended if someone moves.
Expected result: The crew has one agreed next action and knows its operational cost.
If it did not work: If you cannot identify the affected component or safely reach it, do not guess by switching unrelated systems. Keep people clear and plan the return.
The shield looks low but power is available.: Read the actual shield and generator state alongside condition and warnings. Do not infer a specific failure solely from one display.
Changing a preset made another system stop.: Return to the recorded baseline, tell the pilot what changed, then diagnose one system at a time.
Finish on the recorded profile or explicitly report the unresolved configuration. Do not leave the next pilot to discover a practice power change during departure.
Record the selected system, restored setting, visible warning and pilot readback. A changed number is an observation, not proof that a destroyed component was repaired. If unsafe, end practice and use the agreed service or withdrawal plan.
Use Preset View to select the original recorded profile, or return the single Config value to its recorded setting. Reopen the same system in Config and compare its allocation and warnings with the baseline. Ask the pilot for a fresh readback before ending the exercise.
Expected result: The original allocation is restored and both stations agree on the resulting system state.
If it did not work: If the preset is missing or the warning persists, stop experimenting. Keep the unresolved state visible and use the crew's service or withdrawal plan; selecting a preset is not proof of a completed repair.
After the intervention, inspect the same system and compare it with the baseline. Ask the pilot for a fresh readback. Record any warning that remains and restore the practice configuration before finishing.
Expected result: The crew distinguishes an observed improvement from a completed repair or a still-unresolved fault.
If it did not work: If the symptom returns, stop the drill and record the sequence rather than claiming a fix. At a service location, inspect condition after the requested work.
The shield looks low but power is available.: Read the actual shield and generator state alongside condition and warnings. Do not infer a specific failure solely from one display.
Changing a preset made another system stop.: Return to the recorded baseline, tell the pilot what changed, then diagnose one system at a time.
4.10.2 reference baseline; named source UI and controls keep dated evidence; gameplay verification pending. Reference information, not a claim of current-patch playtesting.
CIG Engineering Gameplay Guide, developing systems reference; checked 20 October 2026CIG Welcome Back Pilot: released features and dated eventsCIG input data via Subliminal: 4.9 LIVE cl12248363; 4.10 PTU comparison, 22 Aug 2026CIG peripheral keybindings, updated 17 Feb 2026CIG Alpha 4.8: ASOP loadout recovery and Vehicle Manager changes; checked 14 Oct 2026CIG Personal Inventory, updated 10 Jun 2026; checked 14 Oct 2026CIG Alpha 3.23: master/operator mode labels; controls compared with later input dataRSI Vehicle Maintenance Services, updated 28 July 2026; checked 20 October 2026CIG Alpha 4.10.2 Known Issues, updated 9 Oct 2026; checked 14 Oct 2026CIG Missing Ship and Personal Equipment, updated 28 Jul 2026RSI How to Quantum Travel, updated 12 June 2025; checked 20 October 2026