Random Game Crash when using Roller Fieldwork (infinity)

[modelleicher]

Version

8.0.0.4

Game Version

1.4.0.0

SP/MP

SP (Singleplayer)

What happened?

When Rolling the Game crashes randomly. It freezes then closes completely. Log contains Callstacks.

On 3 out of 4 fields it crashed, during the first two times about 40% into the field, the third field did not crash and in the fourth field it crashed 20meters before the end point.

How can we reproduce this?

It seems to happen randomly when rolling a field. I have not played with Courseplay long enough to do many tests with other equipment - but cultivating and harvesting worked 100% so far - rolling was 3 out of 4 a crash.

Vehicles used:
Basegame Zetor Forterra HSX 140
Özdöken RZ950 roller https://www.farming-simulator.com/mod.php?mod_id=305467&title=fs2025

Fields used where created ingame using a plough and are not where actual field definitions are. (not tested if that plays a role yet - trying to be as complete as possible in regards to information of the save)

Can't confirm if it only happens with that roller either - might have to do more testing but since I do have Log Errors maybe thats enough to figure out whats going on.

What did you expect to happen?

No crash

Attach your log.txt!

log.txt

Screenshots

No Screenshots needed to describe this issue

[Tensuko]

Did you had a mission running in the mean time or finished one (took the money and stuff)

[Tensuko]

Can you test it with 8.0.0.5?

[Tensuko]

Can't reproduce this with 8.0.0.5
Used roller on a complete field and nothing happened.

[pvaiko]

Another one with the infinity error, like #374

[modelleicher]

Sorry for the late response.

I did try to reproduce the issue with Debugs enabled but ran out of time.

I did try with other rollers and could not reproduce it at least within the same 4 fields. That does not mean I can conclusively say that its with this one roller only, but there's at least some evidence for that.

I did not have a mission running. I have not done any missions on that Savegame.

There are 3 clips of 3 of the crashes - I don't think they help anything.
But what they show is no coordinates/speed going crazy like in #374
https://www.youtube.com/watch?v=POv_7wz6GUI

Not sure if that is anything related but I got very similar infinity Callstacks during scripting animation stuff when the referencePoint for setDirection is exactly the same position and orientation as the object the setDirection is applied to.

I will test with the latest Version of Courseplay and see if I can reproduce the error.
The weird thing is that when it happened the first time it happened on 3 out of 4 fields.
I've tried reproducing it since then and it ran through 3 fields without Crash, thats when I ran out of time.

[modelleicher]

Alright I managed to reproduce it faster than I thought. It was running fine 4x but the 5th run it crashed again.

Here is the Log with all the Debug Info enabled

log.txt

And a short clip as I was recording the entire test
https://www.youtube.com/watch?v=Ml-EHZ9BRuA

[rangingwarr]

I also had a crash while using the roller with Course play. It started with the screen going black and the interface messing up and when I hit escape it went ahead and autosaved which made the save unplayable. It would take forever to load and I was getting less than 1fps and when switching to the vehicle that was pulling the roller I was once again met with the black screen followed by a crash. That time the speedometer was still visible and showing 621mph. I tried loading back in to sell the vehicle through the escape menu but when clicking on that tractor or the roller it wouldn't show the interface buttons to sell or view it. I went into vehicles.xml to have a look and discovered that all of the position data for both vehicles was showing '-nan(ind)' for all 3 axes. At that point I went ahead and just removed those two from the xml which fixed the save issue. I still have a copy of the broken vehicles.xml if it would be helpful for figuring out what's causing the issue.

[pvaiko]

Thanks folks, that's very useful info. I'm still wondering how CP could cause the vehicle position to jump to some "not a number", we never move vehicles by setting their coordinates, only through actual driving, so there's something else must also be going on there.