Version
8.1.0.3
Game Version
1.17.0.0
SP/MP
SP (Singleplayer)
What happened?
The auger wagon driver chooses its route so close behind a combine, that it crashes into the folded grain pipe that hangs over in the back. This happens when I have multiple "Case AF11" running with the elongated grainpipe and "Elmer's Haulmaster" towed by a BigBud. It also crashes into the outer edge of the grain header when using "MacDon FD261".
How can we reproduce this?
Have multiple combines running on the same field. Have a big tractor and big auger wagon unloading them. Wait for the unloader to navigate close to one of the combines to reach another combine to unload. It will crash into the outer edge of the header or crash into the overhanging grain pipe.
What did you expect to happen?
The navigation system should detect the colliding objects and avoid crashing into them.
Attach your log.txt!
I will hand in a log later, when I have a good clean log that reproduces this bug.
Screenshots
I will hand in a screenshot later, when I have a good clean situation that reproduces this bug
Version
8.1.0.3
Game Version
1.17.0.0
SP/MP
SP (Singleplayer)
What happened?
The auger wagon driver chooses its route so close behind a combine, that it crashes into the folded grain pipe that hangs over in the back. This happens when I have multiple "Case AF11" running with the elongated grainpipe and "Elmer's Haulmaster" towed by a BigBud. It also crashes into the outer edge of the grain header when using "MacDon FD261".
How can we reproduce this?
Have multiple combines running on the same field. Have a big tractor and big auger wagon unloading them. Wait for the unloader to navigate close to one of the combines to reach another combine to unload. It will crash into the outer edge of the header or crash into the overhanging grain pipe.
What did you expect to happen?
The navigation system should detect the colliding objects and avoid crashing into them.
Attach your log.txt!
I will hand in a log later, when I have a good clean log that reproduces this bug.
Screenshots
I will hand in a screenshot later, when I have a good clean situation that reproduces this bug