Autoloading logs sometimes puts them partially outside loading areas

[joscha999]

On Version 0.3.2.3 I encountered this problem:

Looking at the middle of the trailer there's one log that was apparently loaded on the back loading zone but too far forward and partially outside the second zone. It seems like the back of the ~6m log is at the same position as the shorter end pieces loaded just before.

This is using the Schwarzmüller Timber Trailer Semi but I'm not sure if it's related to it specifically.
I'm using two 6.2m long loading zones to load 6m logs without having them interfere when loading short logs - this worked fine but at some point this bug appeared (I'm not 100% sure but this might be related to log loading changes in 0.3.0.3).

Attached is my UA modsettings, log (though it doesn't seem like it has much information in this case) and the save. If you load the save and tab into the Semi and then hit ctrl + R to autoload this issue will occur (tested on my end, happens every time I load the save).

For obvious reasons this requires the Schwarzmüller Timber Trailer Semi, other mods should not be necessary to load/repro the issue.

2024_12_29_Autoload_Bug.zip

Thanks for looking into this!

[joscha999]

Adding more cases to this:

1. Driving forward and loading more logs after loading the save causes a bunch more logs to load weirdly.
2. After bringing away one load and taking more logs on this also happened with the forward loading zone:
   

[loki79uk]

I thought htis might happen now - are there some messages in the log like:

EXCEEDED LAST ADDED LOAD LENGTH

I think it was the change I made to improve distribution

[joscha999]

Not present in the log I sent in the zip nor in my current log where this definitely happened again after restarting the game a few hours ago.

[loki79uk]

Okay, I reproduced it. Tends to happen after loading the game with partially full trailer, or if moving to a new area because those new logs are not sorted by length vs those already loaded. I'm going to be away for a week or so, but I will see if I can solve it before I go.

[loki79uk]

I think should be fixed now in latest release https://github.com/loki79uk/FS25_UniversalAutoload/releases

Note that it can still happen after loading the old savegame for the fist time, but after unloading/reloading the logs it shouldn't happen again as the "last loaded length" is now saved as part of the savegame.

[joscha999]

After moving about 80 trees worth of logs I can confirm this is fixed - thank you!