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

Selling active unloading tractor locks up combine #427

Closed
maddavo opened this issue Apr 10, 2014 · 5 comments
Closed

Selling active unloading tractor locks up combine #427

maddavo opened this issue Apr 10, 2014 · 5 comments
Assignees
Labels

Comments

@maddavo
Copy link

maddavo commented Apr 10, 2014

Situation:

  • Combine has requested a driver and a tractor has been assigned.
  • The assigned tractor is sold.

Problem:
The combine still has the tractor assigned to it - the "Send driver home" button doesn't clear it, nothing clears it, even resetting the course doesn't clear it. Only solution is to abort game.

I am using 0.449 but I didn't find any issue relating to this so I assume it is not addressed in latest version.

@sootysax
Copy link

This has also happened to me if the active tractor is reset while assigned to a combine.

@JakobTischler
Copy link
Contributor

@maddavo: Before the resetting/selling, activate debug channel 4, then after the error post the complete log.

@JakobTischler JakobTischler self-assigned this Apr 11, 2014
@JakobTischler JakobTischler added this to the Release v3.50 milestone Apr 11, 2014
@maddavo
Copy link
Author

maddavo commented Apr 18, 2014

Westbridge hills on field 16 - debug #4 as follows:

[...]
[dbg4 lp17789] BaseMission:removeVehicle() -> courseplay_manager:removeCourseplayersFromCombine("Schlueter 1500 TVL (#2)", nil)
data/vehicles/cars/car6.i3d (0.38mb in 34.92 ms)
[dbg4 lp23014] BaseMission:removeVehicle() -> courseplay_manager:removeCourseplayersFromCombine("Case IH Axial Flow 9230 Quadtrac (#1)", false)
[dbg4 lp23014]  .courseplayers ~= nil (1 vehicles)
[dbg4 lp23014] Case IH Axial Flow 9230 Quadtrac (#1): has 1 courseplayers -> unregistering all
[dbg4 lp23014] Case IH Axial Flow 9230 Quadtrac (#1): has 1 courseplayers

Edit by Jakob: code brackets for better readability

@JakobTischler
Copy link
Contributor

  1. As I stated above, post the complete log, not only part of it.
  2. Always post stuff like the log in code brackets - for better readability.
  3. Which build were you actually using during the last test? As we update often, we always need to know the user's build number.
  4. You sold/reset two vehicles: first a Schlüter, where no problems occured. Then a combine, where some problems occured (unsuccessful unregistering of an active unloading driver). This doesn't really correlate with your opening post, where you stated the problems occur when the tractor is sold.

Edit: I've reworked the resetting function once again. Try build 0468 and report.

@JakobTischler
Copy link
Contributor

Closed due to inactivity.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants