This post (and the following discussion)
https://forums.frontier.co.uk/showthread.php?t=175391&page=4&p=2696544&viewfull=1#post2696544
in the general forums got me curious enough to do some actual testing, trying to find out if the planets in E: D really are represented in 1:1 scale.
Simple, I thought, just compare actual in game size to the size reported in system map.
Then I saw someone already had beaten me to it:
https://forums.frontier.co.uk/showthread.php?t=175391&page=11&p=2698064&viewfull=1#post2698064
But something didn't seem quite right. Oh yes, IIRC the FOV setting value tells the vertical FOV, not horizontal. FDEV posting confirming that: https://forums.frontier.co.uk/showthread.php?t=168931&p=2582229&viewfull=1#post2582229
So, I took a couple of screenies of planets, wrote down the distance I took the screenies at and system map reported radiuses, calculated predicted planet diameters in pixels and compared that to the screenies. Results of 9 measurements showed a variable scale, from 0.908:1 to 1.13:1
Started thinking - are my measurements, maths or basic assumption wrong, or is the variable scale really a fact?
First measurements. I tested some High Metal Content Planets and Rocky Planets, radiuses between 1216 km and 4100 km, from distances between 4960 km (4.96 Mm) and 26500 km (25.6 Mm). Rounding error in having the distance (in most cases) at 100 km accuracy proved to be negligible. I also trust the pixel counts Photoshop Elements gives from zoomed-in, unedited full screen screenshot. Conclusion: measurements are fine.
Then maths.
Let's denote:
half of the viewing angle of the planet = α
FOV = vertical field of view in degrees (= 60 if FOV slider set at max)
calculated planet diameter in pixels = X
Vres = vertical screen resolution in pixels
We get:
tan α = radius/distance
X/Vres = 2α/FOV <=> X= 2α*Vres/FOV
Looks legit to me.
We're left with the basic assumptions.
When drawing the following diagram (slightly different version), I noticed that the assumption "tan α = radius/distance" is actually false. A few test calculations showed that once distance becomes greater than 10*radius, the error in calculated diameter falls below 1% though.
View attachment 55769
From the pic we see that when using r/D as tan α, we actually calculate angle β. Correct value for angle α comes from sin α = r/D .
This correction reduced the observed variation of scale to be from 0.903:1 to 0.996:1 .
Weird thing here is that of the 9 measurements I made, 3 were of the same planet (r = 2531 km), at 3 different distances. Resulting scales were:
D = 26500 km => 0.903:1
D = 8290 km => 0.928:1
D = 4960 km => 0.996:1
How come that the closer to the planet you go, the closer the scale appears to 1:1 ?
Is the fisheye effect the culprit (objects do become distorted near screen edges)?
And has that been taken into account by making all planets actually to be 90% of their real size, so they look like 100% when close enough, because of the fisheye effect?
Additional point: I have set my FOV at 64.00000 in the config file, but surely the difference in fisheye effect strenght vs. FOV of 60.00000 is negligible?
https://forums.frontier.co.uk/showthread.php?t=175391&page=4&p=2696544&viewfull=1#post2696544
in the general forums got me curious enough to do some actual testing, trying to find out if the planets in E: D really are represented in 1:1 scale.
Simple, I thought, just compare actual in game size to the size reported in system map.
Then I saw someone already had beaten me to it:
https://forums.frontier.co.uk/showthread.php?t=175391&page=11&p=2698064&viewfull=1#post2698064
But something didn't seem quite right. Oh yes, IIRC the FOV setting value tells the vertical FOV, not horizontal. FDEV posting confirming that: https://forums.frontier.co.uk/showthread.php?t=168931&p=2582229&viewfull=1#post2582229
So, I took a couple of screenies of planets, wrote down the distance I took the screenies at and system map reported radiuses, calculated predicted planet diameters in pixels and compared that to the screenies. Results of 9 measurements showed a variable scale, from 0.908:1 to 1.13:1
Started thinking - are my measurements, maths or basic assumption wrong, or is the variable scale really a fact?
First measurements. I tested some High Metal Content Planets and Rocky Planets, radiuses between 1216 km and 4100 km, from distances between 4960 km (4.96 Mm) and 26500 km (25.6 Mm). Rounding error in having the distance (in most cases) at 100 km accuracy proved to be negligible. I also trust the pixel counts Photoshop Elements gives from zoomed-in, unedited full screen screenshot. Conclusion: measurements are fine.
Then maths.
Let's denote:
half of the viewing angle of the planet = α
FOV = vertical field of view in degrees (= 60 if FOV slider set at max)
calculated planet diameter in pixels = X
Vres = vertical screen resolution in pixels
We get:
tan α = radius/distance
X/Vres = 2α/FOV <=> X= 2α*Vres/FOV
Looks legit to me.
We're left with the basic assumptions.
When drawing the following diagram (slightly different version), I noticed that the assumption "tan α = radius/distance" is actually false. A few test calculations showed that once distance becomes greater than 10*radius, the error in calculated diameter falls below 1% though.
View attachment 55769
From the pic we see that when using r/D as tan α, we actually calculate angle β. Correct value for angle α comes from sin α = r/D .
This correction reduced the observed variation of scale to be from 0.903:1 to 0.996:1 .
Weird thing here is that of the 9 measurements I made, 3 were of the same planet (r = 2531 km), at 3 different distances. Resulting scales were:
D = 26500 km => 0.903:1
D = 8290 km => 0.928:1
D = 4960 km => 0.996:1
How come that the closer to the planet you go, the closer the scale appears to 1:1 ?
Is the fisheye effect the culprit (objects do become distorted near screen edges)?
And has that been taken into account by making all planets actually to be 90% of their real size, so they look like 100% when close enough, because of the fisheye effect?
Additional point: I have set my FOV at 64.00000 in the config file, but surely the difference in fisheye effect strenght vs. FOV of 60.00000 is negligible?
Last edited: