You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the problem this feature/enhancement solves?
The amount of headland runs required is not always obvious or known for an implement
Describe the solution you'd like
Suggest the number of headland rows the field should have based on the implement & vehicle combined length if this is possible? This is maybe something that can't be done, but I think it would be a nice touch to offer this if possible. Then the correct headland can be used for pulling into a row without obstruction.
Forgot to add title - Suggest number of headland rows required for length of vehicle + implement being used
The text was updated successfully, but these errors were encountered:
@Tensuko I dadn't see that idea. Would be good if it could ever happen as a user has no idea what the length is, where as the game does, so a suggestion based on length would be excellent. perhaps to start with a just a box that tells the users the current vehicle length, just like there is for the vehicle width?
What is the problem this feature/enhancement solves?
The amount of headland runs required is not always obvious or known for an implement
Describe the solution you'd like
Suggest the number of headland rows the field should have based on the implement & vehicle combined length if this is possible? This is maybe something that can't be done, but I think it would be a nice touch to offer this if possible. Then the correct headland can be used for pulling into a row without obstruction.
Forgot to add title - Suggest number of headland rows required for length of vehicle + implement being used
The text was updated successfully, but these errors were encountered: