System Map is now LETHALLY SLOW.

Status
Thread Closed: Not open for further replies.
This is getting ridiculous. I am on the Distant Worlds expedition, and I swear the System Map is trying to kill me with lag. I cannot safely check the system map unless I am no where near a star or a landable planet. It takes between 30 seconds and over a minute to bring up the damn map. I have a decent internet and good ping, so I have no idea why I cannot check the system map anymore without pulling my hair out, or stepping away to do some breathing exercises. It used to take 5 seconds at most to load the System Map, and I remember thinking THAT was too long. Now I long for the days when I could quickly check a map and plot a course while fuel scooping. Not anymore!!! If I try that near a star, I stand a good chance of popping my canopy from over heating!!


Frontier please fix this ASAP. It's not funny anymore.
 
Last edited by a moderator:
System Map is now LETHALLY SLOW.

That would imply you die every time you open the system map.

I don't think FD support can help with resurrections, but just in case you are exaggerating a little, and i'm not talking to a zombie, i suggest you raise a ticket with support and send them your netlogs and any other network analysis you can do (try this one: http://netalyzr.icsi.berkeley.edu/)

For my the system map opens in between 1-10 seconds, which from the recent poll on the topic most people were when i last looked.
 
For my the system map opens in between 1-10 seconds, which from the recent poll on the topic most people were when i last looked.

One second? It has never, ever opened that quickly for me, at any time in the past 13 months. Somewhere in the 3-4 second range is a minimum, and while 10 seconds may be the maximum I've seen, that seems like an absolute eternity sometimes. I assume it's requesting system data from the servers each time you open that UI, rather than pulling it down during the jump into the system and caching it. Maybe this is necessary to prevent some kind of cheating, since everything in the space station UI behaves the same way. But all of those things only take a few seconds at most.

The abysmally slow system map is by far the worst experience I'm having on the DW trip. I can't think of any reason why it should take so long to open -- it's at most tens of KB of data, and a UI simple enough to render at hundreds of FPS. I doubt FD can put much time into fixing something that's mainly impacting the ~800-1000 long-range explorers out there, given all the other stuff that needs attention, but if there's a quick fix that can make this better it would be really awesome.
 
This is getting ridiculous. I am on the Distant Worlds expedition, and I swear the System Map is trying to kill me with lag. I cannot safely check the system map unless I am no where near a star or a landable planet. It takes between 30 seconds and over a minute to bring up the damn map. I have a decent internet and good ping, so I have no idea why I cannot check the system map anymore without pulling my hair out, or stepping away to do some breathing exercises. It used to take 5 seconds at most to load the System Map, and I remember thinking THAT was too long. Now I long for the days when I could quickly check a map and plot a course while fuel scooping. Not anymore!!! If I try that near a star, I stand a good chance of popping my canopy from over heating!!


Frontier please fix this ASAP. It's not funny anymore.

Going througha bunch of neutron star farming i can confirm it is LETHAL.

A couple of times now i've exited the system map to over 100% heat and its only been to the loading which has only been an issue since around christmas holiday.
 
Last edited by a moderator:
Agree

Please FDev, do something about system map. At least so that when you have opened it once, the data is stored in the memory (somehow) so that if I want to open it again it goes fast. Why can't the system map start loading in the background as soon as you enter a system, so that when you take it up it has already loaded for a while?
 

Mitore

Banned
I want permanent caching of system map. I opened it once i want as much data as possible to be stored on our pc with some HASH so server can exchange some HASH to see if they check out and save traffic. And yea open cached map first.
 
System map is too slow. It wouldn't be such a big issue if E:D would alllow the usage of more than one screen, so we could continue flying while it loads.

Realistically, it should load in far less than a second.
 
That would imply you die every time you open the system map.

It implies that if I was a less skilled pilot, or a less experienced explorer, I'd be dead a dozen times over in just the first 3000 LY of DW. Just because the system map is a failed assassin, it doesn't mean that it's primary utility atm isn't the as a defacto self destruct dice roll button. Every time I watch that loading icon spin, I am reminded of a similar game called Russian roulette.
 
Good grief, the system map syndrome slowly but steadily climbed my list of things that drag Elite down and now sits proud (and unresponsive) at the very top.

Since Horizons and planetary landings i check the map more often so it's even more obvious that the load times get longer and longer each passing week.

I have to insist that this is a priority issue by now because it seriously cuts into gameflow.

My pet peeves like messed up outfitting menus, weapon balance or supercruise load screens seem positively trivial in comparison (though they are still a bit of an embarassement one year after release).

Edit: It's 6 to 10 seconds on average for me but since Chrismas there are times when i can count up to 25. An these spikes are getting more and more frequent.
 
Last edited:
Maybe it's my low spec system, but i only get the system map to open within 5 seconds if there are only 2-3 objects in that system.

For me, 20-30 seconds has always been the norm. Iv not noticed it taking any longer to open recently.

My method is to Fuel Scoop while hitting the horn, then select nearest object to scan, selecting the throttle speed in relation to the distance from the object as follows...

0% for already scanning
25% for distance up to 125LS away
50% for distance up to 250LS away
75% for distance up to 500LS away
100% for any greater distance.

This allows me to be travelling towards the first object while I can then open the System Map & it's loaded up & Iv had the first look at it to see what's worth scanning in the system, before the first scan starts.

Works every time for me. Yes it's annoyingly slow, but Im used to it taking up to 30 seconds every time by now.

The only frustrating thing now is that Im not planning on landing on EVERY SINGLE PLANET that I come across. But I do want to know what EVERY PLANET TYPE THAT I SCAN IS.
For some reason now, when you scan a landable planet, the data no longer tells you what the planet type is, only speed & distance scales. So you have to go into the SLOW System map again & again to know what type of planets you are scanning. This IS a noticeable distraction in Exploring now.
 
System maps sped up a lot for me when I moved from old I5 to I7 processor. Normally less than 10 seconds for me now.
However they (and exit from hyperspace) started slowing down last night (around 8pm UK time) - OP was this a more "long term" i.e. always since Horizon or "getting ridiculous" or very recent which I think is more server load based?

Simon
 
It implies that if I was a less skilled pilot, or a less experienced explorer, I'd be dead a dozen times over in just the first 3000 LY of DW. Just because the system map is a failed assassin, it doesn't mean that it's primary utility atm isn't the as a defacto self destruct dice roll button. Every time I watch that loading icon spin, I am reminded of a similar game called Russian roulette.

Here's a tip, don't open the system map when pointing at the star ;)
 

