To answer all the replies to my question (Thanks BTW!), my CPU runs at 3.4 GHZ, and has turboboost enabled, which means that under certain conditions, under load, it actually boosts its clockspeed to 3.8 ghz, effectively 4.
Now for the settings!
Bloom is off.
No AA. (ingame AA, as it is rubbish. I have 2xMSAA enabled via the Nvidia CP along with 16xAF. The AF only drops me a couple of FPS.)
1920x1080 resolution.
Buildings maxed.
Effects on the "HIGH" setting. (2 settings below max)
gloss mapping, cloud transitions, animation desync, detailed shadows on.
Terrain quality maxed.
Unit detail set to "HIGH" (2 settings below max)
Tripple buffer enabled.
Vegetation quality set to "HIGH". (2 settings below max)
As a reminder, here is my rig.
Spoiler Alert, click show to read:
i7 2600k@3.4 Ghz, turboboost to 3.8 Ghz.
8GB of DDR3 RAM @1600 mhz
MSI GTX 570, 1.2 GB, Factory overclocked.
win7 64bit
Gigabyte z68 motherboard, I cannot recall the exact model. ATX form factor though. A few bells and whistles.
Last edited by rsslcs; April 09, 2012 at 01:15 PM.
I just had the most buggiest battle i ever encountered in my life
1) Near the start of the Macedon campaign 0 turn is the greeks attacking me, now, when they attacked me when i just captured dryhaccium(the roman town in greece at the start) i naturally played it and was outnumbered 2 to 1.
First problem i saw was in the middle of the battle. Now since they were attacking me i naturally thought they would put all their forces in to take the town over(except cavalry) when i dealt with what i thought was the main army was actually half and they had forces outside near the borderline of the map 2 units with battering rams was not being used along with other units... so i had to get my cavalry to hit them and lure them in one at a time. I expect that situation to be in stone walls siege not the wooden palisade or the other one(second tier)
2} When i was trying to move one of my units which was the agema elite phalanx instead of moving to the place i wanted it to go, it just stood there moving its phalanx up and down(even when i put the phalanx mode off it still continued to do it)
3) the moment number 2 happened my screen just began moving itself, i was not moving it with my mouse or keyboard and i had to hold Ctrl just for it to stay still and the moment i let go of it it just continues to move it self to the edge of the map
4) after the heroic victory(which by the way took a lot longer then usual) i was expecting my campaign map to be normal but what happened? it just moves left to the edge of the map and i did not have a clue why it was doing that(and no the buttons of the keyboard is not stuck at all)
Another issue I have found is that when ordering a unit to charge, only the front line of the unit charges and the rest stands there waiting for the unit to make contact with the enemy. Sometimes the unit stays separated with only the front line of men doing anything until eventually that front line dies off. Is this being looked at?
At first I'd liket to congratulate you making the new version! It's great! I have onley one question. Yesterday I started a Seleucid 1 turn campaign and when I checked Babylon in the battle map I didn't see the Hanging Garden. Is it normaly? In the previews I saw it in the city...
At first I'd liket to congratulate you making the new version! It's great! I have onley one question. Yesterday I started a Seleucid 1 turn campaign and when I checked Babylon in the battle map I didn't see the Hanging Garden. Is it normaly? In the previews I saw it in the city...
Thanks!
It only shows in the large and huge city levels. There was no room for it at the 'city' level.
Creator of: "Ecce, Roma Surrectum....Behold, Rome Arises!"
R.I.P. My Beloved Father
I don't mean to be cruel, but if you're using anything other than the 'pure' 2.5 patch I really can't help you.
It is not about the 4tpy-script, I am experienced enough to tell that for sure.
Its something else, I just wanted to post the turns after which the error occured - i.e. after 76 turns.
The error is in the "pure" 2.5 version, sorry to say that.