Originally Posted by
mr_belowski
I've just testing this on pCars2 and I've been able to reproduce a bug, but I'm not sure if it's sufficient to cover what you're seeing.
There's a piece of validation on the gap-ahead / gap-behind calls, intended to prevent them playing if your race position has changed since the message was 'queued', or if the gap is very small relative to your current speed. This issue here is that validation is too strict - if either of the gaps (ahead or behind) is too small, it won't play the messages. This is compounded by the fact that being in the lead means the gap ahead is 0 (so no gap messages play) and being last means the gap behind is zero (so again, no messages play).
The upshot of all this is that it's far too likely for the gap messages to be considered invalid and not be played.
A fix for this will be in the next version of the app. Hopefully it'll address your issue