As you suggested reducing the Y Offset did the trick, but It's so different from Bing elevation that I had to reduce it to -95 (!!).
And, when I increase the map zoom level, the Mapbox horizon overlay again the "standard" map (with Bing elevation), just because it's so much different (Mapbox elevation data seem to be a lot scaled on Y axis).
Since it's really a shame not to be able to extend the horizon (it look way better), I tried again to use Mapbox, instead of Bing, for elevation but
1) with "OnlineMapsMapboxElevationManager" (instead of "OnlineMapsBingMapsElevationManager") I don't receive OnlineMapsElevationManagerBase.OnElevationUpdated" event.
I've subscribed a function in my class to "OnElevationUpdated" in this way:
private void Start()
OnlineMapsElevationManagerBase.instance.OnElevationUpdated += MyFunction;
but with "OnlineMapsMapboxElevationManager" script I don't get this event (with "OnlineMapsBingMapsElevationManager" I get it).
2) since Mapbox elevation data seem to be wrong, or too scaled, I don't know, at least in my area, I'd really like to be able to use Bing elevation data for the horizon.
I gave a look to Horizon2_OM3 script, but honestly I don't know how to modify it for Bing.
I know that to write a new script is quite an effort, but... any chances to have this script for Bing?
Maybe, could you write me a private message to talk about it?
3) I'm a bit confused how to use Google for elevation data (that, maybe, would be the best solution).
All the Google scripts must derive from Monobehaviour, so... how to use Google for elevation?