From aa7da1de53478df72be5227a52bac2b9b8d4ea7e Mon Sep 17 00:00:00 2001 From: Mat Sutcliffe Date: Fri, 7 Jan 2022 18:26:54 +0000 Subject: [PATCH] Increase number of situations stored per remote aircraft With 5Hz updates and a maximum offset of 6s, we need to store at least 30 situations to guarantee we're not throwing away situations that we haven't even used yet. There is probably a smarter way, like keeping situations based on their age rather than quantity, or letting the consumer remove them after they are no longer needed. --- src/blackmisc/simulation/remoteaircraftprovider.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/blackmisc/simulation/remoteaircraftprovider.h b/src/blackmisc/simulation/remoteaircraftprovider.h index 12e346f92..5e14e6938 100644 --- a/src/blackmisc/simulation/remoteaircraftprovider.h +++ b/src/blackmisc/simulation/remoteaircraftprovider.h @@ -45,8 +45,8 @@ namespace BlackMisc class BLACKMISC_EXPORT IRemoteAircraftProvider : public IProvider { public: - static constexpr int MaxSituationsPerCallsign = 6; //!< How many situations we keep per callsign - static constexpr int MaxPartsPerCallsign = 20; //!< How many parts we keep per callsign (we keep more parts than situations as parts can just come in) + static constexpr int MaxSituationsPerCallsign = 50; //!< How many situations we keep per callsign + static constexpr int MaxPartsPerCallsign = 50; //!< How many parts we keep per callsign static constexpr int MaxPartsAgePerCallsignSecs = 60; //!< How many seconds to keep parts for interpolation //! Destructor