Sorry, we don't support your browser.  Install a modern browser
This post is closed.

Error initializing resources after newest update (28 april 2022)#105

Hello,
After last aoe patch from 28 april 2022, i can’t use capture age. I am getting 2 bugs that i’ve attached. I’ve tried reinstalling capture age and reinstalling aoe and veryfing local aoe files, but it didnt’t help. After last update - 1.5.0 it was working fine for 1 day, just before the aoe patch came. Is there a way to fix it?
Greetings, Igor

2 years ago

Hey Igor,
Could you please send a logfile to: support@captureage.com or join our public discord and message me there “SirLaurenceNZ#5028

Find your logfile by putting %APPDATA%\CaptureAge\logs into your File Explorer’s address bar (to the left of the Search box).
Only send log files to developers, as they may contain some personal information (which all falls under CA’s privacy policy - https://captureage.com/privacy).

-SirLaurenceNZ

2 years ago

I am having the same problem since the dlc came up, tried reinstalling aoe2, validanting files, reinstalling captureage and nothing worked.

2 years ago

same issue

2 years ago
B
Changed the status to
Investigating
2 years ago
B

We are not sure at the moment what is causing this, but our next release will add some additional error reporting that should allow us to track this down.

2 years ago

A fix for anyone wanting to use CaptureAge now has been found:

To repair your CaptureAge install from the “Error initializing resources” bug, follow these steps:

  1. Open your CaptureAge folder by putting “%APPDATA%\CaptureAge” into your File Explorer’s address bar (to the left of the Search box).
  2. Delete the file named “smx_metadata_cache.dat”
  3. That’s it, restart/run your CaptureAge and it should be working again.

Note, an update will still be made to prevent this from happening for more users but if you’re having this issue you can get it working before the update :)

2 years ago
1

This solved for me, thank you very much!

2 years ago

Solved! Thank you so much !!!!

2 years ago
Changed the status to
In Progress
2 years ago
D

Has anyone had this issue since updating to version 1.5.2? If not, I think we can close this.

2 years ago

Closing this now as there doesn’t seem to have been any further reports, thank you to everyone who sent logs and helped in getting to the bottom of this :D

2 years ago
Changed the status to
Completed
2 years ago