Ummm ... there's a lot of « good feedback » on the other, recent Beta-1A threads ! It's an OK post (but why did he insert part of his DxDiagnostic text-file ?!) ... but there are a lot of other « good » posts on the other threads.

It would have been more interesting & informative, Frog Boy, if you had precisely explained what you found soooooo « good » in his post to single it out from the other posts, on other threads.

When a Stardock official does post, it has more weight. Consequently, it "should" convey more information. « Good feedback! » : what does that mean ?! There's a lot of "good feedback" on the other threads.

Feel free to inflict upon me a minus 1 karma for my impudence.

I inserted part of my dxdiag so GPG would have system specs to reflect my fps, memory exhaustion, and cpu usage issues (Especially since it is a drastic change from Build 1 to Build 1A.

Just saying I have these issues doesn't mean the bytes it's saved on without something that can explain the issue or be used in quantitative analysis.

New Information regarding:

1)  Memory exhaustion worked around by using a 4 gig thumb drive and allocating it to Readyboost.

2) Less on screen increases fps...which is really interesting, as in the last build it was the exact opposite.  Number of pure individual units still causes fps to stutter with each new wave, and the more units in the wave the less the fps.  Most noticeable around giants, but starts with catapultasaurs.

Continuing with but seperate from 2), for some reason the game plays better with graphics set on high.  I honestly don't know why, but I'm guessing it's alot like how Hellgate was made.  Same with vertical sync off, even when fps doesn't reach the sync cap.  The improved fps and responsiveness on high compared with other graphic options is consistent between builds, but thought it was worth mentioning.

Nope, pure empirical evidence.  I'll get back next time I play and actually post the render. It will be interesting to see how the measured render time compares to the actual play experience.  The last build had a fps measure, and I remember how the game played at different fps.

What I was trying to convey was that zoomed in it's really fast until giants, then its slow but playable.  Zoomed part way out it's slow but playable, almost unplayable when giants hit.  Zoomed really far out it;s really fast until giants, then its slow but playable.

Edit:  Just played 3 games.  Waterfall level 3v3, but I'm the only real player.

Zoomed in real close (can see entire base at start):  render of 100-150 during normal creep killing.  Flashy Demigod fights range from 200-1500 depending on how many are in the fight and what misc. things are happening (1500 involved three demigods, a new wave spawning, and my death animation).  Giants spawn raises it to 2000 while everything loads.

Mid level zoom (can see from base to central flag):  render of 100-150 early game, grows to 200-300 around healers spawn, 400 around catapultasaur spawn, 1000 around angels spawn, 3000 around giants spawn.  Drops back down to between 150-400 depending on what's happening.

Really zoomed out (ie.  I'm at my health crystal and can see beyond the far side of the map beyond enemy base):  drops below 100 for normal gameplay and ramps up to 300 around the end of the game.  Constant during all demigod fights.  Otherwise constant except at angels or giants spawn, then can ramp up to 1000 then drops back down.

Summation:  New waves spawning at and after catapultasaur cause the game to spend a lot of time rendering.  The closer you are zoomed in, the more what units are doing affects the render rate.  For me, the game can quickly become unplayable since my normal mode of play is at a mid-level zoom.