Ok, here's new build. Does this work any better ? BTW, check that "linear interpolation" is selected. The "cubic" doesn't work.
Thanks!
Some test results:
» Changed elevation to -6172 to make the flat area more visible (about 10 meters higher than the existing terrain). Slight adjustment to Pathfinders's location.
Correct visual altitude at the center of the area, incorrect visual as you move off center (drop off).
» Changed falloff from 50 to 100.
Displayed terrain above the logical terrain.
» Changed falloff to 0. Slight adjustment to Pathfinders's location.
Same as the first test. Correct visual altitude at the center of the area, incorrect visual as you move off center (drop off).
The mismatch seems to be affect displayed terrain only.
On all cases the DG drives around the same: climbs to center of the raised area, then drops gently. No noticealbe change to computed terrain when I changed falloff.
I understand that tile level (resolution) might be a factor here. Will test with larger ellipses.
__________________________________________________________________________________________________
» Changed syntax to Ellipse -6172 -33.220001 19.129999 2000 2000 (are drop off and angle values not used ?)
Good match between visual and computed altitude (DG is at the edge of the ellipse, Pathfinder is in the distance to the right)!
Works as expected
PS: -6172 is the altitude in meters, shown on the DG MFDs