Yes, there is an API compatibility problem that is causing the offset in longitude. The problem will apply atleast BaseSyncMFD and IMFD. The problem can be fixed by code modifications and that's probably the best course of action. Every program that is using oapiGetPlanetTheta() to compute a planet orientation may suffer about this problem. Programs should rely on oapiGetPlanetObliquityMatrix() instead.It seems to be that the margin of error is exactly 2.391° to the east wherever you are on mars. BasesyncMFD v2.1 shows the same mismatch.
Yes.Anybody here, who can confirm that there is a little mismatch on moon (little more than 4km at equator) caused of same reason?
The Earth is also effected. I don't know which precession parameter will effect in the magnitude of the error and it's not important at a moment.That there isn't a mismatch (or at least minimal) on earth?
No, not really. Planet axis precession support didn't cause it. It's not a side product. I suppose this could be more like an implementation error in addons rather than in the Orbiter itself.Is it a "result" of the new "feature" discussed here http://www.orbiter-forum.com/showthread.php?t=8185 ?
Yes, it will change in time with different rate in a different planets. It could be something like 0.0001 deg / yearAnd, important for me, is the mismatch constant of body or will it vary by time?
i think it may be crashing due to some "division by zero" error... i assume it wasn't made for landing without atmoosphere...
i use BaseSync for that... works just fine in 2010 too:thumbup:
I have released a new versions of BaseSyncMFD and IMFD. New versions should no longer suffer from the longitude offset issue. I haven't had time to test them, so, I would be happy if some one could test and confirm if they work properly.