OLD BETA patch 14413 - May 4, 2011(!!!) - do not install!

[Kankkis]

Originally Posted by roadczar

Dude ... Look at my system specs - crossfired 6990s = 8gb total that is 2 gb per GPU. Also, as I said - same stuttering happens even at the lowest settings.

The same rig has no issues with DCS-A10 with highest settings @ 5760x1080. Or anything else for that matter.

I am willing to bet this stuttering is from poor implementation of Crossfire/SLI support. Prior patch (Steam) did not have this issue.

Real total is 1gb but absolutely there is something wrong with the code, maybe better crossfiresupport is coming sooner or later, even 1 6990 is enough for that eyefinity settings. Or is that 6990 4gb then he have total 2gb

EDIT : yes it is 6990 4gb so total is 2gb, not 8gb

Crossfire/sli memory is working somehow to RAID harddrive.

[Untamo]

S!

Short test online: Haven't had the infamous stutters before, but this beta patch brought them to me too .. The stutters happen at approx 2 second intervals and freeze the screen for a very short but very noticeable time.

Didn't test very long, but the Bf-110 I tested online seemed also to jitter back and forth in the air in its flying direction.

-Untamo

[roadczar]

Originally Posted by Kankkis

Real total is 1gb but absolutely there is something wrong with the code, maybe better crossfiresupport is coming sooner or later, even 1 6990 is enough for that eyefinity settings. Or is that 6990 4gb then he have total 2gb

EDIT : yes it is 6990 4gb so total is 2gb, not 8gb

Crossfire/sli memory is working somehow to RAID harddrive.

I think we are all saying the same thing. My only point was 2GB/GPU and not 1GB/GPU as previous poster had stated.

[Buchon]

Originally Posted by roadczar

I think we are all saying the same thing. My only point was 2GB/GPU and not 1GB/GPU as previous poster had stated.

With 1920x1200 you fill 1GB VRAM easily (game maxed but SSAO).

1920x1200 = 2.304.000 pixels in 1 GB VRAM

Which mean that the appropriate capacity for 2 GB is :

2.304.000 x 2 = 4.608.000 pixels more or less.

Your system exceeds this :

5760x1080 = 6.220.800 pixels

Try lowering the resolution at 3760x1080, it should be in the margins to play the game maxed (4.060.800 pixels) and you will not notice the difference.

Edit :

And up a video, that Eyefinity setup is really cool

[roadczar]

Originally Posted by Buchon

With 1920x1200 you fill 1GB VRAM easily (game maxed but SSAO).

1920x1200 = 2.304.000 pixels in 1 GB VRAM

Which mean that the appropriate capacity for 2 GB is :

2.304.000 x 2 = 4.608.000 pixels more or less.

Your system exceeds this :

5760x1080 = 6.220.800 pixels

Try lowering the resolution at 3760x1080, it should be in the margins to play the game maxed (4.060.800 pixels) and you will not notice the difference.

Edit :

And up a video, that Eyefinity setup is really cool

Thanks for the effort, but as I said this is not a VRAM issue since same stuttering and frame rates happen even at lowest settings. I'll upload a short vid in a few...

[roadczar]

Now famous stuttering @ 2400 x 600

http://www.youtube.com/watch?v=AY11UXOpD2E

[Buchon]

Thats really weird, I can fly better with my card at 1920x1200 over there.

Did you tried a single card in a single monitor ?

[ARGH]

When will the rendering thread be offloaded on its own core as you promised earlier? This will double framerates and shut everyone up for a bit.

[Eckhart]

Originally Posted by roadczar

Now famous stuttering @ 2400 x 600

I have exactly the same problem on a similar system.



When I think that I acquired my computer configuration with "Storm of War" in my mind and now they made me jump off those "Cliffs of Dover".

What we have here is high end material. So 1C...do something to get this game going on our settings too not only on some low end steam powered computers....Fix it and don't get lost in day dreaming about future projects (eastern front !?)...Focus and come out with something working. Otherwise there won't be any future projects

[Buchon]

Screenshots not working.

The full screen mode broke the default screenshot key [print screen], redefining the screenshot key in controls to F12 for example it will work again.

Looks there a conflict between Windows and the game interface for this key.