Il-2 Sturmovik: Cliffs of Dover: Patch 1.00.14072 -ARIL 15

[Wolf_Rider]

Originally Posted by MadTommy

I'm using these beta drivers.. not seen this issue.

Regarding patch: Great to see the server browser working.. not seen much performance increase. I've got good fps, but still get stuttering when at tree top.

Game is playing great for me.. its just tree top flying needs work.

Dual core E8400 @ 3.6 Ghz, GTX 480, 4 GB (1066) Ram, SSD, x-fi extreme music sound card.

its as the video shows for me too... nonetheless the patch is a good effort in the right direction

one thing though... running a Quick Mission and then exiting and restarting that same Quick Mission, on occasion, has some of the engine control settings as they were in the previous Mission

[IvanK]

"So you're saying that the original release, with bouncing needles was inaccurate"

Yes

- but you're also saying that the devs have access to current warbird pilots,

Yes, who didnt get to see the bouncing needles until release.

which suggests that the bouncing needles were accurate

No it doesn't. The bouncing needles were a coders "interpretation" or his idea of what it should look like and was not referred to subject matter experts before release. If it had been we wouldn't be having this discussion.

(they didn't code it for a laugh did they).

Not worthy of a response.

[Fall_Pink?]

Thanks! This is indeed a big performance fix and stutters have been reduced big time. There' still there, but I reckon that's largely related due to the texture size. On my 5870 1 Gb video card I can use medium and high textures, but 'original' is unfortunately out of the question... I guess a 2 Gb vid card is needed for that.

edit: 1) I noticed the disappearing sounds bug is still there. It seems the sounds sometimes looses synchronization with the objects that are displayed. 2) Furthermore, it seems the AI too easily collides with wing men. 3) I noticed medium bombers perform sometimes a bit like fighters and do not seem to have weight/mass/inertia limitation. 4) the constant flaps on/off message for the quick cross country mission (auto pilot enabled on take off) is still there and seems like a bug to me.

Rgs,
FP

[schnorchel]

After the new patch I think the FPS is generally increased, but at some location the FPS is drops alot. in quick mssion4 use fly a JU88 only get 20FPS in cockpit an d14 FPS external view when flying over the plant area close the sea. I normally have 35+ FPS in previous version at same location. that's wierd.


My rig, i7 980X 6G RAM and ATI5870 with 2GRAM, Win7 64bits.

[ICDP]

As mentioned a few times I have serious problems with this patch.

Buildings look like brown blocks or are missing entirely.

Building densitiy option in video settings has no effect

FPS is 1/4th what it was over towns. Especially over the closest city on the Normandy Free Flight mission.

Here are my PC specs:

ASUS P6X58D-E
Intel i7-920 clocked at 3.8GHz
2X AMD HD6970 2GB in Crossfire (crossfire disabled for CoD) AMD 11.4 preview drivers
Win7 X64 Pro
ASUS Xonar DX
12GB Patriot DDR3 1600 RAM
Corsair 750W PSU

[150GCT_Veltro]

No improvements on DX9 and there are again several problems also with cockpit and aircrafts.

http://www.150gct.it/users/150GCT_Ve...415_201421.JPG

I give it up with this game.

[catar]

I wonder if the buildings problem is related to Intel's Hyperthreading.I don't see any difference in core usage after the beta patch.

Originally Posted by fly_zo

... huge improvement in FPS and performance in general , i can actually fly now with grass enabled

Many, many thanks to all involved !

regards,
fly_zo

specs:

Win7 Ultimate 64bit - SP1

MBO: ASUS P5Q SE PLUS
CPU: Pentium Dual-Core E6500 @ 2.93GHz
RAM: DDR2: 4GB
GPU: Club 3d Geforce 460 GTX 768MB GDDR5

[Display]
Operating System: Windows 7 Ultimate, 64-bit (Service Pack 1)
DirectX version: 11.0
GPU processor: GeForce GTX 460
Driver version: 266.58
DirectX support: 11
CUDA Cores: 336
Core clock: 675 MHz
Shader clock: 1350 MHz
Memory clock: 1800 MHz (3600 MHz data rate)
Memory interface: 192-bit
Total available
graphics memory: 2559 MB
Dedicated video memory: 768 MB GDDR5
System video memory: 0 MB
Shared system memory: 1791 MB
Video BIOS version: 70.04.1B.00.01
IRQ: 16
Bus: PCI Express x16 Gen2

...I have i7920@3.5Ghz, gtx470@480, 6GIGS of RAM, X_FI Extreme gamer, TIR 4 pro, 1680x1050, win7 64bit....and although my average FPs are pretty high COD is still not smooth as it should be with such FPS.....that is over water, over land its stutters a bit.....svašta.....

[jibo]

interesting reports from SimHQ

I went from "not struggling" to "rather struggling" with this patch. Go figure. I had gotten the game to play quite fluidly (London was even playable) using the nossao mod. Now with this latest patch I get a definite rubberbanding effect. Not really stutters per say but the frames are sped up and than slowed down. I revert/re install the previous "parts" folder and the game is fluid again. Maybe I should not fix what isn't really broke but I would like to run the latest version so I can do multiplayer.


Specs
Intel i7 950 OC'ed to 4 Mhz
4 Gig Ram
ATI 6950 2 Gig
Win 7 32bit on SSD
Game installed on different SSD

Game Res 1920x1080

The patch makes things worse for me.

Missing buildings
Unable to change buildings amount in video options. I can change it in the optins but it does nothing in game.
Much lower FSP over towns.

Very poor patch on my system.

ASUS P6X58D-E
Intel i7-920 clocked at 3.8GHz
2X AMD HD6970 2GB in Crossfire (crossfire disabled for CoD) AMD 11.4 preview drivers
Win7 X64 Pro
ASUS Xonar DX
12GB Patriot DDR3 1600 RAM
Corsair 750W PSU

ps: don't post youtube vidz here buddies

[Triggaaar]

Originally Posted by IvanK

The bouncing needles were a coders "interpretation" or his idea of what it should look like and was not referred to subject matter experts before release.

I just find that incredibly surprising. The developers have gone to huge lengths to try and simulate several old warbirds, from their flight model, weapons, engine, damage model as well as how it all looks in cockpit. I'd fully understand if the degree to which they bounced was wrong or up for debate, but I'm amazed they came up with this idea that the needles bounce if they never did.