The problem is solved in latest patch. Thank you guys. You can close the ticket if you want now.

Hard to give you more info. I've uploaded a repro mission. Just getting in as commander, and turning the turret around, spams the RPT with the error I've mentioned. I'm assuming you've seen the RPT, right?

The amount of disk writing is so massive than the game is unplayable if some Striders are manned. It happened after 1.42 update. I have verified the installation with Steam. Everything seems fine.

Are you still unable to reproduce or have you stopped trying? Please ask me anything you need I still can't use the Strider.

I can't understand it is not being fixed. As you can see in the related reports, it affects any cargo seat in a helicopter too, both single and multiplayer.

I'm happy to confirm the bug is gone. Thank you. (I was a little worried not to see any mention of this in the changelog for 1.24 though.)

Thank you. I'll check it when it hit stable branch.

@ceeeb I'm not sure I follow. What do you mean by "works". Does the AI engage the enemy? Also, the ticket is about the current stable version, so I'm not sure if you are confirming that the bug is not present in dev branch, or if you are contradicting my report.

Thanks a lot ceeeb.

Thank you. My best guess is some of the patches fixed part of the problem (which is great), because now I can only reproduce the behaviour with one vehicle class: the Marshall. I've uploaded a repo mission as requested.

Please fix this. I based an entire game mode on having to tell friend from foe by yourself, and then I got this BS. Hours wasted.

It's unbelievable this hasn't like a million votes. The problem is not tecnically related to the landing procedure per se, but to bleading air speed. The same behaviour can be seen when a chopper flying at ~ 270 km/h gets near it final move waypoint. The bleeding speed starts at up to 700 meters from the waypoint position, because the pilot want to get there at a hover.