Couple of things:

a) some projectile hits (flak/.303 rounds) on the 109 (and maybe all aircraft) still don't make any noise.

b) aircraft are still very hard to see from above. When I say 'hard' I mean unrealistically difficult to see.

also, and as mentioned elsewhere in this thread, you can see ships through the cloud cover!

Thanks Krupi. Bloody internet is broken and I can't get the patch, let alone get online.

no no no!its not only ships you now see through clouds!also ground objects as well as other aircraft!!!!

Thanks for the response, they did ignite rather easily before which didn't appear to be very realistic :)

Luthier,

I noticed the following errors while using things like actor.Group() and (actor as AiAircraft).getParameter() in a mission.

Was something missing on the RC?

To all,

Can any one confirm is not just me?

Thanks,
ATAG_Colander

I run this application but the problem still remains.

I check the Log.txt and noticed it is something related to MS NET Framework

------------ BEGIN log session -------------

=================================================
:
System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)
at System.Reflection.Assembly.LoadFile(String path)
at dPWis1VsDhM1hfIWwIN.moO5oFVgqvBqqcohOo1.e82U0e5AiU b6W0HeZ7Yi(Object )
at dPWis1VsDhM1hfIWwIN.moO5oFVgqvBqqcohOo1.mMhI2M6s2Y c()
=================================================
Application part bob not load assembly f:\program files (x86)\steam\steamapps\common\il-2 sturmovik cliffs of dover\parts\b

Don't read all topic, maybe and possibly repeated ones:

1) Can't start up Hurricanes;

2) Planes still turning into "comets" sometimes;

And the reported problems with ground units, ships seeing through terrain and really bad optimized smoke/dust effects and clouds.

Tried again last night and the problem was gone, i have better performance now than before

Unplayable - 470's Nvidia surround. Yes I CAN disable my SLI and run single monitor, but why would I want to do that?

Waiting for a fix and checking for solutions.... ty.

Selfish bump.

Colander .... You've got mail

Mosca,

Read this:
http://blog.falafel.com/Blogs/scott-...2010_and_NET_4

Basically, the problem is that you need to "unblock" the files from each file's properties (or apparently the zip before extracting it)

Here's an image of the file properties with the unblock button:
http://devierkoeden.com/Images/Artic...ockedFiles.png

.

Salmo,

Replied.

I am breaking my rules.. but do we know why this is happening?

Colander, that was exactly ... ;)

Apreciated!

1. - The Su-26 cockpit is blurred, not sure if it's normal
2. - Merlin engines stop when you reduce the throttle below 15 (ish) %
3. - The pilot's left arm is visible through the cockpit in outside view when wearing an irvin jacket.

Spitfire MkIa 100 octane performance.
 

Improved but still not quite there, especially the climb which falls away from A&AEE tests above 5,000 feet. Report is here:
http://forum.1cpublishing.eu/showpos...6&postcount=10

Spits do not have a collision model, they can ram another aircraft and not suffer any damage!!

that's funny I was just about to post the same effect from a BF109E!
I bet Net-code issue then.

S!

Bug in collision detection maybe. I have no flak hit sounds, very seldomly know I am hit as hit sounds are missing most times. Last patch also increased lanscape shimmering compared to previous one.

That's good to hear at least it's not one sided, now I think we can assume that however is going the fastest is the one that gets away unscathed.

We are going to test tonight.

Is there a way to display latency/ping in game? That might be interesting to see while testing this...

Salute

Bugs noticed:

1. Hurricanes will not start, after 5 minutes of trying I quit.
2. Hurricane engine flames visible inside the cockpit when trying to start.
3. Spitfires and Hurricane cannot sustain RPM's and boost levels which were historically allowable, the engines overheat and destroy themselves at RPM's over 2650 when higher boost levels are used. According to the actual manuals, a rpm of 2850 and +9 boost could be used for continuous climbing for 30 minutes with 100 octane fuel versions of the Merlin, and 3000 rpm and +9 boost could be used for 5 minutes in level flight, with +7 boost and 2650 rpm for unlimited continuous cruising.

