alterNERDtive
commented
4 years ago That is an ingame problem too, btw. You know how the galaxy map draws your recently travelled path? Well, it simply emits any carrier jumps. So if you go A (carrier jump) B (regular jump) C, it will show you going from A to C.
My squadron and i (PS4 only) went on an excursion into an undiscovered area and since we went there using a fleet carrier it seems to me that the updater does not recognize any of the systems being visitied, scanned, mapped, parked, whatever, after the first fc-jump. The current location simply does not change anymore. Neither login out and in again while not landed on the fc, nor landing on the surface and switching on/off the ps4 or the Console updater seems to solve anything.
The credit balance gets updated, after handing in exploration data on the FC, so the basic connection between my ps4 account, and the edsm connection to my frontier account is working.
I didn't find a similar issue on the edsm github (but that might be a user triggered lack of searching virtuosity).
There is an indication that possibly the whole area in the GalMap is not transmitted correctly to EDSM, because there are numerous systems in this area, which are simply not existing in EDSM, but already discovered in Elite. And even after syncing my account while I was in this system, these systems still do not appear in EDSM.
Possible explanation: these systems can only be reached with an FC, therefore nobody has been able to register these systems in EDSM
The updater is beginning to update the flight - log again from that moment on, the ship launches from the FC in an already EDSM - registered system.