An example of a system not rendered as intended is the Farwell system, near Colonia.

It has Null orbit points between stars at CD and BCD,

This is an issue with how data is processed in the back end as well as how it is handled in the front end.

Both will need to be modified at the same time to improve this (without making things worse).

It's probably missing a check when some events relevant to changing ship occur. I've observed this on a Fleet Carrier so it might be that it's related to changing ships and/or jumping in a carrier and/or using Apex. It is hard to replicate so it's at least a bit of an edge case.

I think it's also missing ship renaming events, so should look at that too.

Specifically - in addition to whatever events are need to track changing ship - it should also listen for Set User Ship Name event and update name/ident in Ship model when it changes.

When near an on-foot ground mission target, serialized JSON data for the location displayed, instead of a descriptor the destination.

i've experienced crashed on icarus lately, not sure the cause of it.

When scanning unmapped system latest planet doesn’t show up. E.g. after scanning 4 bodies only 3 show up.
Once system is fully scan you have to honk again for it to mark as completed in app, otherwise is stays at 90ish percent.

This has been requested by several users, who are using multiple monitors.

This should be an option in the settings.

As reported here, some systems have planets that are landable, but the Navigation Map and List views do not indicate they are landable:

https://forums.frontier.co.uk/threads/icarus-terminal-pre-release.594667/page-15#post-9977466

Examples of systems / bodies:

• HIP 96438 - Planet A 5 is landable
• HIP 94791 - Planet 3 A is landable
• Outopps UB-K c22-2 - Multiple bodies

Since this report, I've seen this bug first hand in other systems.

I'm sure it's because there is data in EDSM from these planets that pre-dates the release of Odyssey and these planets were recorded in EDSM as not being landable, because they were not at the time.

What I'm not sure of is if the problem is ICARUS Terminal is showing older data from ESDM incorrectly (that has been an issue before) or the issue is EDSM persisting older data and not updating when a system is scanned again and has changed.

Frameshift drive active is permanently blinking in top right corner. Restarting the app shows system name again. After a single jump frame shift message stay permanently on again.

Display time more legibly and use space more efficiently, in part to make room for future data in the header

Nav panels not keeping up with system changes and often defaulting to a previous system. The course plotted panel keeps up. I was using Icarus on 5 different devices so I went down to two and then to just one, there was no change in the panels not keeping up or showing wrong system. With my use of Icarus, this is a program breaking fault.

Not sure where to display this yet, certainly on the Navigation Panel but potentially also in the header. In the Navigation Panel it would be appropriate to display systems where the player is wanted at, if that information is known.

I keep the terminal on a secondary monitor. When i click on the "full screen" icon, the terminal moves to the primary one.

before:

after:

It should instead remain on the monitor where the windows currently is.

A recent release of Chrome OS (sometime around August) introduced a bug with table rendering, currently most prevalent on the Engineering Blueprints view. This is not a bug in ICARUS Terminal, it's a rendering bug in Chrome and is specific to Chrome OS (not Chrome in general). It's been an issue for a few weeks now.

This only happens on Chrome on Chrome OS - not the desktop Chrome for Windows or Mac (or on Android).

It's worth exploring to see if a quick workaround for this issue is possible.

I would like to be able to pick a folder when Setup Icarus.
Right now it does not ask for it, neither tells where Icars was installed at the end.

Several CMDRs have requested the ability to be able to see which systems have already been mapped (at least as far as EDSM knows) in the Route plan view.

As routes can be hundreds of light years and many systems there are technical considerations as to how to do this, how to cache the result and how and when to invalidate the cache.

The simplest approach would be to do this for every system when a new route is plotted, and to cache the results until a new route is set, although this may impose an unreasonable number of requests in sequence on the EDSM API for long routes (e.g. with hundreds of hops).

An ideal approach would be to use intersectionObserver to fetch the data as the user scrolls the list of systems in the route, and to cache that data in memory; and update that cache when the user lands in the system (and/or uses FSS inside the system). This would only fetch data for routes as actually needed; although it would take a second or two to add that information to the display as the user scrolls.

As a first iteration, I would like to include an indicator for "high value" planets (>500k when scanned) in the List view and the Inspector panel (which is shown in both the List view and System Map view).

1. Earth-like World
2. Water World
3. Ammonia World
4. Any body that can be Terraformed

This would not rely on local scan data or checking for status (e.g. discovered, scanned, etc) so is easy first iteration that would be useful; later iterations could include specific value estimates for bodies and systems; they would require more significant improvements to the Navigation panel.

For more information see https://elite-dangerous.fandom.com/wiki/Explorer

I was trying to open a terminal on my tablet, and then i realized that the IP address shown on the launcher was incorrect. it was neither my local IP address, nor my public one.

For example. In Vega System. Fort Dixon actually orbits the ELW (Tracy's Havan) and not the innermost rocky planet.

https://imgur.com/a/xRtAAT4

The Terminal window will not go to Fullscreen on any other screen then the main screen.
Even when I pull the window to my second screen, when I click on the button to go to Fullscreen, the Terminal window will switch back to the main screen. It should be possible to choose on which monitor I want to have the Terminal window.

Bug introduced in v0.17.0.

Somehow it's not rendering a circle correctly >.>

Would be appropriate to display as a notification and/or as icon in the header

Much like the in-game "modules" tab, it would be awesome if we could have a "modules" tab in icarus that lists our internal modules & their status (health being the most important one). This is extremely useful while in combat! While fighting thargoids, I'm often overheating temporarily and like keeping an eye on my modules to make sure they're above 75% health.

It would be cool to aquire the Devices Wake-Lock in the Web Application especially on Tables or Smartphones to prevent the Device to go to Standby or Prevent Screen Dimming.

This can happens when disembarking on carrier (it reverts to just displaying the system name as current location, which is not wrong but not intended behavior) and when on a carrier on foot after it has jumped (e.g. if you were seated during the jump).

When not in input mode (e.g. with focus on a textarea or text input control) allow key presses to active panels. This is something several CMDRs have requested.

The initial implementation may include key navigation for Top and Left navigation items (e.g. WSAD/Num Pad to move LEFT/RIGHT between panels and UP/DOWN between views within panels, so that arrow keys can still be used for scrolling; not everyone has page up / page down buttons) as well as support for explicit short cuts (e.g. numbers on the top row of the keyboard - which are widely supported across different keyboards layouts).

A future iteration may aim to make the shortcut keys configurable, for the first release of this feature the aim will be to choose defaults.

For context, see this thread:
https://forums.frontier.co.uk/threads/icarus-terminal-pre-release.594667/page-14#post-9968523