Allowable oil temperatures were 98 degrees at +9/3000 rpm for 5 minutes.

http://imageshack.us/a/img259/833/r0p095.jpg

http://imageshack.us/a/img13/9018/sp...limitsat12.jpg

Because of overheating and damage, Hurricanes and Spitfires cannot achieve historical speeds and climbs.

5. Ship and ground object dots can be seen through clouds.
6. Spitfire engine cutout when flying through clouds and for 5 minutes did not run properly.

Luftwaffe bombers do not show damage to skins on the wings. Only damage shown is to the tail and elevators.

Also, unable to explode aircraft fuel tanks with DeWilde and wings do not break off as before.

Test done in Hurricane 100 Oct. Picture 1 all DeWilde.
Picture 2 with mix of DeWilde, Ball and AP.

Convergence 150 Metres Horizontal, 338 metres vertical.

Online and Offline results are the same.

Yep, right-click to get the context menu then click Net something or other (NetStats from memory).

Thats right,

had online fight with a Spit, he made an head attack and rammed me. My 109 exploded, the Spit flew with no scratch away.

IMPORTANT BUG: Spitfire AI

AI has massive problems with Spitfire Ia, Ia (100 octane) and IIa on the ground (I didn't check Spitfire I). Their engine shut down every 2 seconds while rolling and standing.

This causes:
a) It takes very long for them to role to the runway when the spawn parked.
b) The aircraft don't take-off after each other causing collisions.

I think the reason is that the engine shuts down when throttle is set to idle.

This basically makes it impossible to use the Spitfire for everything else than Quick Mission and Online Dogfight.

Last night two 109 clashed with my own 109 in dogfights and both times they exploded and I flew on undamaged, I never saw them hit me just heard a boom and I could not see them anymore...

