Aurora 4x

VB6 Aurora => VB6 Mechanics => Topic started by: Kytuzian on June 26, 2016, 10:23:40 AM

Title: Incorrect Active Sensor Range Detected
Post by: Kytuzian on June 26, 2016, 10:23:40 AM
I'm playing a game with multiple empires, and one of the empires has an active sensor with a fairly large range. However, when the active sensor is turned on, it their range as being significantly lower (like almost 8 times lower) than it actually is to the other empires in the system. Why is this?
Title: Re: Incorrect Active Sensor Range Detected
Post by: swarm_sadist on June 26, 2016, 12:55:40 PM
When estimating range of sensors, the EM sensitivity is unknown. The guessing empire uses their own sensitivity rating to estimate range. If the opposing empire has a very large EM Sensitivity rating compared to the player empire, then the difference in actual range and estimated range could be drastically different.

If the estimating empire upgrades their EM sensitivity rating, that estimate range will increase.
Title: Re: Incorrect Active Sensor Range Detected
Post by: Kytuzian on June 26, 2016, 03:22:40 PM
Ah. Thank you, that's definitely what's causing it.
Title: Re: Incorrect Active Sensor Range Detected
Post by: sublight on June 26, 2016, 03:37:15 PM
No, its worse than that. The game currently estimates detection range as the GPS x 10k km. In addition to not considering tech level differences this also overestimates the range of large resolution scanners while underestimating the range of small resolution scanners.
Title: Re: Incorrect Active Sensor Range Detected
Post by: Iranon on June 28, 2016, 04:57:28 AM
Yes, this seems odd.
Changing resolution increases GPS linearly, but only increases range by the square root.

With GPS and resolution known as implied by the format of sensor contacts, the range estimate should take this into account.
Title: Re: Incorrect Active Sensor Range Detected
Post by: iceball3 on June 28, 2016, 12:59:30 PM
Yes, this seems odd.
Changing resolution increases GPS linearly, but only increases range by the square root.

With GPS and resolution known as implied by the format of sensor contacts, the range estimate should take this into account.
We'll have to set this out as a Bug then, I believe.