Practise a route, return and service check
A known-destination drill with a planned return and named Landing Services steps.
A known-destination drill with a planned return and named Landing Services steps.
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.
Our exercise: start at a serviced port, choose one known destination and return to the same port. Eat, drink, check helmet and supplies before departure. Record the starting location, destination and planned service fallback. Choose a route you can abandon without losing your transport.
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.
SC Nomads practice plan
While safely parked, write down your starting port and a nearby serviced destination in the same system. Agree these names with anyone coming along.
You can name both the outward stop and the place you intend to return to.
What this means: A successful return teaches a reusable route before contracts, cargo and deadlines compete for your attention.
If the destination is unfamiliar or the trip includes a jump point, choose a shorter exercise first.
mobiGlas > Map > search
Search its name and select the correct result. Compare the body and location names. Wheel zooms; left-drag rotates; right-drag pans.
The selected place matches your written destination.
What this means: Selecting a place identifies it; the next action commits the route.
Similar names are not interchangeable. Recheck the result before plotting.
Map > Route to this Location
Choose Route to this Location. Read the right panel for Quantum Fuel and the number of legs.
A plotted route and its requirements are visible.
What this means: Several legs mean several travel stages, not one uninterrupted journey.
No route? Check the selection and your ship context. Keep this separate from a drive that will not engage.
Flight - Movement > Cycle Master Mode (Long Press)
Read the current master mode. If it is SCM, hold B once and let the transition finish. If it already reads NAV, leave it there.
The master-mode label reads NAV and the transition completes.
What this means: NAV prepares the ship for travel. Spooling is the drive preparing itself, not proof of a calibrated destination.
This input cycles modes. Holding it again can undo your choice. Inspect the current label before another input.
Vehicles - Seats and Operator Modes > Next Operator Mode
Click the wheel, rather than scrolling it, until the operator label reads QT. Read the label after each click.
NAV and QT are selected.
What this means: QT exposes quantum-travel information. Changing the interface does not select your destination for you.
FLT is a different operator. If the quantum display is absent, inspect this label before trying the engage input.
Write down the selected destination, next leg and displayed fuel requirement. Leave a reserve for the return and an alternative service stop; do not spend the entire displayed capacity on the outward leg. This is a planning rule, not a fixed fuel percentage.
You can name the next marker and the place you intend to return to.
If the map shows an unexpected system or leg, clear the mistaken selection and replot while stationary. A familiar name is insufficient if the location is wrong.
Before engaging, read the master-mode and quantum operator labels and the drive readiness/alignment feedback. After the leg ends, reduce the approach and identify terrain or traffic before concentrating on the destination.
You can distinguish route selection, drive preparation, travel and local approach as four observations.
If engagement fails, read the actual warning and stop changing unrelated controls. Reposition for a clear route or choose a reachable intermediate marker. Do not hold a travel input while aiming through terrain.
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.
Our exercise: start at a serviced port, choose one known destination and return to the same port. Eat, drink, check helmet and supplies before departure. Record the starting location, destination and planned service fallback. Choose a route you can abandon without losing your transport.
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.
SC Nomads practice plan
While safely parked, write down your starting port and a nearby serviced destination in the same system. Agree these names with anyone coming along.
Expected result: You can name both the outward stop and the place you intend to return to.
A successful return teaches a reusable route before contracts, cargo and deadlines compete for your attention.
If it did not work: If the destination is unfamiliar or the trip includes a jump point, choose a shorter exercise first.
mobiGlas > Map > search
Search its name and select the correct result. Compare the body and location names. Wheel zooms; left-drag rotates; right-drag pans.
Expected result: The selected place matches your written destination.
Selecting a place identifies it; the next action commits the route.
If it did not work: Similar names are not interchangeable. Recheck the result before plotting.
Map > Route to this Location
Choose Route to this Location. Read the right panel for Quantum Fuel and the number of legs.
Expected result: A plotted route and its requirements are visible.
Several legs mean several travel stages, not one uninterrupted journey.
If it did not work: No route? Check the selection and your ship context. Keep this separate from a drive that will not engage.
Flight - Movement > Cycle Master Mode (Long Press)
Read the current master mode. If it is SCM, hold B once and let the transition finish. If it already reads NAV, leave it there.
Expected result: The master-mode label reads NAV and the transition completes.
NAV prepares the ship for travel. Spooling is the drive preparing itself, not proof of a calibrated destination.
If it did not work: This input cycles modes. Holding it again can undo your choice. Inspect the current label before another input.
Vehicles - Seats and Operator Modes > Next Operator Mode
Click the wheel, rather than scrolling it, until the operator label reads QT. Read the label after each click.
Expected result: NAV and QT are selected.
QT exposes quantum-travel information. Changing the interface does not select your destination for you.
If it did not work: FLT is a different operator. If the quantum display is absent, inspect this label before trying the engage input.
Write down the selected destination, next leg and displayed fuel requirement. Leave a reserve for the return and an alternative service stop; do not spend the entire displayed capacity on the outward leg. This is a planning rule, not a fixed fuel percentage.
Expected result: You can name the next marker and the place you intend to return to.
If it did not work: If the map shows an unexpected system or leg, clear the mistaken selection and replot while stationary. A familiar name is insufficient if the location is wrong.
Before engaging, read the master-mode and quantum operator labels and the drive readiness/alignment feedback. After the leg ends, reduce the approach and identify terrain or traffic before concentrating on the destination.
Expected result: You can distinguish route selection, drive preparation, travel and local approach as four observations.
If it did not work: If engagement fails, read the actual warning and stop changing unrelated controls. Reposition for a clear route or choose a reachable intermediate marker. Do not hold a travel input while aiming through terrain.
Our record template: system, body, nearest named marker, observation time, approach notes and why you decided to leave. A screenshot is your observation, not proof that the location is safe, permanently empty or a paid discovery.
Scanning is a separate skill. This drill does not invent scan ranges, signature codes, a discovery sale terminal or a universal ping shortcut. Use the existing scanner lesson and the named binding for your actual device when resource identification is the objective.
Map > current route
Once safe to look away from flight, check the location reached and any remaining leg. Say whether the next task is another quantum leg or a local approach.
Expected result: Your location and next task agree with the plan.
The long-distance journey and the final landing are separate tasks.
If it did not work: Unexpected location? Reconcile the route before engaging again. Do not follow an unrelated marker simply because it is visible.
Choose a simple trigger such as finishing one observation, a worsening situation or reaching the supplies you reserved for return. Keep the ship location and a walking route back identifiable.
Expected result: You leave deliberately while transport and supplies remain available.
If it did not work: If you cannot identify the ship or return path, stop extending the excursion and recover your bearings. Do not convert a short drill into an unplanned rescue.
The destination is visible but the ship will not travel.: Compare selected route, operator label and the displayed drive warning. Fix the named obstruction or requirement before repeating engagement.
The route was successful but I cannot repeat the discovery.: Improve the location record and distinguish your observation from a persistent bookmark or supported discovery feature.
Complete the planned landing before opening services. The dated RSI procedure below separates request, cost approval and actual outcome; a successful route does not prove the ship was refueled.
Before ending, record the destination reached, service requested and unresolved warning. If service fails or supplies no longer support another leg, stop the excursion and retain the alternative return or assistance plan.
Open mobiGlas; latest-known default from RSI Vehicle Maintenance Services, updated 28 July 2026. Check your saved device binding if changed.
Land at the assigned service location and remain in the pilot seat. Open mobiGlas with the latest-known F1 default, then select Landing Services, the label in RSI's 28 July 2026 article. Read the ship and offered repair, restock, hydrogen and quantum-fuel choices before selecting what is needed. These are different supplies; a quantum top-up does not refill hydrogen.
Expected result: The landed ship service screen is open and you can identify the requested service.
If it did not work: If Landing Services or the expected choice is absent, confirm you are landed at a serviced location and still in the pilot seat. Do not substitute a tanker transfer or another menu just because it also mentions fuel.
Review the selected services and any displayed quantities and charges. If the cost or request is wrong, cancel or change the selection before committing. Select Confirm only when satisfied, wait for the operation to finish, then re-read hydrogen and quantum quantities separately, condition or ammunition as applicable, and any displayed credit change.
Expected result: The intended quantity or condition changes after completion; opening the menu or clicking Confirm alone is not proof of service.
If it did not work: If an option is unavailable, a warning appears, or the readouts do not change after the operation, do not repeatedly approve another charge. Record the observed failure and use the planned alternative service stop.
The destination is visible but the ship will not travel.: Compare selected route, operator label and the displayed drive warning. Fix the named obstruction or requirement before repeating engagement.
The route was successful but I cannot repeat the discovery.: Improve the location record and distinguish your observation from a persistent bookmark or supported discovery feature.
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.
RSI How to Quantum Travel, updated 12 June 2025; checked 20 October 2026RSI Locations in Star CitizenRSI Vehicle Maintenance Services, updated 28 July 2026; checked 20 October 2026CIG defaultProfile.xml, extracted by Subliminal: 4.9 LIVE defaults compared with 4.10 PTU, checked 13 Oct 2026CIG Getting Started, updated 24 Jul 2026; checked 14 Oct 2026CIG Alpha 3.23.0: master modes and hold inputs, historical design basis; checked 14 Oct 2026CIG How to Land Your Ship, updated 22 Jun 2025; checked 14 Oct 2026CIG Alpha 4.10.1 LIVE.12650677: route and ATC fixes; checked 14 Oct 2026CIG default input data via Subliminal: 4.9 LIVE cl12248363, compared with 4.10 PTU; checked 14 Oct 2026CIG Set up keybindings for your peripherals, updated 17 Feb 2026CIG Alpha 4.10.2 Known Issues, updated 9 Oct 2026; checked 14 Oct 2026CIG Engineering Gameplay Guide, developing systems reference; checked 20 October 2026