Reto.GreenBow

No problems for me when I'm using your settings. Are you pressing CTRL SHIFT or ALT maybe? (maybe caps lock accidentally turned on?)

Did you make sure that DX12 is disabled? This setting is highly experimental and can result in crashes and performance problems depending on your system and drivers.

I tried that but had no problems with A and D in classic controls on a Warhawk. Maybe some other setting is interfereing. Can you send me your localsettings.ini (located in %USERPROFILE%\AppData\LocalLow\Heroes and Generals )?

Yes the test has ended. You can still post your logfiles here if you encountered an issue (see the responses to messages above).

Please contact support, they can check your account status and help you with further instructions. Link: http://support.heroesandgenerals.com/

You can paste your desription of the issue, the lofgiles and secreenshots here (use a spoiler section for the long logs).

That is a very wide interpretation of what I wrote. But of course that needs to be constantly monitored, not only since the vehicle update. However, for me in QA it is important to know if there is a bug involved or not: as I said, the matchmaker is not supposed to launch a mission that doesn't have at least one infantry squad per faction. So if you can provide examples of such missions I would be interested in that data.

Thanks for providing this screenshot with mission ID and build number. While there are no hard limits on the class composition of a battle, the matchmaker can not launch a mission without at least one infantry squad for all participating factions (this feature was added a while ago to prevent extreme scenarios like this). The ability to freely switch soldier class (re-introduced with the recent armor update) should also help to mitigate the issue, since players can now actively respond to a class imbalance within the mission and switch classes when needed, which adds a certain tactical gameplay layer. However, we in QA want to make sure that no bugs are involved with these extreme examples, so if you have more examples of missions where one or both factions started out with practically all non-infantry classes then please send me a PM (don't forget to include mission ID and build number).

Can this still be observed? If yes, please provide the mission ID again and also your player-live.log file (from right after the incident).

Try disabling DX12, this is experimental and not supported on all systems. It could easily be the cause of your observation.

Our logs indicate that the latest commit (Build 151852) got rid of the last cause for the rejoin-issue. We need more missions to be played though to be sure (or as sure as it gets), so keep them coming!

Can you explain a little more in detail what happened here? Did you see the battle report right after joining it? Was the mission resetting and did it have to be played again? PS: Keep the mission IDs coming, trying to find out a pattern. Include the build number too if you can please, it's really hard to find missions without having a build number.

Thanks, this issue was already reported, reproduced and forwarded.

The gun in the video above is adjusted for 200m. It would be expected that you overshoot when the target is closer. However, there is a known issue with the auto-adjustment getting sometimes "stuck" after switching between ammo types - I assume this is the issue that Vudu_guy is talking about. This doesn't seem to be the case in the posted video though (it would show an adjustment to 0 but still overshoot on a very close target if you had encountered that issue).

From a gameplay perspective it is important that you can't get an unfair advantage from rotating your ATs, because that obviously helps large Generals while smaller ones simply can't do that. The situation was that if you had a certain critical mass of ATs, you could indirectly bypass the rebuild timer by equipping "fresh" ATs while the others were rebuilding (which is called "AT rotation"). This weakness of the morale system was hotfixed in the mentioned update to 1.03 - it is what it says: a hotfix to directly address this issue, so it's clear that the solution is not perfect but the warserver-refactoring has to be finished first before we can make larger changes.