Sorry, did you already try to reinstall and this is still happening or are you asking? If you're on Steam I would try to verify files before reinstalling just incase

Unable to repro this in the latest beta version, can you try it there and see if you get the same error?

Can you try this on the latest beta version of the game? There may be something wrong with 1676 that's interfering with the scenario as I can't reproduce it in the latest version.

To "validate" an older community scenario you can try to update the DB (the scenario you linked is using 478 and we ...

For a normal auto-attack (Just F1) you only have to hold F1 if you're lassoing multiple targets. For a single target just press F1 to activate the targeting cursor and left click on the target. Let me know if I'm missing something

Thanks, logged as 0016988

Thanks, logged as 0016984

This is WAD as far as I can tell, its ok if the LSM is able to move ashore a bit to land units/cargo. Its stopped by the terrain before its able to move inland. If you have a more egregious example please share it

Thanks!

What version of the game are you running?

Does this still happen if you set unit pathing to "Direct"?

Hi, this should be fixed in our current beta version

Seems like this may just be due to the scenario, I can't repro it

Yes, this is a product of the scenarios start date being moved ahead after the satellites detected these contacts

Thanks, logged as 0016967

Thanks, logged as 0016964

This is WAD, the scenario designer just decided to use negative values. In these scenarios getting a 0 or positive score is enough to win. It doesn't mean instant victory

This isn't a bug, it needs to be reported here- https://forums.matrixgames.com/viewtopic.php?t=373623

For now you'll have to take into account the cloud layer and change the mission altitude accordingly

Logged as 0016943

Logged LOAD/DOC issues as 0016942

Hmm, adjust the "collective responsibility" option under side options and see if that changes the behavior