Mitore

Banned
Here's a tip, don't open the system map when pointing at the star ;)

We should be able to close that damn map even if it's not already loaded, or keep it loaded or something because opening map 5 seconds later again and it loads for TOO DAMN long again, it's just poor excuse for bad code.
Some people just started playing ED and may quit over things that feels like alpha pre-release quality. Not to mention open is already openly empty.
 
Here's a tip, don't open the system map when pointing at the star ;)
*

When fast traveling through neutron stars, the SOP is point to the star to scan, open the map to have a looksee, close the map. Scan finishes.*
Since most use the neutron star fields to cover long distances fast while making a dime, it is anoying to lose time for no good reason in every systems just to open the map.

Now you cannot do that (well, it is possible, but then the ship may be on fire upon closing the mao). The long time needed to open the map is from 1.5/2.0, before it was fine.
Sometimes, it's fast (like 0.5 sec) and sometimes its very slow (30 seconds). It seems related to the number of objects in the system, but there is something more to it.

*here is a dumb way to die (lose a SRV) : open the galactic map, not realizing that you are on very low fuel. Spend 10 min looking for planetary nebulas. Die due to lack of O2 XD
 
Last edited:
When fast traveling through neutron stars, the SOP is point to the star to scan, open the map to have a looksee, close the map. Scan finishes.*
Since most use the neutron star fields to cover long distances fast while making a dime, it is anoying to lose time for no good reason in every systems just to open the map.

Now you cannot do that (well, it is possible, but then the ship may be on fire upon closing the mao). The long time needed to open the map is from 1.5/2.0, before it was fine.
Sometimes, it's fast (like 0.5 sec) and sometimes its very slow (30 seconds). It seems related to the number of objects in the system, but there is something more to it.

For me, it didn't change from before 2.0 and after. Before, it was sometimes slow, about ten seconds at most, now it's still about ten seconds at most. If anything, I get less lag overall now.

There is something fishy going on with every problem in the game looking very inconsistent across players. I don't get many of the problems people say they suffer from regularly. All I get is occasional hicups, which are annoying but never game breaking. I guess it's one of the special perks that come with being a fanboy, next to the secret paycheck.

Jokes aside, I wish the problems were consistent across the board so FD could identify what the cause is and fix it. This way it looks like what fixes something for a part of the playerbase breaks it for another.
 

Deleted member 38366

D
Although the issue is very very old, I somehow don't think the System Map (on modern Systems) should take longer than 0.1sec to open up.

Never understood what was the matter with it and its very notable delay.
After all, it's just a number of Balls with Textures and a little Animation (Suns), plus a little bit Information on them.

Anything requiring Server inquiry should be handled and cached the very moment the Hyperspace countdown starts for this specific System.
 
Last edited by a moderator:
Although the issue is very very old, I somehow don't think the System Map (on modern Systems) should take longer than 0.1sec to open up.

Never understood what was the matter with it and its very notable delay.
After all, it's just a number of Balls with Textures and a little Animation (Suns), plus a little bit Information on them.

The delay is in downloading the first discoveries information most probably. It's database optimisation they need to make. Either that or they can try pre downloading the info in the background during the hyperjump. This requires more traffic because it will load the data even if you won't use the system map so it's traffic on fd servers for something you'll never see.

The only logical way is to reconsider how the system and first discovery data is stored and accessed. They can of course buy bigger and faster servers, which probably isn't as simple as it sounds because they would have done it already.
 
For some reason now, when you scan a landable planet, the data no longer tells you what the planet type is, only speed & distance scales. So you have to go into the SLOW System map again & again to know what type of planets you are scanning. This IS a noticeable distraction in Exploring now.

It's actually just super buggy. It always does show the planet type after a scan, but usually it switches back to the speed/distance readout after a fraction of second. Rarely it won't do this and will keep showing the planet type. I agree this is super annoying, compounded by how slowly the system map opens.

Sometimes, it's fast (like 0.5 sec) and sometimes its very slow (30 seconds). It seems related to the number of objects in the system, but there is something more to it.

The only time I ever see the map open that fast is if I repeatedly open/close it without much delay in between, several times in a row. Almost like something finally gets cached. It is equally slow for me on systems with only a single star as it is for systems with 50+ bodies. If they are doing some kind of quick/dirty "render each planet using the game engine" thing instead of having pre-baked thumbnails, then it doesn't seem to have much impact (on my system anyway).

Either way, this has definitely changed my routine. I always make sure I'm at 0% throttle now before opening the system map, unless I know I'm traveling a few thousand+ LS toward a planet. It really breaks up the pacing of trying to explore efficiently. Having to wait a long time for detailed scans to complete, I can accept for lore reasons. But unless the lore also states that my ship's cartographic systems are powered by a vintage Spectrum ZX, there's no explanation for this. Especially when the vastly more complex galaxy map opens almost instantly when set to "realistic" mode.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom