Why is the galmap so slow?

Seriously - pre-2.2 I hit the hotkey for the galmap and it came up in seconds... now I have to wait a minute or more.
 
I'm finding the system map slightly faster, the galmap and highwaking both take a lot longer. Dropping down from supercruise also takes about a minute each time for me. It used to be that bad at planetary bases, now it seems to be everywhere.
 
I'm finding nearly every panel to be excrutiatingly slow to open... galaxy map takes 30-60 seconds. I have 3 bookmarks. And 3 ships total on the map.

Mission board, Outfitting, Ship Selection are also very, very slow - we're talking "Has the game actually just crashed?" slow. At one point I just went out for a smoke and hoped it would appear by the time i returned.

EDIT: Also noticed actions within Outfitting were slow. Selling a few things back to the Outfitter took... I don't know, 10-15 seconds (per item) to start animating (complete the sale) after I clicked SELL.
 
Last edited:
My experience has been different. If I try and open the galaxy map, right after logging in, it is very slow. This is true of pre- and post-2.2. To give you an example of how slow, I would select Return To Surface, and then hit my galaxy map hot key, and the map would usually come up, right about the time that I reached the surface, sometimes a little before that. It is a very noticeable delay.

After the game has run for about 5 minutes, things seem to be better. I does load faster, usually with only a second or two delay, but I have noticed that there is more of a delay for the galaxy map in the 2.2 patch.
 
good to hear, but if you're getting that data faster and I'm getting it slower..  What the h is going on server-side?

AFAIK almost all of the galaxy map is client-side.

Do you have lots of stored modules, ships or bookmarks?
 
Coming out of hyperspace takes notably longer. Yes, I know they want us to see how pretty it is, and I would gladly accept variable lengths of time spent there based on the distance of the jump. But I've come out of 30ly jumps faster than 4 ly jumps more than enough times to say this isn't the case.

Dropping in to orbital cruise takes eternity.

Dropping into glide takes eternity.

And yes, the Gal Map and System Maps take even longer.

I'm sure these are things that will be worked out as downloads taper off and they continue to kick the servers to figure out what's getting gummed up there as well.

In the mean time, please stand by... ... ... ...
 
AFAIK almost all of the galaxy map is client-side.

Do you have lots of stored modules, ships or bookmarks?

yes, a lot of bookmarks. But before the release it was never this slow. I could hit "launch" and have my next bookmark selected and back in the cockpit before my ship was released from the docking clamps. Now it's so slow if I looked at the map while undocking I'd get blown up for loitering!
 
I honestly believe galmap and mission board slow downs are on the user side, equipment probably.

I've never had an issue with either of the maps or the mission board not loading in less than 10 seconds. Usually they pop up in less than 3, with the mission board taking the longest on occasion.
 
Small update:

Played again last night. Every board continues to be uber-slow in opening, including Commodities - at 2 different stations, opening the commodities board the first time took ~50 seconds @ one station, and ~70 seconds @ other station. (Not exaggerations. I timed it.) And the game is NOT frozen - i continue to hear the sound fx, and see the game clock (upper right) ticking the time away.

And if this is related to user equipment, then note that I have not changed my equipment in months. This never happened before 2.2.
 
Last edited:
I honestly believe galmap and mission board slow downs are on the user side, equipment probably.

I've never had an issue with either of the maps or the mission board not loading in less than 10 seconds. Usually they pop up in less than 3, with the mission board taking the longest on occasion.

Fair enough, it may well be that 2.2 is tickling something on my rig that 2.1 didn't, but it's a really radical change from my perspective and my machine isn't exactly low end. (it's something of a monster, actually)

There's still worth in trying to find out exactly WHAT 2.2 is tickling that 2.1 wasn't, because if it's happening to me on this kit, it may be happening to others too and if there's a fix or a workaround it's worth exploring. Bottom line is that for me, on this hardware and software, in 2.1 the various boards and particularly the galmap were sufficiently responsive that I didn't really notice any delay. With 2.2 I'm glaring at the screen tapping my foot on exactly the same rig, the same underlying OS and the same net connection. So SOMETHING changed, and the only change I made was to download 2.2.
 
I honestly believe galmap and mission board slow downs are on the user side, equipment probably.

I've never had an issue with either of the maps or the mission board not loading in less than 10 seconds. Usually they pop up in less than 3, with the mission board taking the longest on occasion.

Core i7, 32 GB RAM, internal PCIe SSD, 60x6 internet, clean install of Win 10 less than two weeks old. I doubt it's my equipment.
 
Core i7, 32 GB RAM, internal PCIe SSD, 60x6 internet, clean install of Win 10 less than two weeks old. I doubt it's my equipment.

Cool. I've just powered up something similar. Took me months to buy each piece and put it together: i7, 32Gb RAM, GTX 1060 3Gb - Standard SATA and BT Internet. Installed on Tuesday, played Elite yesterday, and for me, everything was opening up instantly. I've never seen it so fast (I've always played it on i5/Intel 4600 before - 10-20fps) now I'm locking at 60fps 2560x1280 and graphics set to High.

So whatever is bugging it, it's not universal.
 
Core i7, 32 GB RAM, internal PCIe SSD, 60x6 internet, clean install of Win 10 less than two weeks old. I doubt it's my equipment.

Huh..

I'm i5 2500k @ 4.3 constant, 8gb RAM, 980 GTX, SSD on 100x15 internet with a likely corrupted install of Win 10.

Playing last night, checking out passenger missions, doing the normal minor-faction support missions and outfitting an Anaconda (After flying my python back from Farseer, so galmap plotting) I didn't have a single window/menu that took longer than a handful of seconds to open.

I did, however, have one issue where I accidentally accessed the engineer info from the status panel and, for some reason, couldn't exit out of the menu for a few minutes due to some kind of UI focus issue that wouldn't let me click the "back" button.

I'm really curious now about what this could be caused by.
 
Core i7, 32 GB RAM, internal PCIe SSD, 60x6 internet, clean install of Win 10 less than two weeks old. I doubt it's my equipment.

Dual i7's, 32G RAM, OS and drivers are on the SSD, everything else on the 3x1TB HDDs in RAID5 (stripe size optimized for the bandwidth of the triple PCIe controllers) 2x high-end NVidia cards in SLI, gigabit internet over fiber... So yeah, I doubt it's my equipment either :)
 
Huh..

I'm i5 2500k @ 4.3 constant, 8gb RAM, 980 GTX, SSD on 100x15 internet with a likely corrupted install of Win 10.

Playing last night, checking out passenger missions, doing the normal minor-faction support missions and outfitting an Anaconda (After flying my python back from Farseer, so galmap plotting) I didn't have a single window/menu that took longer than a handful of seconds to open.

I did, however, have one issue where I accidentally accessed the engineer info from the status panel and, for some reason, couldn't exit out of the menu for a few minutes due to some kind of UI focus issue that wouldn't let me click the "back" button.

I'm really curious now about what this could be caused by.

I'm sure the heart of these issues - both the maps, along with extended Orbital Cruise times, SC drops, Crew Lounge, Mission Board, and other elements taking longer than usual to update lie either at the servers themselves, or in the network somewhere. I'd love to Wireshark the servers for an hour and see what turns up. It's also entirely possible the issue is neither in the host or the client, but somewhere in the middle.
 
Back
Top Bottom