Hello bt132,

this log just shows your onboard Intel HD Graphics which wouldn't be supported by the game.

Do you even have a dedicated ATI Graphics card and if so which model?

Hey Marshalty,

at least the errors from last time are now gone, but I can not see any other issue that would cause a freeze in the log.

Now I am unsure which cause we are looking for.

Could it be caused by an instable internet connection? 

Or do you encounter such freezes even in Single Player mode?

Hello xiaolung,

I loaded both of your save games and they both work for me as intented.

The first one I played to an end and destroyed both Korvek dungeon cores and the winning sequence triggered correctly.

The other save game must have been made instantly when Korveks second core was about to be destroyed.

Directly after loading it the winning sequence triggered.

Did this problem happen before you updated to Patch 1.6.5 (released last Thursday)?

I ask because one of the issues fixed in this patch is that you can not win a level from a save game which was made short before the last enemy core is destroyed.

However this was fixed in the newest patch and thus even your second save game works fine now.

Can you make sure you arew on version 1.6.5 and then load your save game again?

Can you tell us if the problem is fixed by now?

Cheers

XtraPEG, I did edit your lost to link the output_log in a file rather than bloating this thread with these logs.

Please use the "File" button above the text area where you enter your message to attach any files in future.

You didn't mentioned that it was a multiplayer game in which you were client rather than just a Skirmish match.

In this case another possible cause can be lag or package loss when you had your match.

If so, the hosts response to make Titans available did not arrive at your client and thus it didn't update the UI.

At least your output_log does not contain an error that would be related to this issue.

Might it be you had a laggy or instable internet connection during that match?

Glanten, did you by any chance possess a unit which died while possessed before the lag occured?

Hello XtraPEG,

If no mutators were used to prevent Titans or higher their sin cost and you didn't had a Titan summoned already,
then the only reason why Titans would be locked would be an error that prevents them from being made available.

If you can reproduce this issue it would be very helpful to take a look at your outout_log because it might reveal an issue preventing Titans.

Here is described how to upload such a log, beware it is overwritten each time the game is started, so please save & upoload it immediately after the issue occured:

http://brightrockgames.userecho.com/forums/2-war-for-the-overworld-knowledge-base/topics/118-how-to-submit-a-bug-ticket/

Cheers

Hello Glanten,

the log you uploaded contains an error which happens over and over and might well be the cause of the lag you encounter.

It's caused by at least one destroyed unit still trying to update and causing errors every tick as it looks.
Unfortunately we do not yet fully understand how this can ever happen and we need to investigate deeper.
We didn't see this issue before and wonder if this is always happening when you encounter lag.

Do you remember doing anything specific in all cases it started to lag which might help us to find the root cause?

In case you run into this issue again, can you upload another output_log just to see if it is indeed this same issue all time?

We will keep you updated when we find out more but further hints how to trigger the issue would be appreciated.

Thanks for your help in finding the cause!

Hello Valtiel,

I can confirm this siege door in Ponygrasp is 90 degrees off in rotation.

We will get this fixed for the next patch.

Thanks a lot for pointing us to this!