Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Little]

Some odd behaviour when firing with hull machine guns after using the main gun, seemed like some successful hits weren't getting attack rolls on an enemy Panzer.

Edit: Seeing if bug carries over into new beta release.

[sudasana]

Player MGs won't have any effect on fully armoured targets. AI crew injuries and collatoral damage are not yet implemented.

[sudasana]

No crashes yet. Playing the newest beta. Campaign started as the UK during the battle of France. Having light snow as a weather pattern, wondering if this intended or not?
Edit: Crash during close combat. Crash occurred after a defending rifleman was destroyed. Driving a MK VI C tank. The crash didn't reproduce on reloading the save.

Yes - light snow is rare but possible at the start of that campaign!

The other bug has now been fixed in 1.0.5, it happened when there was a non-combat unit (like a truck) involved in close combat.

[sudasana]

New development build now available, incorporating improvements and fixes prompted by a few new active players:
https://www.armouredcommander.com/blog/2020/04/04/development-build-4-april-2020/

[High tyrol]

Bug found in the development version:

In the September campaign when firing at opal blitz 3-ton it crashes during the allied action phase while running the percentages based on the firepower delivered to the unit.  when I am using a 7TP.  Artillery had been called for this attack but they were not firing on the turns that it crashed. The first time the crash occurred I was able to get to the next turn when I reloaded the save. However, when I attacked it again the next turn it got stuck with a crash occurring whenever I load the save. It occurred on day 3 of my first game.

[sudasana]

Can you send the savegame to the email address in the readme? I haven't been able to reproduce this crash. I'll need the saved_campaigns\poland_campaign folder. Thanks!

[Little]

Been busy, found some idle moments. Tried the new dev build. Loaded up a campaign as France. Lots going on in the background. The black logging screen behind the main window filled up at the first battle, pasted the log below.

Spoiler (click to show/hide)

#1 (3.0): 47mm(HE) against Opel Blitz 3-ton in -1,-2
#2 (-17.0): 47mm(AP) against Opel Blitz 3-ton in -1,-2
AI DEBUG: SOMUA S35: no good scored attacks on target list
AI DEBUG: SOMUA S35 set disposition to: Combat
AI DEBUG: 2 possible attacks for SOMUA S35:
#1 (3.0): 47mm(HE) against Opel Blitz 3-ton in -1,-2
#2 (-17.0): 47mm(AP) against Opel Blitz 3-ton in -1,-2
AI DEBUG: SOMUA S35: no good scored attacks on target list
AI DEBUG: Opel Blitz 3-ton set disposition to: None
ERROR: could not play sound: 37mm_firing_01
b'That operation is not supported'
ERROR: could not play sound: 37mm_he_explosion_01
b'That operation is not supported'
AI DEBUG: SOMUA S35 set disposition to: Combat
AI DEBUG: 2 possible attacks for SOMUA S35:
#1 (3.0): 47mm(HE) against Opel Blitz 3-ton in -1,-2
#2 (-17.0): 47mm(AP) against Opel Blitz 3-ton in -1,-2
AI DEBUG: SOMUA S35: no good scored attacks on target list
AI DEBUG: SOMUA S35 set disposition to: Combat
AI DEBUG: 2 possible attacks for SOMUA S35:
#1 (3.0): 47mm(HE) against Opel Blitz 3-ton in -1,-2
#2 (-17.0): 47mm(AP) against Opel Blitz 3-ton in -1,-2
AI DEBUG: SOMUA S35: no good scored attacks on target list
ERROR: could not play sound: vehicle_explosion_00
b'That operation is not supported'

New wound system looks interesting, have yet to see it in action. The new results screen makes sense, will give more thorough feedback upon further playtesting.

[sudasana]

Ah I must have left some debugging logs activated in the last dev build. Nothing to worry about, and it gives you a little insight into what the AI is doing!

Edit: New development build now available, should not have the console spam in the background now:
https://www.armouredcommander.com/blog/2020/04/09/development-build-9-april-2020/

[sudasana]

Just a quick post to announce that Armoured Commander II is coming to Steam later this year:

https://store.steampowered.com/app/1292020/Armoured_Commander_II/

[Little]

Played through a day of the new dev build, will get more time through it as I can. No crashes or bugs yet.

Edit: New overrun mechanic makes sense. Had a critical heavy machine gun roll against me, did twelve damage yet no rolls against me. Intentional or bug of the damage system?

[sudasana]

Edit: New overrun mechanic makes sense. Had a critical heavy machine gun roll against me, did twelve damage yet no rolls against me. Intentional or bug of the damage system?

If you're buttoned up there's no risk of damage. Even if one of your crew has their hatch open, they'll usually be ok unless they're unlucky.

[Little]

Trying the new version 3 release! Field hospital seems like a great addition, nobody's been sent to it yet but it's a good thing to have in place. Still need a graveyard. Line of Sight could use better explanation in-game but adds a bit of variety and chase into combat. Only a couple days into my campaign, but seems all clear on the bug front so far!

[sudasana]

Good to hear! The record of past commanders and campaigns is coming in the Steam version, it didn't make sense to add it until after I finish all the changes to the campaigns, which may drastically change the base difficulty level and likely VP scores.

[Little]

Bug found: the Line of Sight Blocked that appears when you mouse over a unit or select them in targeting runs over the Fortified or Entrenched descriptor.

[sudasana]

I found that one too - I'll issue a fix shortly.

EDIT: Fixed now: https://www.armouredcommander.com/blog/2020/04/30/armoured-commander-ii-update-3-0-1/