Skip to content
This repository has been archived by the owner on May 23, 2023. It is now read-only.

Worker skips parts of the field with plow #6762

Closed
bojanh66 opened this issue Feb 1, 2021 · 4 comments
Closed

Worker skips parts of the field with plow #6762

bojanh66 opened this issue Feb 1, 2021 · 4 comments
Assignees

Comments

@bojanh66
Copy link

bojanh66 commented Feb 1, 2021

If you need any debug channel, let me know.
I am using latest version of CP.
Course is created with 5 headlands, started working from up/down, then headlands.

The white part of the field is unplowed, worker simply skips it.
FarmingSimulator2019Game 2021-02-01 12-55-38

@pvaiko
Copy link
Contributor

pvaiko commented Feb 1, 2021

I need your field definitions (https://github.com/Courseplay/courseplay/wiki#how-to-post-your-field-definitions) and a screenshot of the course generator when you created this course.

@bojanh66
Copy link
Author

bojanh66 commented Feb 1, 2021

cpFields.zip
FarmingSimulator2019Game 2021-02-01 16-50-37

@Commissar0617
Copy link

does it look similar to #6652 ??

@bojanh66
Copy link
Author

bojanh66 commented Feb 2, 2021

I dont think so, because i am using small plow and only 1 worker and it happens only on headland which is cutting up/down rows in half (take a look at Start position and next 4-5 rows)
If you see on the picture the limed part of the field is skipped by worker, only because headland is cutting those up/down rows.
I think worker should continue over the headland and finish the up/down row, but instead of that, once he reach headland that is cutting up/down row, he turns around and continue doing next row, so the other half of up/down rows stay unplowed.

pvaiko added a commit that referenced this issue Feb 4, 2021
Fixed connecting track between two blocks, making sure we do not
overshoot the starting waypoint of the up/down row when changing
from one block to the other.

Relevant only for complex fieldwork courses where the field has
to be split into multiple blocks.
@pvaiko pvaiko closed this as completed in 384b12d Feb 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants