FS19 Courseplay for FS19 v6.03.00024
6.03.00024 Bridge and proximity sensor fixes
Goal node elevation fixed (#6665)
Proximity sensor directly on the back of the combine/chopper
allowing for the unloader to get closer.
When driving over non-level bridges, the controlled node isn’t vertical and
the goal node was positioned on the ground level which is way below the vehicle.
Due to this, the goal’s position in the controlled node’s reference wasn’t accurate
in this situation, seemed to be a lot closer when driving uphill, lot further when
driving downhill. Uphill goal being too close caused oscillations in PPC.
Moved the goal point on the level of the vehicle (controlled node), so the error
caused by the non-vertical controlled node is negligible.
Few proximity sensor and vehicle size fixes
Proximity sensor sits on the back of the combine now
fixed pathfinder vehicle data rectangles, clarified the
misconception that the direction node is always on the root node,
it is not, the direction node is the turning node, usually sits
between the non-steered wheels.
6.03.00022 Minor fixes
fix all hybrid A* pathfinder failing
fix reset fill level after making pocket
6.03.00021 Course generator and turn fixes
No extra headland circle (#6605)
Fixed the calculation of the headland/middle transition.
If the center mode is lands, there is still a small chance that
an almost full circle connecting track will be added if the starting
point is very close to the start/end of the first working row of the
lands pattern.
Partial fix for #6383
do not add straight section to turn end to align if there is no towed
implement
if turn on field enabled but there’s no space to turn (must reverse), use
the legacy wide turn (which is also buggy a bit).
if you don’t want your sprayers boom hit obstacles outside the field,
use a headland.
6.03.00020 Mode 2/3 improvements
Wait before starting the next row if the rendezvous point is close to the row end.
use A* to calculate distance to combine before the
rendezvous.
combine notifies unloader on missed rendezvous, unloader
re-plans route
try to approach combine waiting after backing out of the fruit
from the rear so we won’t cut in front of it.
don’t slow down around rendezvous when discharging already
don’t ask for a rendezvous when the combine is not willing to,
for example when unload is disabled on the first headland.
won’t initiate new rendezvous until the combine cancels the current one
move up rendezvous points close to row end
pipe in fruit map changed to have a 20 m buffer at each end of the
row to account for non-perpendicular headlands.
fixed offsets when calculating target to combine, sometimes it
used the side offset as front offset.
make sure to reset 95% full limit after making pocket
added safety margin to the calculation of the distance until full
All this to avoid the situation where the combine stops before reaching
the rendezvous point because it thinks it is full (although only 95%)
only considers unloaders actually waiting for assignment,
ignore the ones on unload course for example when a combine
is looking for an unloader
if an unloader is already assigned to a combine, only it is
waiting for the combine to become ready for unload (for example
due to fruit in pipe), assign the same combine to it. This
should probably be refactored, adding a new state for the unloader,
like WAITING_FOR_COMBINE_TO_BECOME_READY or so.
