Olympus scan Radar soft-lock · Week 250–251 current-player evidence boundary
ICARUS Olympus Scan Mission Radar Picked Up Early: Fix
Quick Answer
If an ICARUS Olympus scan mission stopped progressing after someone picked up the Radar before the scan completed, first confirm that the client and host run Week 245 build 3.0.23.155919 or later. RocketWerkz documented a legacy issue in Olympus scan-type missions, except Livewire: an early Radar pickup could leave the required snap actor from respawning and make the mission impossible to finish. Week 245 records the fix. On the corrected build, identify the exact mission and tracker step, keep the Radar available, let each scan register before moving equipment, and record whether the prospect began on an older build. The official note does not list every affected mission, give scan coordinates, publish a manual actor reset, or guarantee that every already-stuck prospect repairs itself. Livewire has separate update history and must not be diagnosed through this specific exception.
- Reading time
- 8 minutes
- Difficulty
- Mission identity and scan-state diagnosis
- Checked
- 2026-10-05
On this page
Guide details
Before you begin
Check the Week 245 fix for legacy Olympus scan missions that could become impossible after the Radar was collected before a scan completed.
Week 245 Olympus legacy scan early-Radar pickup fix, excluding Livewire; no invented mission list, locations, reset command, save edit, or old-prospect guarantee.
- Status
- Official ICARUS release evidence plus bounded exact-query review
- Edition
- Week 250–251 current-player evidence boundary
- Platform
- PC · Steam
- Checked
- 2026-10-05
- Check note
- Only the cited release facts are verified. Search volume, keyword difficulty, external SEO score, unsupported recovery methods, numeric values, and later changes remain Unknown.
Before you set out
Prerequisites#
- Use Week 245 build 3.0.23.155919 or later on both the player client and the session host.
- Confirm the prospect is an Olympus scan-type mission and not Livewire, which the official fix explicitly excludes.
- Record the current tracker text, completed scan count, Radar location, and whether the prospect started before Week 245.
- Preserve the prospect while diagnosing; the source does not authorize save editing, console commands, mission deletion, or an invented snap-actor reset.
Why an Olympus scan mission could fail after early Radar pickup#
The Week 245 changelog describes a sequence-sensitive legacy defect rather than a universal Radar failure. In affected Olympus scan-type missions, the player could pick up the Radar before a scan had finished. The game then failed to respawn a required snap actor, and the mission could become impossible to complete. A snap actor is the release note’s internal description of the mission-side object involved; the note does not expose a player command for creating one. The fix therefore supports a narrow diagnosis: mission family, map, timing of the pickup, scan completion state, and running build all matter. It does not prove that every missing marker, every unresponsive Radar, or every stalled scan has the same cause. Livewire is explicitly excluded, so its separate reconnect and search-area fixes should not be merged into this page. On Week 245 or later, use the visible mission state as the authority. Let a scan complete and the tracker acknowledge it before collecting or relocating equipment. If the objective remains unchanged, preserve the sequence instead of repeatedly dropping, replacing, or destroying the Radar. The source confirms the software fix, but it does not promise that an in-progress prospect whose state was already damaged on an older build will reconstruct every missing actor after updating. That uncertainty is why the build at prospect creation matters alongside the current build.
Route 02
Check an ICARUS Olympus scan mission Radar picked up early#
Use this order to distinguish the documented early-pickup defect from another mission, map, scan, or version problem.
Confirm the Olympus map#
Verify that the active prospect is on Olympus. The saved release scopes this legacy scan fix to Olympus rather than every scan mission in ICARUS.
Identify the exact mission#
Record the displayed mission name and objective. Do not call a generic scan, a Great Hunt task, or an Open World activity an affected legacy mission without matching evidence.
Exclude Livewire#
If the mission is Livewire, stop using this diagnosis. The official line explicitly says the early-Radar fix applies to Olympus scan missions except Livewire.
Check client and host builds#
Confirm Week 245 build 3.0.23.155919 or later on both sides. An updated client does not prove a dedicated server or host session runs the fix.
Record the current scan step#
Write down whether the tracker asks for placement, scanning, collection, travel, or another action. Similar equipment can appear across different states.
Leave the Radar until registration#
When testing on the corrected build, allow the active scan to complete and wait for the tracker to acknowledge it before picking up the Radar.
Observe the next valid interaction#
After the tracker changes, collect or move the equipment only through the normal live prompt. The release does not document a hidden interaction sequence.
Note the prospect creation boundary#
If the prospect began before Week 245, record that fact. The patch fixes code behavior but does not publish a guarantee for every old serialized state.
Preserve a remaining failure#
Save the mission name, map, build, scan count, objective text, pickup order, host type, and whether the Radar or placement prompt is visible.
Avoid destructive guesses#
Do not delete the prospect, edit saves, spawn actors, or promise that dropping and replacing the Radar resets the objective. None is documented here.
Pocket list 03
Verified Olympus Radar boundaries#
- Affected scope — legacy Olympus scan-type missions.
- Explicit exception — Livewire is not covered by this exact fix.
- Trigger sequence — picking up the Radar before completing a scan.
- Failure — the required snap actor could fail to respawn, making completion impossible.
- Fix boundary — Week 245 build 3.0.23.155919.
- Unknown — full mission list, scan coordinates, reset command, actor-spawn method, and old-prospect recovery.
- Search volume, keyword difficulty, and external SEO score remain Unknown.
Fault ledger
If the Olympus scan still will not progress#
- The mission is Livewire
- Use current Livewire-specific evidence instead. Week 245 explicitly excludes it from this legacy early-Radar fix.
- The host is older than Week 245
- Update and restart the host before judging the fix; a current client alone cannot establish fixed mission logic.
- The scan has not visibly completed
- Keep the Radar in place and read the live objective. The documented problem concerns collecting it before completion.
- The prospect started before the patch
- Preserve that boundary. The release does not promise reconstruction of every actor missing in an old saved state.
- A workaround tells you to edit or delete files
- Require separate authoritative evidence. The Week 245 source publishes no save-edit or console recovery.
Field questions
Olympus scan Radar questions#
- What caused the documented soft-lock?
- Picking up the Radar before a scan completed could prevent a snap actor from respawning.
- Which version contains the fix?
- Week 245 build 3.0.23.155919-rel-DangerousHorizons is the verified boundary.
- Does this fix include Livewire?
- No. The changelog explicitly says the affected Olympus scan-type missions exclude Livewire.
- Can I manually respawn the missing actor?
- The cited source provides no player command or manual actor-reset procedure.
- Will updating always rescue an old stuck prospect?
- That guarantee is not documented. Record when the prospect began and preserve its current state.