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

[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.

[Space Communist]

Originally Posted by 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.

I am really not sure why people think the propeller graphics were taken out. The prop is quite visible if you look at its edges, it's just very faint as it is in real life.

[AARPRazorbacks]

The sim is flying much better on my system.

Intel core Duo E8600 @ 3.33GHz
Ram 4GB
550 watt power supply
Video card GTX 470 1280 MB GDDR5
MOBO- Gigabyte GA-EP45_UD3P
Duel partition
Windows XP Pro 32bit.
Windows 7 64 bit.
CoD in W-7 64 bit
Fraps
x52
MSWFF Pro 2
TIR5
Monitor- HP-19 or a VIZIO 42in screen.
Turtle Beach Gaming Headset and Mic.

What your doing is Great The interaction with the owners of CLoD. I Knight you Sir luthier!
The keeper of CLoD.

I know now that you understand that for most of us, flight sim's are not a game! But a way of life.

http://www.youtube.com/watch?v=Z0ceu...eature=related

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

flyer01

[anavas44]

Originally Posted by 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.

Although I'm only an end user I can give you some answers mate:

1] Propeller IS visible indeed. It's as visible as in RL (we are used to props on movies and videos, which are substantially more visible than in RL)

2] There are no tracers on the Spitfire due to historical accuracy. If you want tracers, make a custom loadout on the loadout screen

3] As far as I know since early april all rendering work (i.e. loading textures, etc) is distributed between all the cores of your CPU (in a multicore CPU obviously)

4] I know nothing about the G940, so I can't be of any help here. Please note that FF has been activated in this patch though so not all is lost

5] IMHO tree collission is not the highest priority right now. Luthier team should focus on other most important things that are yet to be fixed

6] Yeah, you are right. AA doesn't work for me neither ATM

7] According to Luthier they are working right now on this. Im sure it will be fixed on the next beta patch

Cheers,

Quick return:

Unfortunately NOT the slightest vertical g-impact on head movement any longer. A small amount should have been preseved.

Did anybody now with the 109 reach the 450 kpm at sea level that we at least could get before? If so how do you manage your engine? I now only seem to get 430 kpm.

[SG1_Lud]

Originally Posted by 41Sqn_Stormcrow

Quick return:

Unfortunately NOT the slightest vertical g-impact on head movement any longer. A small amount should have been preseved.

Did anybody now with the 109 reach the 450 kpm at sea level that we at least could get before? If so how do you manage your engine? I now only seem to get 430 kpm.

will try the SL test now and report you, but bear in mind he have to correct the results with atmospheric Temp and pressure to compare data with the specs
And, to bypass the bug of the overweight of the 109, we have to reduce the fuel load, in order to compare. (did you do that?)
Can you please try to climb her to maximum ceilling on your side, I 'd like to compare too.

And yes, I felt too is too quiet in the cockpit now, steady. I think I like it, but could be agaisnt realism for some tastes.

[Bungmiester]

Just tried your new patch, thankyou for all your hard work, still getting some minor stutters over London, HUGE IMPROVMENT IN PERFORMANCE, hope you keep up the work with more optimisation perfomance as well as content, as this sim has huge potential.

System spec
P5N-D Asus motherboard
on board sound card
8 Gig corsair Ram
intel core 3ghz Q9650 4 core processor
Nvidia GTX 460
Win Vista sp 2

[Skoshi Tiger]

Mixed results after installing the patch.

When I first entered the british convoy attack mission I had sound corruption for about a minute before the correct engine sound started playing. The first two missions ended with the sim freezing.

I exited and deleted the softclub folder, then verified my games cache files in steam and ran two games in a row. with out problems.

The default setting for video seam to be mostly medium, whereas before I had details up high and forrest low.

My graphics card seams to be running at close to 100% in mission now. (no heating problems low 60'sC)

Cheers

Hope this fixes the issues.


Cheers!

Originally Posted by cheyennepilot

will try the SL test now and report you, but bear in mind he have to correct the results with atmospheric Temp and pressure to compare data with the specs
And, to bypass the bug of the overweight of the 109, we have to reduce the fuel load, in order to compare. (did you do that?)
Can you please try to climb her to maximum ceilling on your side, I 'd like to compare too.

And yes, I felt too is too quiet in the cockpit now, steady. I think I like it, but could be agaisnt realism for some tastes.

Did you do the tests already?

Just to give you an idea:

This test where I only got about 430 kph was in exactly the same mission that I used before patch and where I got 450 kph on sea level and both times with the same fuel loading. Nothing has been changed except the patch.

[grunge]

Originally Posted by 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.

I whis just that the propellor would be like in Sturmo 46. This blurry dish is just dissapoints me, it's very sad. On the early promo stuff and the pictures it just looked awesome! Thats one of the main things that keeps me away from it, i just can't understand why was it necessary to destroy this.

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