So a couple of days ago, I started to explore properly.
Bought my advanced scanner, detailed surface scanner, fuel scoop, etc.
Headed out, currently going through the Pegasi sector, so not even out of populated space yet.
What has been really bugging me however, is the 'lagginess' of the scanner/server.
For example the system i just scanned...
Land at start,
Start turning away from star, while already deploying my scanner. (And start counting...)
5 seconds or so of charging later, the scanner tells me complete.
(I'm unfortunately getting used to this now), so check my Navigation list.
Now I see only 1 USS, not even the start I landed at.
Eventually, now I've counted to 37, I get the first
"Discovered 1 new Astronomical object"
"Discovered 38 new Astronomical objects"
Ok, so off to next star...
Start turning away from star, while already deploying my scanner. (And start counting...)
5 seconds or so of charging later, the scanner tells me complete.
8 seconds after scanning complete:
"Discovered 1 new Astronomical object"
11 seconds after scanning complete:
"Discovered 38 new Astronomical objects"
Given that if you simply land, scan while pointing at next star, and immediately hit jump, I wonder how much of the data over the past few days that ive scanned I have actually lost.
I verified in one system that if you do this and it lags, and you jump too soon, if you jump back to the system you just scanned, it is NOT explored.
To Clarify, I mean the Navigation panel lists no objects full stop.
When correctly scanned and processed, it will list however many "Unexplored" entries.
I highly doubt my pc/connection has anything to do with it, but before anyone accuses me of having a poor connection/etc:
Please, please please fix the lag!
It depresses me to think how much exploration data I have lost, by being too efficient in scanning and jumping to the next system.
I know this must be either a bug or just plain lag, because when its working properly, you instantly discover the objects when the scanner finishes scanning.
This is really putting me off spending too much more time exploring until I can trust the server to actually process my exploration data in a sensible timeframe (A couple of seconds lag would be acceptable, but not 10+!)
EDIT:
There seems to be 2 distinctly different lag issues here, which I've been keeping track of over the past 100 or so systems explored:
1: The lag between your Scanner being 'Complete' and you actually getting the 'Discovered X ...' popup. (Happens to me about 50% of the time)
2: I assume the response lag, where your scanner is 'Complete', you got the 'Discovered X ...' popup, but your Navigation list still shows no Unexplored objects. (Happens to me about 20% of the time)
Bought my advanced scanner, detailed surface scanner, fuel scoop, etc.
Headed out, currently going through the Pegasi sector, so not even out of populated space yet.
What has been really bugging me however, is the 'lagginess' of the scanner/server.
For example the system i just scanned...
Land at start,
Start turning away from star, while already deploying my scanner. (And start counting...)
5 seconds or so of charging later, the scanner tells me complete.
(I'm unfortunately getting used to this now), so check my Navigation list.
Now I see only 1 USS, not even the start I landed at.
Eventually, now I've counted to 37, I get the first
"Discovered 1 new Astronomical object"
"Discovered 38 new Astronomical objects"
Ok, so off to next star...
Start turning away from star, while already deploying my scanner. (And start counting...)
5 seconds or so of charging later, the scanner tells me complete.
8 seconds after scanning complete:
"Discovered 1 new Astronomical object"
11 seconds after scanning complete:
"Discovered 38 new Astronomical objects"
Given that if you simply land, scan while pointing at next star, and immediately hit jump, I wonder how much of the data over the past few days that ive scanned I have actually lost.
I verified in one system that if you do this and it lags, and you jump too soon, if you jump back to the system you just scanned, it is NOT explored.
To Clarify, I mean the Navigation panel lists no objects full stop.
When correctly scanned and processed, it will list however many "Unexplored" entries.
I highly doubt my pc/connection has anything to do with it, but before anyone accuses me of having a poor connection/etc:
I7 3770k, running at stock clocks.
32Gb 1800Mhz DDR3 Ram
2x128gb SSD (Raid 0) (Windows)
256Gb SSD (Where Elite is installed)
2x Intel gigabit nics, bonded with LACP, to managed switch, connected to a HA pair of pfsense firewalls.
2x 80/20 FTTC connections, with a VPN tunnel bonding both connections into a 160/40 pipe to my datacenter.
HA Pair of pfsenses in datacenter, each with gigabit WAN connection.
While in a game, and exploring, I see the following connections from the game:
Image PID Address Send (B/sec) Receive (B/sec) Total (B/sec)
EliteDangerous32.exe 9500 ec2-54-78-2-174.eu-west-1.compute.amazonaws.com 31 0 31
EliteDangerous32.exe 9500 ec2-54-78-160-94.eu-west-1.compute.amazonaws.com 16 0 16
EliteDangerous32.exe 9500 ec2-54-78-4-44.eu-west-1.compute.amazonaws.com 2 0 2
Only one of those hosts actually responds to pings, but here it is:
Pinging ec2-54-78-4-44.eu-west-1.compute.amazonaws.com [54.78.4.44] with 32 byte
s of data:
Reply from 54.78.4.44: bytes=32 time=20ms TTL=42
Reply from 54.78.4.44: bytes=32 time=22ms TTL=42
Reply from 54.78.4.44: bytes=32 time=21ms TTL=42
Reply from 54.78.4.44: bytes=32 time=20ms TTL=42
Ping statistics for 54.78.4.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 22ms, Average = 20ms
32Gb 1800Mhz DDR3 Ram
2x128gb SSD (Raid 0) (Windows)
256Gb SSD (Where Elite is installed)
2x Intel gigabit nics, bonded with LACP, to managed switch, connected to a HA pair of pfsense firewalls.
2x 80/20 FTTC connections, with a VPN tunnel bonding both connections into a 160/40 pipe to my datacenter.
HA Pair of pfsenses in datacenter, each with gigabit WAN connection.
While in a game, and exploring, I see the following connections from the game:
Image PID Address Send (B/sec) Receive (B/sec) Total (B/sec)
EliteDangerous32.exe 9500 ec2-54-78-2-174.eu-west-1.compute.amazonaws.com 31 0 31
EliteDangerous32.exe 9500 ec2-54-78-160-94.eu-west-1.compute.amazonaws.com 16 0 16
EliteDangerous32.exe 9500 ec2-54-78-4-44.eu-west-1.compute.amazonaws.com 2 0 2
Only one of those hosts actually responds to pings, but here it is:
Pinging ec2-54-78-4-44.eu-west-1.compute.amazonaws.com [54.78.4.44] with 32 byte
s of data:
Reply from 54.78.4.44: bytes=32 time=20ms TTL=42
Reply from 54.78.4.44: bytes=32 time=22ms TTL=42
Reply from 54.78.4.44: bytes=32 time=21ms TTL=42
Reply from 54.78.4.44: bytes=32 time=20ms TTL=42
Ping statistics for 54.78.4.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 22ms, Average = 20ms
Please, please please fix the lag!
It depresses me to think how much exploration data I have lost, by being too efficient in scanning and jumping to the next system.
I know this must be either a bug or just plain lag, because when its working properly, you instantly discover the objects when the scanner finishes scanning.
This is really putting me off spending too much more time exploring until I can trust the server to actually process my exploration data in a sensible timeframe (A couple of seconds lag would be acceptable, but not 10+!)
EDIT:
There seems to be 2 distinctly different lag issues here, which I've been keeping track of over the past 100 or so systems explored:
1: The lag between your Scanner being 'Complete' and you actually getting the 'Discovered X ...' popup. (Happens to me about 50% of the time)
2: I assume the response lag, where your scanner is 'Complete', you got the 'Discovered X ...' popup, but your Navigation list still shows no Unexplored objects. (Happens to me about 20% of the time)
Last edited: