[Bug]: Standard and possibly fast Trip pacing can cause destination exits to be announced before they're close enough to signal for them

[stefenhudson]

What happened?

If trip pacing is set to standard and my velocity is 45 or greater, destination exits can be announced before they're actually close enough to signal for them.

The attached log shows me starting with a fresh career with trip pacing set to standard. I start a route and approach my destination exit at around 54 MPH. The game reports that the destination exit is in 8 miles. When I attempt to signal for the exit, the game reports that there are no exits coming up.

I then quit to the main menu and start the route over, this time approaching the exit at around 42 MPH. This time, the game reports that the destination exit is in 5 miles and signaling is successful.

I then quit to the main menu and set trip pacing to relaxed before starting the route over again, this time approaching the destination exit at around 56 MPH. The game reports that the destination exit is in 5 miles, and signaling is successfull.

What were you doing right before?

No response

Game version

1.8.6 development build

Game log

game.log

[Orinks]

The fix is now available for review in draft PR #119: #119

The exact announced destination exit remains actionable for a 25-second real-time response window even if slowing shrinks the normal approach window. Passed, mismatched, and expired exits remain rejected; expiration allows a fresh closer callout, and a nearer optional stop cannot steal the destination-exit response.

Verification passed at Standard 54 mph and Fast 56 mph with a real pygame X press after five seconds, plus expiry/reannouncement, passed-exit, competing-stop, cruise/ramp, smoke, complete serial pytest, accessibility-agent, and visible NVDA/SAPI desktop checks. The desktop transcript confirmed the five-mile callout, successful signaling about three seconds later, and ramp entry without “No exit coming up.”