Posts made by JuliusBorisovBeamdog

While it would be absolutely good to have such a feature, we’re past the stage when the game can get substantial code changes. AAO stayed in Early Access between July 2019 and November 2021, and the also kept getting updates until July 2022. There was always a different feature or issue we worked on.

Hey, I don’t see a username silkyselfie, but please send me an email you use for the game (in a DM).

@stancollins

You just click the link, no need to install anything, you can use it as a site. You’ll need to register there ofc.

As for screenshots, I just Shift + Win key + S to take a screenshot of what I need and then save it in Paint 3D.

Similar to your other question/report, @stancollins, this looks rather like understanding how game controls/UI works. Those things might seem wonky to new players. Please join the Discord so that more people could help you. Also, it’s hard to provide commentary without screenshots of your situation.

https://discord.gg/RrpbBFX4ae

Just merged them!

Hello! I would suggest creating a Steam family and playing AAO as doodleflungee from your second account, thanks to Family Sharing.

https://store.steampowered.com/promotion/familysharing/%3Fl%3Drussian?l=english

Other than that, we can’t provide an extra copy to the second account.

I’ve merged them into a Steam one.

On a side note, I’ll be on X-mas holidays until Jan 6th, so future requests like this will have to wait until then. Thanks, and happy holidays to everyone!

All done now!

@Glasi You need to create a separate Commander Name on Steam and tell me, so that I could merge manually. Probably better send me a DM with all the info (e.g. emails used for both)

@Frunobulax The issue was fixed, so feel free to update your iPad.

It’s here! After a long wait (thanks for hanging in there), the fix for the Axis & Allies 1942 Online crash on iOS is being deployed via the App Store. So you can update as soon as Apple uploads the fix.

It’s here! After a long wait (thanks for hanging in there), the fix for the Axis & Allies 1942 Online crash on iOS is being deployed via the App Store. Update now—and get back to the battlefield!

So for other people running into the same issue:

https://play.google.com/store/apps/details?id=com.google.android.play.games

Launch it and click on the 3 dots top right
Click Settings, then scroll down to “Change account for games”
find the AAO entry, and press Change, click signout
launch game and it should ask for what phone account it should use to launch the game

We’ve been testing the fix with a select group of users from Discord. There is still one issue left affecting iPhones 16, which we’re trying to fix.

There is also a workaround (found by one of our testers): enable the Lockdown Mode on your iOS device, and then even the live (old) build of AAO will work without any of these issues.

This can be accessed on your device in Settings > Privacy and Security > Lockdown Mode.

More info on Lockdown Mode and for non-iPhone devices, visit this page: https://support.apple.com/en-us/105120

@Robbie_S Done now!

You can’t sign in with the iOS account. Create a new Commander name on Android, and send me a DM with both Commander Names, I’ll merge them manually.

I see new replies to this thread. Please follow my previous recommendation of joining Discord. If you don’t want to join Discord for some reason, and still would like a Steam key as a workaround, plese send me a DM with your iOS Commander Name.

I’ve noticed an influx of people with this problem over the weekend, for one reason or another.

We’re still working on the issue, it’s getting closer. If you join Discord, you’ll be able to get a special role related to the issue and get notified once we start a test. https://discord.gg/QGBpdjptsT

@GeneralFig Send me a DM with your Commander Name

I see both threads about the iOS crashing issue are locked, so I’ll post here.

We have made a new internal build of AAO on iOS and it seems like the black screen is gone. There were many, many things we needed to upgrade since the last build was about 3 years ago, but it seems like something along the way fixed the issue.

Now we are not quite at the point of having a publicly testable build, but we are not far off. Once we get a build up at TestFlight, we’ll invite you folks who are having this problem to test it out.