Ref T229, FS9 and XPlane adjustments for changed CInterpolationStatus

Ref T207, maybe MS should review the XP part
This commit is contained in:
Klaus Basan
2018-01-19 03:14:32 +01:00
parent 467f8cbac9
commit fae5e6ac0a
2 changed files with 6 additions and 4 deletions

View File

@@ -188,8 +188,8 @@ namespace BlackSimPlugin
hints.setLoggingInterpolation(this->getInterpolationSetup().getLogCallsigns().contains(m_callsign));
const CAircraftSituation situation = m_interpolator.getInterpolatedSituation(-1, m_interpolationSetup, hints, status);
// Test only for successful interpolation. FS9 requires constant positions
if (!status.didInterpolationSucceed()) { return; }
// Test only for successful position. FS9 requires constant positions
if (!status.hasValidSituation()) { return; }
sendMultiplayerPosition(situation);
sendMultiplayerParamaters();

View File

@@ -342,8 +342,10 @@ namespace XSwiftBus
BlackMisc::Simulation::CInterpolationAndRenderingSetup setup;
BlackMisc::Simulation::CInterpolationStatus status;
const auto situation = plane->interpolator.getInterpolatedSituation(-1, setup, plane->hints(), status);
if (! status.didInterpolationSucceed()) { return xpmpData_Unavailable; }
if (! status.hasChangedPosition()) { return xpmpData_Unchanged; }
if (! status.hasValidSituation()) { return xpmpData_Unavailable; }
//! \fixme KB 2018-01 commented out with T229. Change detection needs to go somewhere else
// if (! status.hasChangedPosition()) { return xpmpData_Unchanged; }
using namespace BlackMisc::PhysicalQuantities;
using namespace BlackMisc::Aviation;