The current macro feature is quite simple and could be improved. Some games (pCars2, RF2, ???) expose pit-request-state - macro logic should check this before triggering the pit-toggle button. So saying 'box this lap' can be safely ignored (with a 'we're already expecting you' response) in some cases. Can also add a 'cancel pitstop' voice command.
The macro manager could do a better job of tracking the state of the pit menus. This is risky because it's easy for them to get out of sync, but it's worth putting something together to see how it goes. The app could track which strategy is select, and what changes its made to it - specifically what fuel's been added.
State tracking needs careful consideration - perhaps it's only safe to track the fuel added and modify the behaviour of the next fuel-add call where the user doesn't select a different strategy
major overhaul of the macro system - it's now more flexible and generic, allowing lots of cool things. The main limiting factor is now the speech recogniser
The current macro feature is quite simple and could be improved. Some games (pCars2, RF2, ???) expose pit-request-state - macro logic should check this before triggering the pit-toggle button. So saying 'box this lap' can be safely ignored (with a 'we're already expecting you' response) in some cases. Can also add a 'cancel pitstop' voice command.
The macro manager could do a better job of tracking the state of the pit menus. This is risky because it's easy for them to get out of sync, but it's worth putting something together to see how it goes. The app could track which strategy is select, and what changes its made to it - specifically what fuel's been added.
State tracking needs careful consideration - perhaps it's only safe to track the fuel added and modify the behaviour of the next fuel-add call where the user doesn't select a different strategy