Also I saw a lot of 109 stalling into the channel last night, three in a row!!!! :(

I wouldn't call that a bug. It was a bug that you could blow the wings off before. The DM is quite improved in this RC patch.

Ju88: Bombsight left and right does not move the bombsight now. It stills gives an indication in the info window but nothing happens.

It seems now I have to use a wide range of speeds to get the crosshairs to settle; @3000m TAS is 348, I had to use from 240kph to 370kph at various times thru the bomb run, when 350kph before would be a good starting spot and go up or down from there.

From the previous loft fix (thanks!) 50kg bombs drop correct, 250kg and 500kg drop long. I think it's backwards on the 111, 250kg drop correct and 50kg are off.

.
With the new patch I havee sometime, most times, when I exit a mission with "esc" i find mysellf on the desktod but not out of the game because if I do enter with the numpad enter key I am back in the game and is I do a second time "esc" then I am in the exit screen of the end mission. Strange is it not? :confused:
Now a question how do you have the smoke efect in the SU26 I tried to find the key in the control menu or the button in the plane but nothing?

In the control page assign a key to "toggle war time power" not sure if those are the exact words.

Neither you nor I know that. So it is reported as a difference in observation as we do not have access to documents that show what has or what has not been changed by the programmers. It is an inclusion to seeing no damage on the wings or bits and pieces falling off. There may also be a link to the no storage tanks exploding programming changes, but I do not know that so it is worth bringing to their attention in case that is the issue.

FWIW: I also think that the wings blowing off with .303 ammunition on a consistent basis is not factual. Rather, my understanding over the years is that the .303's beat the crap out of the insides of the fuselage killing or wounding the occupants and rendering the aircraft unflyable through pure pounding forcing attrition and returning to base or swimming in the channel on the return.

Bug
 

Have to disable X-fire same as everyone else or Video crashes and screen goes to standby until I reboot(Have screen always on in power options and A.V.E.C.Center).
Render pauses @ low altitude (studder).

Ju 88 Bomb Doors closing after singel Drops!
109 have problems in High Rudder...and elevators ...fast stalling by 300-350 speed.
Cant go out from a spin down(stall) from 3000m.
Combat flaps... bad working.

Human Tailgunners Multiplay
you cant shoot a plane behind you...the MG 15(Heinkel,Me,JU) is shooting only 1 or 2 Salves than stopt.than again 1 -2 Salves than stopt again.This BUG is since 1.3 Jeahr!:evil:
This BUG is only in Multiplayer , and when u got 6 from Human and AI!

Positiv: my Mate can fly since 1.3 Yeahr for waiting and Patching.
With a High end System. thx

JG4_Widukind

Hmmm, my xfire has only ever had the green smoke issue... odd :|

My Mate have green smoke iusses too with Crossfire 2 X ATI 4890

Neon Lights
 

I had never seen this before the current patch. The blue will change to red as you change throttle settings.

binky9

Spit 1 trim wheel animations are not working.

Salute

The game weights of the Hurricane and Spitfire aircraft are not correct. They are both too heavy.

For more details, please see this post:

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

Blenheim Bomb bay Doors
 

No indication that the Blenheim Bomb Bay Doors have opened or closed.

Apparently this is accurate

I noticed this - if we go more players in formation, say 6 Stuka, at some distance from each aircraft will begin nasty lags way forward and backward. Observed repeatedly on ATAG server. Im not sure if this is error at ATAG server only (on single player i didn't spotted similar error) or if is this a problem in general multiplayer.

rubber-banding effect, yes seen it a lot when we get more then 45 on line

JU88A-1 dive break indicator
 

JU88A-1 dive break device is still connected to tail wheel indicator...

JU88 & HE 111 automatic steering
 

Setting the main switch of the German-Kurssteuerung --automatic steering device-- to stage 2 the automatic steering takes rudder ailerons and elevaton under contol. This feature does not exist in the original Kurssteuerung K4ü.

JU88A-1 automatic steering device is conneted to pitot heater signal lamp
 

When the SAM-Kurssteuerung K4ü --automatic steering device-- is switched on, the signal lamp for the pitot heater simultaneously is switched on.

The pitot heater switch is connected to auto steering on/off lamp...

Ju 87 B-2 - Missing dive brake indicators
 

Extending / retracting dive brakes were indicated by little bolts at the upper right and left wing.

look at this bug:

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

Then it would be nice to have a bit more sound when the bombs hit the doors.

ok i came to the conclusion that it has to be a bug:

B-Beobachtung bullet type, doesnt have any destructive effect at all anymore on enemy planes...except if you shoot at another 109!

you can choose unlimited ammo and shoot a level flying spit forever without doing any damage whatsoever!
definitely wrong, as B-Beobachtung was known to be very effective, not only in "marking" the target, but also had explosvie and ignition effects.

Salute

109E3 and E4 are at least 74 kilograms too light in weight, please see this thread for documentation:

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

Already noted and requested for all planes.

http://forum.1cpublishing.eu/showpos...&postcount=102

Very heavy stuttering. Have reverted to last official version, deleted conf.ini and emptied cache before updating. Game currently unplayable.

Wheels of the 109 still appear down to the enemy in online play.
http://www.qmku.info/0.jpghttp://www.qmku.info/7.jpghttp://www.qmku.info/8.jpghttp://www.qmku.info/9.jpghttp://www.ymeu.info/test5.jpg

I'm the same as feathered. Because of the increased stuttering and loss of performance no matter what adjustments I've tried with the current patch/hotfix, it is not worth continuing with. Have reverted to beta 18956.

Bf 109E-1, E-3, E-4 appear to be missing the 8 mm armored bulkhead in the fuselage.

A few reports on shot down 109E inspected by the British on the ground.


A.I.2.(g) Report No. 4/53 ñ 1940

Me 109. Crashed 30.09.40 at 17.00 hours, at Queens Anne's Gate, Windsor Great Park. Markings: 9 painted on yellow engine cowling. Spinner white with black circle on tip. Old markings had been painted out, viz. PH + LV. Airframe built by Arado, 29.06.40,. No. 109.4851. Engine DB601. Following fighter action aircraft forced landed and turned over. There are a number of bullet strikes from astern.

Armament: x 2 MG 17 in wings and x 2 under engine cowling. Armour: Standard cross bulkhead and head protection for the pilot.


A.I.2.(g) Report No. 4/54 ñ 1940

Me 109. Crashed on 30.09.40 at 16.50 hours at Sydling St. Nicholas, near Cerne Abbas. Map ref:U0821.
Markings not decipherable. Engine DB601. Following fighter action aircraft dived into the ground and burnt out. Pilot baled out, but was killed owing to parachute failure. Armament: x 2 MG 17 in wings and two under engine cowling traced. Armour: Standard cross bulkhead was found only.


AIR 22/266

Me 109. Crashed on 31.08.40 at Jubilee Farm, Ulcombe. Identification markings 10 + I, black Gothic S on white shield. Fuselage built by ERLA Werke Nr. 62914. Cause of crash, fighter action, condition fair. Aircraft made good landing, wheels up. Armament: 20 mm shell guns in wings and x 2 MG 17 machine guns under engine cowling.
Armour usual bulkhead, pilots head protected by shield. Crew 1, prisoner. Camouflaged green upper surfaces, light blue underneath. In good condition, suitable for exhibition purposes.
The DB601 engine is reported to have had the number 11366/211002a.


Type: Messerschmitt Bf 109E-4 Werke/Nr. 1325

A.I 1(g) Report No. 3/67 states:

Crashed on 30.09.40 at Langney, near Eastbourne. Map ref: R.0820. Markings 13 + (figures in yellow). Orange nose, rudder and fin. Engine DB601A, No.63509, made by Daimler Benz at Genshagen, Toltow.
Armament: 2 x 20mm cannons and 2 MG 17. Armour: normal cross bulkhead, and panel behind pilots head. Following fighter action, aircraft forced landed. A few .303 strikes in cooling system and engine. Pilot prisoner.


A.I.2.(g) Report 1940

Me 109. Forced landed at Love's Farm, Marden, Kent on 05.09.40. Markings < + - black, outlines in white. Crest: Shield U-shaped, outlined in red, divided into 8 segments coloured black and white. Wing tip and rudder painted white, camouflage all blue, fuselage all blue. Spinner divided into alternate black and white sectors. Fitted with Bd601A engine made by Mercedes Benz Erke Nr.10598. Aircraft forced landed following fighter action. Condition reported to be very good. Standard armament x 2 20 mm cannon and x 2 MG 17 machine guns. No head armour.. Starboard wing shows many .303 strikes.
Attached Thumbnails

BuzzSaw,

that is a rather mild way of putting it, given the currently modeled CoD hurricane is massively overweight by at least 250 kg and as a result is seriously hampered in its performance...quoted from the information in your other recent post where this was discussed in detail:

Ju88A-1 - missing flap position "Elevator and landing flaps"
 

In order to balance / trim the Ju88A-1 while landing, compensation for the characteristic nose heaviness is provided by setting flaps and horizontal stabilizer at a negative angle of attack. For this purpose, the control lever for the landing flaps must be turned to position "Elevator and landing flaps" ("Höhenflosse und Landeklappe").

In this position the iL2CoD-flaps retract ...

~S~

RC + HotFix working fine here. No more CTDs (thanks Heaven!), very few stutters, fps min-max 23-61 (occasionally 5-8 due to stutters), avg. 35-40 on ATAG with full settings. Game is quite smooth.

I MISS BULLET IMPACT FLASHES ON ENEMY A/C! GIVE THEM BACK!


EDIT: SOME STUTTERS AND EVEN 3 or 4 seconds-long freezes. Apparently more with HotFIx than with RC, which ran more smoothly. But all in all the game is very playable.

did you rerun the DOTNETFX40.exe and also the Direct X9?

.
A old bug in Blac death track the poor soldier in the Bofor gun look at the picture it must hurt him a lot.
http://s8.postimage.org/d9kwjuuit/sh...006_154801.png


:rolleyes:

Unfortunatelly, this LOD bug still remain. It's annoying, because the conf.ini meshshowlod=1 solved this problem, but my PC drop 10-15 fps even on a small server :/

Pls devs, fix this bug, this would improve lot of running performance!

There are two bugtracker tickets with 95 and 25 vote, this is a common bug! (Many member complain about it on a hungarian forums too).

http://www.il2bugtracker.com/issues/153
http://www.il2bugtracker.com/issues/294

http://www.pumaszallas.hu/Private/VO...cs/LOD_bug.jpg

Sorry for the off topic, but, Tom, what's the small black square that is on your last picture? That on the low - left corner, close to the throttle, pitch etc levers? How do you activate it at the game?

Cheers

I've done a few single player quick missions against beaufighters, and they also have wheels down every so often. They do not always have wheels down, but sometimes they do. I've never seen both wheels down at once, usually one or two - and only after the plane has been hit.

Hi.
(Right click in the game, new info window, Alt+click on it, then right click and choose the customize info window).
After that choose the "Controls Feedback - Directional" component.

OK thanks

the 109E4 shows different oil temperatures to the E3 and E1 at the same power and radiator settings.while the E3 and E1 keep temperatures at 60° with fully opened oil radiators and full power, the E4 stays on the edge of 80°....i dont know if thats a bug of the gauges, or if it has indeed different temperatures.

ata pressure drops, as soon as your revolutions go above 2200 rpm in all the 109 variants.
if you watch closely, you will notice that at 2200rpm or lower and full throttle, the ata will be at 1,35 or at 1,45 with Notleistung...but as soon as you go above 2200rpm, it will decrease to 1,34 or even lower without,- and 1,44 or even lower with Notleistung.
again i dont know if thats a bug regarding the gauges, or if its indeed in the FM.

the turn and bank indicator doesnt seem to be fully functional in the 109s the first few moments after you have spawned...at least i noticed it on airspawns in multiplayer on rebka4 for example...while the slip ball seems to work, the bank "needle" stays in center regardless of attitude in the first few seconds.only after a certain amount of time, it will begin to work.

the prop pitch is still to slow ever since.while it should take only 4-6 seconds for a full revolution on the gauge, it takes 6seconds in every situation...thats wrong.

109 is still too slow...while it should get to at least 475kph at 1,35ata at sealevel now it hardly reaches 470kph at 1,45ata...

109cockpit....the display for your weapons in the 109 should be iluminated with green light to confirm that everything is ok...only if the amount of available rounds decreases, it should switch to a red light(as it does now).

textures....now with this patch, as soon as i reduce the textures from original to even high, the warning on the wings on the 109 which states: Nicht Betreten gets very blurry and unreadable...
the crosshair becomes less and less visible, and if you set textures to medium, it becomes indeed invisible.

i made already two entries for this issue, but now due to further testing, i came to the conclusion, that the B-Beobachtung(Observer) bullets just lost their explosive effects.thats definitely wrong.

maybe thats something to do with the fact, that you now cant blow up those fuel storages in industrial areas Luthier???
before this patch, it was indeed only possible to blow them up with only MGs, if you had B-Beobachtung in your belts...
if that is the solution to make a more correct damage model for those fuel storages, then thats indeed the wrong way....

decals for small calibre hits are still missing....or do I have to change sth. in the settings? cant play with my PC atm, just testing with my laptop on medium settings.

Can anyone confirm that small calibre hits are still not drawn?!

apart from that the overall smoothness is much improved with my laptop! good work gents!

Launcher crashes 100% of the time, shortly before the mission loads. I have repeatedly attempted the update, reinstalled Direct X, reinstalled .NET 4.0 (from the redist folder), removed my newer V C++ and tried the one in the redist folder, cleared the cache, manually placed files in each location etc. I'm on Win XP 32bit, and have no issues running the official version.

Event Type: Error
Event Source: .NET Runtime 4.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 10/9/2012
Time: 2:31:22 PM
User: N/A
Computer: *********
Description:
Faulting application launcher.exe, version 1.0.0.0, stamp 4d6e3d08, faulting module core.dll, version 0.0.0.0, stamp 50659306, debug? 0, fault address 0x000e6c65.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00700041 006c0070 00630069 00740061
0010: 006f0069 0020006e 00610046 006c0069
0020: 00720075 00200065 006c0020 00750061
0030: 0063006e 00650068 002e0072 00780065
0040: 00200065 002e0031 002e0030 002e0030
0050: 00200030 00640034 00650036 00640033
0060: 00380030 00690020 0020006e 006f0063
0070: 00650072 0064002e 006c006c 00300020
0080: 0030002e 0030002e 0030002e 00350020
0090: 00360030 00390035 00300033 00200036
00a0: 00440066 00620065 00670075 00300020
00b0: 00610020 00200074 0066006f 00730066
00c0: 00740065 00300020 00300030 00360065
00d0: 00360063 000d0035 000a




*****

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1026
Date: 10/9/2012
Time: 2:31:41 PM
User: N/A
Computer: ****************
Description:
Application: Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at <Module>.corelib.RenderWorld.Render(Boolean, Boolean, Boolean, Boolean, Double, Double)
at maddox.core.WRenderWorld.Render(Boolean, Boolean, Boolean, Double, Double)
at vyXPxPXK6qtT2JHtn7W.oF8cKOXlBfDuHiT4EgV.DyjcDmCq9b v(Boolean)
at vyXPxPXK6qtT2JHtn7W.oF8cKOXlBfDuHiT4EgV+JmTo5OXzMw A9EmAfAKk.uliXwTdI3VbVcqUROuYr(System.Object, Boolean)
at vyXPxPXK6qtT2JHtn7W.oF8cKOXlBfDuHiT4EgV+JmTo5OXzMw A9EmAfAKk.render()
at fqUEJHFbcMMmuBqa6LK.4S1nwK7z21Ly9mYxPwE.QrUnlsy0il c()
at fqUEJHFbcMMmuBqa6LK.4S1nwK7z21Ly9mYxPwE.MbNnlVgfg3 u(Boolean)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.dGdhXOXhfr 9LCN84s7u(System.Object, Boolean)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.hVuJhI9Da5 (AZAKS3AEO5F0ZUdYNA9.Q0jqMCADgLe2tQDtS9O)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.p8u9RxClFE ygk4ssMyR(System.Object)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.HMDJJU7HJl (AZAKS3AEO5F0ZUdYNA9.Q0jqMCADgLe2tQDtS9O)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.bajJpZVOmt (System.String)
at xPW984J2CbB6GNlqet0.gwDsDSJdID5e8aYY9Ka.MissionLoa d(System.String)
at ZIfAD49Z7ds5I7Rir6A.iaVYEV9SQk2F93rCdgV.jPvnoorJU5 L()
at System.Threading.ThreadHelper.ThreadStart_Context( System.Object)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Don't forget that the 109 have a nose down attitude flying straight and level ! The only way that you can be sure you fly level is by closely watching your altimeter. Then you can reach the max speed. If 500kph is hard to reach deck without a very shallow descent, 490ish is relatively easy.

Sry for nursing you that way but it's not specifically after you. I am just fed-up to read that claims here and there again and again...

~S!