Il-2 Sturmovik: Cliffs Of Dover Retail Patch v 1.01.14550

[Gollum]

Originally Posted by Gollum

Asus P8P67 Motherboard
I7 Processor 3.4 GH not overclocked yet
2X ASUS 6950 (not linked yet) waiting for game to support it properly
2 solid state hard drives raided (game installed here)
1 terrabite hard drive (nothing on it yet)
8 gigs ripjawx ddr3 ram
mega cooling heat sink to overclock processer when required.
OH, and windows 7 ultimate

Need anything else?
I did not attempt to try psuedo full screen since I did not see an option to enable or disable it. before this patch my game ran flawless (based on performance alone ( FPS, Stuttering, ect..)

PS. Thaought I had ATI card but does not say so on the box. Are the cards mentioned above ATI? I think so right?

PS. Im a jerk.. I found the full screen option.

[ReconNZ]

Originally Posted by luthier

No tracers in the Spit is a feature, a realistic historical loadout. You can change it by manually loading tracers into your plane in Plane Options.

Hi Luthier,

Thanks for your time and hard work - this doesnt work though - the plane loadouts have been faulty in the QMB since launch - you can select tracers etc, but they dont work in the missions - they seem to work ok in MP, but the QMB plane fitout doesnt work.

Also you can select plane weathering, squadron numbers etc, but they dont show up when flying - either in MP or QMB - both elements are broken.

Can you please confirm that this is the same for you, not just on my system? Thanks, it's a big emersion killer for those of us whos systems run this ok.

[ATAG_Doc]

Wow I am going to finish my lasagna and test it. I watched black death again using all max settings and just uploaded it. I see all kinds of new stuff. It's full screen play but the video has a border for some reason. I'll be the first to admit I don't know how to do video but I have fun trying anyways.

[ARGH]

biggest issues;

1] propellar not visible due to stupid epilepsy rules. we need a visible prop. its an immersion-killer without it. if you cannot get around this then quietely release a backdoor fix so the end-user can enable it through config tweaks.

2] all this time i thought invisible tracers on spits was a bug. you should change the default loadout to have tracers so common players won't be confused.

3] you promised the rendering thread getting its own dedicated core and it will double fps. we really need this but have not heard anything since.

4] G940 flight stick not fully compatible with game, sticky fire button, throttle sensitivities not accurate, and what appears to be some input lag. i assume joystick issues spill to other FFB brands as well.

5] we need some form of tree / forest collisions. maybe you can insert invisible building meshes with physics enabled on top of the visible trees or something.

6] AA not working properly / not applied on every object.

7] allow default loadouts to be changed and some input settings do not appear to work. rear view camera on spit appears bugged as well.

[Tempered]

Originally Posted by ReconNZ

Hi Luthier,

Thanks for your time and hard work - this doesnt work though - the plane loadouts have been faulty in the QMB since launch - you can select tracers etc, but they dont work in the missions - they seem to work ok in MP, but the QMB plane fitout doesnt work.

Also you can select plane weathering, squadron numbers etc, but they dont show up when flying - either in MP or QMB - both elements are broken.

Can you please confirm that this is the same for you, not just on my system? Thanks, it's a big emersion killer for those of us whos systems run this ok.

You can change your ammo load out by going to the options screen from the main menu, select plane, select the type of plane you want to change load out on, change your load out, save under a new name. It will now become your load out for that plane. It has worked this way for me since the original version release.

[Timberwolf]

Luthier : I bought this game about a month or more ago I have upgraded my video card (5770) and changed some parts including the case due to the fact i bought a new basic model computer .. I have no real issues running the game or game play at high settings. So for that thank you. You and your team have worked hard and it shows Any word on newer sound files for plane engines, Wind, Guns, I love 2 things The sound of the Merlin flying by and the Start up high pitch whine of the 109

To all : I'm new to the IL-2 series I use to play Fighter Ace online a few years back under the same name My question is there a true level flight adjustment on the game? I found myself bobbing up and down trying to shoot at a 110 it was unreal .. Even with playing around with the trim control. I'm not to crazy about the feel of the aircraft yet. Landing seems to drag on too far

Thanks

[Helrza]

Originally Posted by luthier

This is unintended. Someone is getting murdered tomorrow morning, hot fix is coming right up.

For now please unbind the prop pitch from an axis and bind it to a pushkey, which is not all that unrealistic. Sorry about that!

Rgr mate, make sure u dont make make too much of a mess in the murdering process lol

Just so u know, and as stated above by other users, the problem is with the pushkey binding. I remmaped the the throttle to use the PP instead and it does indeed work as normal as others have said. (up= pp down, center=nuetral, down= pp up)

Thats ok, im happy to leave it like that for now, since ive been using prop pitch more than throttle anyways thanks for the quick acknowledgment mate

[Dano]

Originally Posted by luthier

Yikes. Are you running with full screen ON? Not pseudo?

What exactly do you mean by stutter? Random hiccups? Connected to any events? Constant tiny freeze-ups?

Makes no difference with pseudo or full screen from what I can see, even windows thinks it's running badly if I go full screen and uncheck desktop composition on the launcher.



Stutter: I'd call it random hitches, some seem to be somewhat linked to loading events such as voice but others I cannot see any reason for. This current patch is in second place only to the original release for me.

However I do need to verify that it's not being caused by the new Nvidia drivers...

Oh, and I'm also having very flickery shadows.

[Plt Off JRB Meaker]

Originally Posted by Dano

Makes no difference with pseudo or full screen from what I can see, even windows thinks it's running badly if I go full screen and uncheck desktop composition on the launcher.



Stutter: I'd call it random hitches, some seem to be somewhat linked to loading events such as voice but others I cannot see any reason for. This current patch is in second place only to the original release for me.

However I do need to verify that it's not being caused by the new Nvidia drivers...

Oh, and I'm also having very flickery shadows.

I get this too and it's nothing to do with the Nvidia drivers,I was getting this warning a week ago when I was still running duel ATi cards.

I now have a GTX580 and I got one of these warnings the other day,thought it was just my pc,glad I'm not alone.

[lensman1945]

Originally Posted by Dano

Makes no difference with pseudo or full screen from what I can see, even windows thinks it's running badly if I go full screen and uncheck desktop composition on the launcher.



Stutter: I'd call it random hitches, some seem to be somewhat linked to loading events such as voice but others I cannot see any reason for. This current patch is in second place only to the original release for me.

However I do need to verify that it's not being caused by the new Nvidia drivers...

Oh, and I'm also having very flickery shadows.

I've had the game since day 1, only had the retail patches, never had any errors, crashes etc.
Anyway...had that Windows message pop up last night too. Also had a loss of sound for a minute at the start of a single player mission.

First negative comment from me...