System Map is now LETHALLY SLOW.

[Senik]

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.

There's a pretty cool presentation FDEV gave talking about how the whole thing is put together, with the various databases etc. that are running on AWS (you can find it on youtube). The database records for star systems (appear to) store everything about that system, including first-discovered-by data, so it should fetch everything all at once from a single record. If they're not pre-loading it to conserve bandwidth, then there needs to be a heuristic that starts doing that once the game realizes you frequently access the system map.

I also suspected at first that the growing number of scans/discoveries are what's slowing it down, but I'm not so sure. It makes sense, since the general complaint is that it's been growing gradually slower over time for people. But really it could be anything.

 

[Drakonluke]

Since the map is already slow (3D rendered), any chance that we will ever have the map with bodies in their current position, set waypoints... that kind of thing?
That would be a very NIIIICE mission/exploration planning tool...

 

[Agony_Aunt]

it's just poor excuse for bad code.

Ah, my apologies. I wasn't aware you performed code reviews for FD. Must be quite exciting getting to see all the new features FD are developing.

Joking aside, i'm not disagreeing with the point that it takes a long time for some people to open the map, or that it should be able to cache the system map, or that it would be great if you could close it while its till opening. Indeed, it would all be nice if FD could sort it out.

I simply stated that if you know that it takes a long time to open, don't do it while facing the star, which is what some people here seem to be implying they are doing. I'm sure i don't have to say something like don't AFK when in supercruise right? Its a dangerous thing to do. If you are aware of a the danger of performing a certain action, then don't complain when you get bitten for doing it.

The thing to do though, if you are suffering problems with the system map, you contact support about it, giving netlogs and whatever else they want, so they can identify the source of the problem and pass it onto devs for a fix.

Complaining about it on the forums, while useful for getting it off your chest, doesn't help FD. They don't have access to your PC, they cannot see all the traffic from your computer, and they don't know your hardware. The way you can help them is by providing them the information they need to debug this issue.

 

[Ydiss]

It's been a very long time since I dared open the system map unless I was flying clear of the sun. It takes ages now. I imagine it's less tied to Internet than system spec though. My Internet is very good. It's all the procedural generation going on. Though I'm not sure why it's got worse since 2.0. Unless it's also tied to graphics memory. Can't see why though.

It's far from optimal. And has always been a bit slow, for me.

 

[Ziljan]

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

Thank you captain obvious. If you read the OP, you'd know that wasn't the issue. But as others have said, pre-horizons, it's was perfectly safe to open the system map while refueling and scanning. As of 2.0 many of us are taking a serious risk. But just FYI, the last assassination attempt happened when I was pointed away from a G class proto star (no distance/scooping indicator), and headed away from the star for 5 seconds, but apparently still close enough to fry because while I was waiting for ADS results, the temps just kept rising while I could only look on in horror at a loading screen with Sparks and alarms blaring. Luckily the system map timed out and canceled back to the cockpit just in time for me avoid any serious damage, but if it had taken the full 30 seconds and actually loaded , then I would staring through a cracked canopy if I was lucky.

 

[MagicTofu]

The way you can help them is by providing them the information they need to debug this issue.

Instead of debugging, a slight design readjustment is what would probably make the system map more comfortable to use, at least allowing cancellation of the map opening when it starts taking way too long, and even better, as already suggested by others, caching all required network data such as first discoveries during hyperjump or through a thread upon arrival in the system.

 

[Cosmos]

I've noticed its not a good idea to try and open the system map when you are on the move towards a stellar object. I wonder if its a case of watching a kettle boil. Generally bringing up the system map is quite slow.

 

[Devlin-Darkside]

Yep its slow for me too and I have a good PC with a fibre connection.

When doing shadow missions I often need to look fast at the map and find myself thinking dare I open the map or not.

Apart from being slow I sometimes find it hard to select stuff as icons pop up with tiny movements of the mouse.

The whole thing needs a revamp imo.

 

[ZATZAi]

