Not offered for the interception calculation: Burke-QD (4 km), Tidelock QD (4.5 km), qed_rsi_s03_scorpius (5 km). These are dampeners: inside their jammer range they stop anyone from entering quantum travel, but they pull nobody out of it. Their radiusMeters field reads 1 – an unset field, not a one-metre radius. So there is no interception point for them, not because a value is missing but because none exists.
Set up
1 · Where does the target start?
System and origin of the quantum route.
2 · Where is it going?
The quantum destination. The line between the two is the route.
3 · What are you interdicting with?
The device sets the effect radius.
4 · How close to the destination?
Remaining distance to the quantum target at which you break the jump.
Result
QT abort
When to break the jump – target value, measured deviation with its sign, and the number you watch for in game. Negative means: break earlier.
Verify position
Run /showlocation in game and paste the clipboard content here. The page only reads what you paste – it does not access your clipboard and sends nothing anywhere.
Live navigation
When this page runs inside the BalduursGATE client, the client can hand a position copied with /showlocation straight to it. In a normal browser you keep pasting by hand – both lead to the same calculation.
The client sends nothing but a checked position contract. No other clipboard content leaves your computer – this page cannot read the clipboard at all.
Pirate Nav
Verse validation
For the first in-game test: what the page made of your report – without keeping the raw text.
SHOWLOCATION FORMAT UNCONFIRMED – the command’s output is not in our game data. The parser accepts several described shapes and states for every report which one it recognised. The first in-game test decides.
Calibration test (test B from PIR-02b)
This test is defined in PIR-02b and is not reinterpreted here. It measures how far the ship keeps travelling after the abort.
For an overlay and OBS
A display can pick up this data model later. PIR-02 deliberately does not build an overlay yet.
Expert view
Vectors, tolerances, alternatives and the raw data of the calculation.
Worked example
Test track (invented coordinates, clearly marked)
Route
TEST-ALPHA → TEST-BETA
Route length
100000 km
Break jump at remaining distance
5000 km
X / Y / Z
95000 / 0 / 0
Position along the route
95.0 %
Two invented points, 100,000 km apart. They have nothing to do with Star Citizen and only exist to make the calculation checkable: breaking at 5,000 km remaining means 95 % of the route flown.
Real route from our own data
Route
CRU-L1 → CRU-L4 (Stanton)
Route length
18266527 km
Device
Reynie-QVG · 20 km
Break jump at remaining distance
50.000 km
X / Y / Z
-7173196 / -17754162 / 0
Clearance to nearest body
50 km (CRU-L4)
Smallest remaining distance
50.000 km
Computed on game version sc-alpha-4.10.0-hotfix__1.0.191.55227, calculation model ad74f7c0e9d2e2fe. Not verified in game yet.
What we do not have
Protected and exclusion zones
Our game data carries no size for a protected zone. Only the device’s own check range (30,000 m) is sourced. The map therefore shows no exclusion volumes.
The exact shape of /showlocation
No hit in the game version’s global.ini (90,363 lines) – the command builds its output in code. The parser therefore accepts several clearly described shapes and states which one it recognised.
The unit of the coordinates
Also not provable. The page checks both readings against the extent of the system and says which one fits – or that it is ambiguous.
Physics grid and commlink
We have no solid data on this. So all that stands here is one line: DATA MISSING.
Movement of the bodies
We treat system positions as fixed. A body’s own rotation does not change that, and orbital movement is not represented in our data. Re-check on patch day.
Routes across several jumps
PIR-02 computes one straight quantum leg between two anchors. Jump-point chains across systems come later.
This is an unofficial Star Citizen fan site, not affiliated with the Cloud Imperium group of companies. Star Citizen®, Squadron 42® and Roberts Space Industries® are trademarks of Cloud Imperium Rights LLC. All game data, names, places, ships and imagery from the game belong to Cloud Imperium. Non-commercial fan project.