‘’Unexpected error encountered in application’’ it says in the bottom right corner. The map is black, nothing on it. The minimap is normal. Time stuck at 00:00. I’ve also noticed a longer time on ‘’Renderer: waiting’’ prior to opening the replay. It’s been happening since the new patch, I thought it will only happen for old games, but it’s still happening for new games from the current patch.
Hey Roko, can yoyu confirm what version of CADE and what version of AoE2 you’re trying to spectate? We just had a major game and major CA update so if any of those things doesn’t line up you’ll be running into problems.
What you describe is quite unusual behavior though. If it persists after checking those versions it would be good to get a log file/dxdiag file and recording of the issue sent to support@captureage.com to look into this further :)
I’m at 1.6.0. version of CADE and the newest patch (without the Return of Rome DLC) of AOE2.
I’ve tried re-installing and the bug remains… Any solutions?
This is what happens when I start CaptureAge FIRST, select a game to watch and then the app starts the game automatically… After that first attempt, when the game is already open, the original error starts occuring.
I’ve tried everything. Re-installed multiple times. Even bought the RoR DLC, and it’s still the same. I’m kinda desperate…
Update: I’ve finally managed to open a match in CaptureAge. I randomly clicked spectate with CaptureAge right after I finished a Ranked game and it worked. However, when I tried to switch to another match the same error happened ONLY THIS TIME the screen wasn’t black but it was still showing the previous game in the moment it finished, while the mini map showed the start of the new match I clicked to watch. Everything else the same, same error at bottom right. Also, that was the first and last time I managed to watch that match, whenever I tried again, it reverted to the same error.
Conclusion: I can spectate games with CaptureAge ONLY immediately after they finished clicking watch right in the winner/loser lobby, any other route leads to the errors described above.
P.S. I haven’t had a single response from you guys in 12 days… I’ve also sent an e-mail to support@captureage and nada.
Hey Roko. First of all I’m sorry for not answering sooner.
Thanks for your detailed report. I will file all of this additional information.
From what you report there doesn’t seem to be any apparent quick fix or solution that I can suggest, given you’ve already tried reinstalling.
Did you submit the log and dxdiag files in the mail as well?
Yeah I figured it won’t be straightforward to fix.
I didn’t. Could you please explain how it’s done (log dxdiag)?
I just installed captureage, fresh install. I do have some visual mods. I can’t watch replays, it just sits there trying to connect to renderer. If I alt tab, the game is already running.
@Chris Katko Hey Chris! Thanks for your report. It aligns with what other people have been experiencing. Do you happen to be in our Discord Server?
I managed to fix my issue by unticking all my mods and then restarting the game. There are certain visual mods which seem to mess up Capture Age, so I suggest unticking all of them initially and then adding them back in one by one until you get the Unexpected Error. That way you can pinpoint exactly which mod is causing the issue.
This is fantastic to hear! Thanks, @Daniel Bentley ! Did you happen to catch which mod was causing the issue for you?
Unfortunately, disabling mods does not solve the issue for me… It’s been 3 months now…
@Roko Škrabić do you happen to be in our Discord server? I couldn’t find anyone with the same username.
Yes, “shkrabinho”. I’m in the CA Beta thingy too. In contact with SirLaurenceNZ about the issue.