V.14762 BETA Download Links

[Kwiatek]

I got frequently crashes after patch

and also graphic artefacts sometimes - flashing black boxes

Win7 64bit, Quad 3.2Ghz, GTX 280, 4 GB RAM

[lancerr]

5 to 10 fps gain
Aa seems slightly better, hard to tell
Skins work
No sound issues on stock.
Bullets seemed to have changed. Much more like they were in il2
Weathering is great.
Metal actually shines like metal at the right angles.
Blue lines still there.
radio commands work

All in all, good step towards the right direction but a ways to go.

[Tiger27]

Originally Posted by Phazon

AMD or Nvidia have not been releasing driver fixes for Cliffs of Dover because the engine itself is just too buggy and is/was not supporting DirectX standards (no true fullscreen until recently was a big mistake). There are so many existing graphical artefacts on everyone's copy of the game that it is hard for them to determine what is their fault and what is Maddox Games.

Proof in point, Maddox Games is supposably supported by Nvidia yet we have not seen any driver updates from Nvidia showing support for Cliffs of Dover. Nvidia SLI still won't work with Cliffs of Dover, yet Crossfire does. Maddox Games has to fix their engine first before we'll see any driver fixes from either company.

Seems there may be a fix for SLI, just reading this in one of the many sub forums in a post from 335th_GRAthos.

"Giving some feedback on the SLI status after the beta 14762:

SLI works fine for me, using STL's solution:
Quote:
stl Junior Member Join Date: May 2011
--------------------------------------------------------------------------------
Working SLI-Bits to edit with NVIDIA Inspector 1.9.5.5

Click at Profile Settings (besides the "Driver Version"),
create Custom Profile and click "add application to current profile" to add launcher.exe.
edit:
SLI compatibility bits (DX10): 0x000000F5

NVIDIA predefined SLI mode on DirectX 10: SLI_PREREFINED_MODE_DX10_FORCE_AFR

click on "Apply changes" "

Heres the link to the whole thread.

http://forum.1cpublishing.eu/showthread.php?t=23199

[Buzpilot]

Looks like they changed Spitfire MkI pitch from 1 (fine) and 4 (coarse), to 2 (less fine and 4 (coarse), instead of 1 (fine) and 2 (less fine).
We need 1 (fine) for takeoff and dogfight ,3000 rpm, and 2 (less fine) for climb and top speed 2600-2800.
Very hard to do a takeoff now.

Edit; 1-4 is just to compare with a gearbox in a car, maybe better to understand?
Sounds still disappear after AI respawns online.

[csThor]

Originally Posted by Kwiatek

I got frequently crashes after patch

and also graphic artefacts sometimes - flashing black boxes

Win7 64bit, Quad 3.2Ghz, GTX 280, 4 GB RAM

Did you clear the CACHE before launching the game? Often such artifacts are the result of old cache content.

[Buzpilot]

Originally Posted by FS~Phat

I just did an experiment with turning intel hyperthreading off in bios and noticed a lot smoother game play. The black-death track also had less skips in it and a higher avg FPS by about 4FPS.

I also noticed that COD uses mostly CPU core 0 and 2 regularly going to 95%+ on core 0 and 80% core 2. CPU Core 1 and 3 were normally around 30% each.

This is with 4 GPU crossfire setup which runs at 50-60% utilisation each GPU in blackdeath but 90% plus in normal gaming.
Looks like we are CPU restricted for ultimate FPS and smoothness not GPU.

Looking at shadow outside cockpit, on moving tall grass, it looks software rendered, or cpu rendered?

[Rattlehead]

Originally Posted by Blackdog_kt

What i'm trying to say is that if i bought a new PC today to play a game that i don't know much about its inner workings and it has a small following, i would consider myself asking for trouble if i went for SLI/Xfire.

And to that I agree but let's take for example, a person who bought a 5970, a dual gpu card manufactured on a single pcb, back in late 2009 to play several types of games on.*
There is no way that person could foresee that he would have trouble with a game launched in 2011. Even worse, he can't simply take out a card and run it as a single gpu. He is literally buggered until a fix is found.

I do see your point, it's just that if blame as such is to be apportioned, then for me it's MG and AMD that should be the ones to look to.
I'm confident a fix will be found for those still having trouble on the hardware end, and I understand that it's never easy to make a game run well on every possible kind of PC in this world, so for me it's just one of those things really.
As long as the problem will be attended to then that's the main thing.

*I would have been sitting with a 5970 right now, had they not been as rare as hen's teeth at the time I was looking for a new card. I guess I got lucky in an odd sort of way

[TheEditor]

Originally Posted by Blackdog_kt

Strange, because it works fine on other Ati cards like my two year old 4890 or the 5xxx series. I used to get anywhere between 30-60FPS over any kind of terrain with the previous patch and this one probably made it better since it runs fine without me having to disable the Ubi logo splash screen (i'll try it out and see if i gain anything more).

This blue stripes business is most probably an issue between the drivers and the 6xxx series architecture, otherwise we would all get the blue stripes. However, it's only the 6xxx series that gets it, every other Ati card that meets the system requirements doesn't have this problem.

You say 6xxx cards are the only ones that get blue stripes but thats wrong. I have two 5770 CF and still see the lines in the water.

[skouras]

Originally Posted by banned

Everything running really smooth for me. Only thing I've noticed is planes don't explode when they hit the ground.

same here

[JG52Krupi]

Hmm mine exploded....

But I have been experiencing a huge drop in fps when i fire my weapons online, has this problem being here a while?

I only started flying online again today, apart from that it was awesome...