One issue that is pretty common that might actually be fixed already in 32b954ed77d69aa65b7f5c4bf2fe8052b761417c was that the AI would process the command more than once. This was caused mostly by lingering images as due to the dumb variables that limit the resize (which is very likely unnecessary now thanks to other changes that patched the large image process functionality) by giving the AI system the same image to act on despite it being old, causing the AI system to send multiple movements.
This change would request that any AI movements have a delay before they can be acted upon again, likely a frame or two to prevent sudden multiple movements.
If the capture rate change can go through, then this feature request can be dropped as the AI will now be more accurate, and this will have lower priority than what it has as of writing
One issue that is pretty common that might actually be fixed already in 32b954ed77d69aa65b7f5c4bf2fe8052b761417c was that the AI would process the command more than once. This was caused mostly by lingering images as due to the dumb variables that limit the resize (which is very likely unnecessary now thanks to other changes that patched the large image process functionality) by giving the AI system the same image to act on despite it being old, causing the AI system to send multiple movements.
This change would request that any AI movements have a delay before they can be acted upon again, likely a frame or two to prevent sudden multiple movements.
If the capture rate change can go through, then this feature request can be dropped as the AI will now be more accurate, and this will have lower priority than what it has as of writing