Yah it's been pretty bad of late, depends on what system your in. I guess some systems have recently been generated by the servers and they can be pulled from a cache? Because out in the black some systems can take a really long time, which I guess is because the data is being generated for the first time.

Until it's fixed, a good hold-over would be the ability cancel opening the system map. Right now when you request the system map you can't do anything until it eventually opens. If we could press ESCAPE while it's loading to cancel the load and go back to our ship that would be great.

Or better yet, let it load in the backgroup, it could say "Assembling System Data" and when it's done polling from the server give us a prompt so we could open it. Maybe even cache the last 10 systems on our systems locally? Some of us go in and out of the System map a lot and it's a real pain right now because of this issue.

 

[Marshall...]

Yep its slow for me too and I have a good PC with a fibre connection.

When doing shadow missions I often need to look fast at the map and find myself thinking dare I open the map or not.

Apart from being slow I sometimes find it hard to select stuff as icons pop up with tiny movements of the mouse.

The whole thing needs a revamp imo.

Exactly the same here. By the time its taken to open the system map, im usually bounced back out due to being interdicted!

 

[Devlin-Darkside]

I see people saying don't open the map when you are next to a star!

But the thing is when you have just arrived in a system and you don't have the system data and need to select a destination fast what do you need to do before you pull away from the star?

Yea open the dam map!

 

[Agony_Aunt]

Since the map is already slow (3D rendered), any chance that we will ever have the map with bodies in their current position, set waypoints... that kind of thing?
That would be a very NIIIICE mission/exploration planning tool...

You are talking about the orrery view.

A highly requested feature for a long time... we can hope and dream that one day FD will implement this.

 

[Agony_Aunt]

I see people saying don't open the map when you are next to a star!

But the thing is when you have just arrived in a system and you don't have the system data and need to select a destination fast what do you need to do before you pull away from the star?

Yea open the dam map!

Turn so your rear end is facing the star. This has two effects:

1) No risk with delay opening the map

2) Any ships wanting to interdict you will fly into the sun.

Its a win-win.

 

[Agony_Aunt]

Though I'm not sure why it's got worse since 2.0.

As i recall the problem actually started somewhere around 1.4. I remember pre-1.4 it was quite fast always to open the map. Then somewhere about beta of 1.4 both galactic map and system map got slower and slower. It then cleared up a bit, but never returned to the previous speed it was in 1.3.

And of course, from posts here and in the poll thread about this, its clear for some people this is still a serious problem.

 

[Zieman]

I see people saying don't open the map when you are next to a star!

But the thing is when you have just arrived in a system and you don't have the system data and need to select a destination fast what do you need to do before you pull away from the star?

Yea open the dam map!

You select the target in left side panel (navigation tab).

 

[Agony_Aunt]

Instead of debugging, a slight design readjustment is what would probably make the system map more comfortable to use, at least allowing cancellation of the map opening when it starts taking way too long, and even better, as already suggested by others, caching all required network data such as first discoveries during hyperjump or through a thread upon arrival in the system.

How about both? You help FD find the cause of the problem by supplying logs, and they add code to do the other stuff?

 

[Rorkan]

My system map never takes more than 5 seconds to open.

Are people running E: D on toasters?

 

[Bakerloo]

Yes it's a pain in the Aris.

I don't know how feasible this suggestion is, but I would really like it if the system map opened up as a transparency taking up the top left hand quarter of the screen leaving me in full control of the ship until it loads. Then have an option to go from the transparency to the main map. Most of the time I don't interact with it at all, I just want a quick peek (ha! quick) at the system to see if there is anything worth scanning.

My 20 won.

 

[Audax Cuthalion]

Actually for me the system map is terminally slow, too.
Granted the laptop I play on is on the edge of the minimum requirements, it takes 20 to 30 seconds to open it. Quite a PITA.

 

[DrakeAurum]

Honestly, I wouldn't mind having hyperspace jumps take a little longer (hopefully not an entire 30 seconds though!) and having the loading and compiling of the system map incorporated into that loading screen. I mean, it must basically be the same data, right?