Environment:
ICARUS Version: v0.23.0 (Hotfix build)
OS: Windows 11
Game Version: Elite Dangerous Odyssey
Description:
Since updating to v0.23.0, the Navigation menu fails to populate in new or undiscovered systems. Even after performing a Full Spectrum Scan (FSS) or a Detailed Surface Scan (DSS), the panel remains stuck on:
No System Information \n Telemetry Unavailable
Observed Behavior:
Known Systems: Navigation works correctly (data is successfully pulled from EDSM/external resources).
Other Panels: Ship Manifest, Materials, and Jump Indicators work perfectly, confirming that the ICARUS Service is successfully reading the local journal files.
Troubleshooting Attempted: * Deleted the EBWebView cache folder in AppData\Roaming.
Attempted to force refresh via the "No Scan Data" button (no effect).
Confirmed the issue is specific to "virgin" systems where EDSM does not yet have data.
Expected Behavior:
Upon completing an FSS or Surface Scan in an undiscovered system, the Navigation panel should populate with the scanned bodies/system information using the local journal events as a fallback when EDSM returns no data.
Technical Context:
The issue appears to be a regression in the fallback logic. While v0.23.0 successfully handles the new EDSM API handshake for known systems, it seems to "hang" or fail to trigger the local journal parser when EDSM returns a 404/null for a new discovery. The backend service continues to read other journal files (Materials/Cargo), but the Navigation thread does not transition from "Waiting for EDSM" to "Parsing Local Scan Events."
Environment:
ICARUS Version: v0.23.0 (Hotfix build)
OS: Windows 11
Game Version: Elite Dangerous Odyssey
Description:
Since updating to v0.23.0, the Navigation menu fails to populate in new or undiscovered systems. Even after performing a Full Spectrum Scan (FSS) or a Detailed Surface Scan (DSS), the panel remains stuck on:
No System Information \n Telemetry Unavailable
Observed Behavior:
Known Systems: Navigation works correctly (data is successfully pulled from EDSM/external resources).
Other Panels: Ship Manifest, Materials, and Jump Indicators work perfectly, confirming that the ICARUS Service is successfully reading the local journal files.
Troubleshooting Attempted: * Deleted the EBWebView cache folder in AppData\Roaming.
Attempted to force refresh via the "No Scan Data" button (no effect).
Confirmed the issue is specific to "virgin" systems where EDSM does not yet have data.
Expected Behavior:
Upon completing an FSS or Surface Scan in an undiscovered system, the Navigation panel should populate with the scanned bodies/system information using the local journal events as a fallback when EDSM returns no data.
Technical Context:
The issue appears to be a regression in the fallback logic. While v0.23.0 successfully handles the new EDSM API handshake for known systems, it seems to "hang" or fail to trigger the local journal parser when EDSM returns a 404/null for a new discovery. The backend service continues to read other journal files (Materials/Cargo), but the Navigation thread does not transition from "Waiting for EDSM" to "Parsing Local Scan Events."