Bug: Reduced Output Per Minute from Hub Due to Drone Latency
217 °C
Bug #163

Reduced Output Per Minute from Hub Due to Drone Latency

Status: In Progress
Priority:
High
Added by:
chronotactix
on April 7, '26
Assigned to:
Unassigned
Due date:
Reported for:
0.8.5 Auto

Steps to Reproduce

No steps to reproduce

Explanation

There's a minor bug (unless theres latency I dont see) introduced with the new drone system, as machines appear to be creating a small latency every 4th drone, reducing the output per minute from the hub, if the hub is stationed away from the building. I ran this test at 3 different distances, and for 10minutes each (to account for starting travel time):

Directly next to building (1 space apart for cranes) - 75/m as expected
On the other side of a large island, or approximately 3/4 of a large island away - 73/m
At max range, nearly on the opposite side of a second large island to the west. - 73/m

2 and 3 being the same output sense, as once the "line" is "balanced", they should have the same throughput. Both are slower than directly next to the hub though, I assume because the latency gap doesnt really occur with a minimal travel time, or is so close you dont see it normally (ive seen small bumps down to 74, and then back up).

2 and 3 would sometimes bounce to 74, but very shortly before coming back down to 73 (I assume due to rounding). Not a huge deal, but seemed worth reporting.

Watchers

Video Clips
Log Files

None

Device

No device information

[ #1 ] by
[ #2 ] by
[ #3 ] by
[ #4 ] by
[ #5 ] by
[ #6 ] by
[ #7 ] by
[ #8 ] by
Loading comments...
Loading comments...
8 comments loaded

You need to join this project to comment on issues. Join Project