Falcon BMS terrain
-
As I understand it -
Korea theatre is a 64 x 64 square, of which each segment is made from 16 x 16 tiles, giving an overall map of 1024 x 1024 tiles. Each tile carries a single terrain texture. Am I correct in assuming each tile is 1 kilometre x 1 kilometre, or do they actually measure something else?
TIA
-
Yes you are correct. Each tile represents a 1KM x 1KM of horizontal distance.
But know this - The Falcon projection is WAY off compared to RL, i.e what we consider in sim to be 1024 KM might be really less than that in RL, due to earth projection which isn’t taken into account.
-
Yes you are correct. Each tile represents a 1KM x 1KM of horizontal distance.
But know this - The Falcon projection is WAY off compared to RL, i.e what we consider in sim to be 1024 KM might be really less than that in RL, due to earth projection which isn’t taken into account.
Thanks for confirming.
My issue is with measurement in general. Using the F4SharedMem thingie, I am grabbing the position of my own F-16 and after some jiggery-pokery (not least of all remembering X is Y and Y is X) projecting it onto a 1024x1024 graphic representation (i.e. Red Dog’s Korea map image). On top of this also, I am drawing 30 mile rings (+46 pixels radius per ring remembering 1 pixel = 1 kilometre and 1 miles = 1.6 kilometers) around the bullseye location, and graphically everything is looking fine. My problem arises when I calculate my bullseye posit - the further from the bullseye location, the greater the error I am being left with. Angles are fine - if in-sim it says I am at bulls 236 for 46 miles, in my program it says I am bulls 236 for 54 miles (as an example) and if in-sim it says I am at bulls 131 for 120 miles, my program says 131 for 144 miles (off the top of the head examples).
In a nutshell, where am I going wrong?
Actually, I think I just answered my own question while typing this - I am thinking imperial miles when I should be thinking nautical miles… back to VS I go…
-
Yes that explains the gap
Falcon world is accurate compared to the airspace - I.e if you fly 1KM then it is really 1KM in the from space/time POV.
But, from land aspect, compared to RL you will usually have some error, depends on where in the theater you fly, error may be smaller or larger, that’s because projection is wrong.So if you are using a RL map as reference then don’t try to compare actual “Land positions”, as at some points on the map you will be wrong by a couple of miles usually.
-
Yep, I remember from years back a discussion about the projections, and Blueprint was offering to convert theatre terrains to proper projections with the SRTM data. I nearly used it for Panama until I realised I’d be starting afresh!
Thanks again for your input. :thumbs-up: