The problem with the bmp is still the same: that it won't support projections (i.e. stretching) and zooming very well. If you want to use a bmp, up to lets say 64 times zoom, you need a [imath]\left( 300 \text{ px} \right) \times 64 \approx 20\,000 \text{ px}[/imath] map. It doesn't really work out in any practical way. I would say there's a good reason MartinS switched to vector maps in Orbiter2010. ?
As for 3D map, I think the Map3D MFD I linked in my previous comment does a well enough job at it, making it unnecessary to try to replicate.
Apropos Videnie, have you checked this out?
https://www.orbiter-forum.com/threads/orbits-came-for-the-orbiter.33870/
It does approximately the same, but for the Orbiter2016 with D3D9 client.
And by the way, if you are interested in a map showing your history track instead of the predicted track, then be sure to check out my
Travelmap MFD.
---
To prove my point, here is a quick implementation of the orthographic ("3D view") projection:
View attachment 27042
The problem is that I have to discard half of the globe. All the other projections always show the entire globe's surface, while the 3D view one has to hide half of it, which would mess up current implementation of the daylight, orbital tracks, grid lines, and general map drawing.
Then you have the added problem of: what should the track show in 3D? Should it be along the ground, or 176 km above the surface, as in this example?
But please do come with your suggestions and hints! If you argue enough for it, it could be that I try to implement it in the end. ?