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.
This commit is contained in:
Mat Sutcliffe
2022-01-07 18:26:54 +00:00
parent efb6a3211d
commit aa7da1de53

View File

@@ -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