Same deal here, just crashes over and over. This beta 1.1 is worse by far. This game has not seen one stable release yet. There is no way this thing will be in an acceptable state for 1.1. The engine and the game are plain garbage. I honestly do no think Stardock has the technical knowhow to fix this game.

I will not pass judgment till the official release of 1.1, but I already know they are going to release 1.1 in an unstable state. I have very little confidence that it will be fixed.

Actually I believe that they will eventually fix the issues with the game. Besides stability the game is tremendously better that it was at launch and its getting better as the months pass by.

Well Steven, this game has been Beta past it's official release date so we are starting to enter into uncharted waters here. I do not share your optimism with the game being stable in 1.10. Every patch I check for stability fixes, every time it crashes the same amount. It seems like the same issues are plaguing this game patch after patch.

With this NEW beta I see even more crashing, I can't even really bother myself to boot it up anymore it crashes so much. From the previous version this beta has gotten even worse in terms of stability, to think this will all be fixed with the next 1.10 patch is beyond optimistic,

Like I said I'll give Stardock it's second Beta(after I purchased the game), but after that I am not going to be too kind. We are getting to a point where it is getting absurd. I hope I am wrong and this 1.10 patch is a miracle....but if you have been following game development with developers, like waiitng for a game, you would know that the miracles never happen and usually it's a delay in release or a dissapointing release.

So it would be safer to predict a delayed 1.10 or a unstable bug ridden game in 1.10...the miracle patch is very very unlikely. But I would love to be wrong of course.

Outstanding.

I was able to address a few of these.

Basically, there are two big ones caused by the new threading AI.

First, Unit::GetIntelligence() is called by the AI a lot for things like seeing how different creatures should behave (you can tell the wolf has a bad intelligence XML because it will attempt to "talk" to you).

Anyway, that call involves a lot of stuff that gets touched by other threads.  So I've created a new fuctnion called Unit::QueryIntelligence which simply sends the last cached value of intelligence.

The other one in there is related.  It's Unit::GetBattleRank (your combat rating).  This turns out to be a pretty nasty call in terms of what it ends up touching.  So I created a QueryBattleRank which does the same thing as above -- last cached value.  Big performance boost too.

While I was in there, I redid how GetBattleRank works because the AI really relies on Combat Rating meaning something and in the current public build, it's not terribly useful as a predictor of who will win a battle.  I changed it so that it looks at the combat rating of individuals in an army differently so that it doesn't simply add them up.  I.e. 1000 peons will still get smoted by 1 dragon so the combat rating should reflect this.

Yea, this stuff is extremely helpful. The data in there will actually take us to the line of code (with stack) on where it crashed.

It's really amazing.  When I started programming, I had to use beeps to try to figure out what was causing a problem.  It's all come so far over the years.