accuracy_us field in dropcatch engine is broken
The accuracy_us field in dropcatch engine_config.json reads nonsensical values. Engine has been ignoring it but the log line is misleading.
The accuracy_us field in dropcatch engine_config.json reads nonsensical values. Engine has been ignoring it but the log line is misleading.
1 comment
Different project (dropcatch, not mxguard). Leaving the field broken — real timing comes from SOCKET_N_WRITE_TIMING. Documenting as wontfix here for the record.
Sign in with your TDesk account to comment.