TrackIR problem solved, NOT patch
 

Figured out my problem with Track IR, its not the game or patch....just updating for those who read this.

I agree, this update brought with him also a lot of other visual problems. I must to return to the previous patch version. Only environment colors were good. Sad to say, but anyway this new beta patch is poison my PC configuration and eyes. ;)

Hi,


have maybe the same TFT as you, a Samsung 23". Problem remains even after updating my Track IR5. Opening the software itself and game too, my view is spinning, turning around.

Mee too

Nvidia driver´s 270,61

new beta patch...
 

... I also experienced after maybe an hour online flying that the game crashes. Had to reboot pc. Teammates told me the same.

Still flickering shadows close to the ground.

No flakexplosions can be heard anymore. Was testing it in the replay of recorded flight in external view, while flying through clouds of flakexplosions.
No explosion sounds anymore. Only when landing and flak was shooting close to airfield, you can hear some faint explosionsounds in external view.
Dont know what is more realistic, the way it was before or now?

Sunlight effect when turning your nose into the sun is also somehow strange. No sight on instruments anymore until you turn away. Doesent seem too realistic to me.

Hope this and some more issues reported by others will get fixed before final steam release of the patch!

Overall impression - new patch brings definitely an improvement to the sim!
:|

Patch is great but there's just a few things to be considered in the RA planes.

1) Where is the WEP ("+100Mmhg") on the G.50? It's still missing
2) the bombsight in the BR20 is still broken...
3) The new sound are great but those Breda SAFAT are really awful...

Cheers and thank you!

No, thank you for flying the italian machines. ;-)

Crash to Desktop C++ runtime error, happening more frequently - never happened pre-patch.

A minor graphical glitch on the Spitfire MK Ia.

Red light right sides "Fuel pressure low" is visible in external view .

Same here, cannot fly it at all.

I also have to echo the comments about sunrise and sunset, it looks awful now :(

Darn double post :/

Yep same here, my first ctd's. You can fly outside view, but as soon as in cockpit CTD.

FPS, sounds and colours great btw

I have problems with switching view to desktop. When playing quick mission only flying and sightseeing it's ok. When I load some mission with action, after some gun firing game freezes, then minimize. I get desktop. I can't switch to game (even with alt+enter). It brings me immediately to desktop again. If I'm quick enough with alt tabbing and then ESC I get in game menu. But when returning to fly again desktop. I must exit game and start it again. I haven't got this problem before.

Pics are posted on 3rd side. I was set epilepsy filter off and now is everithing ok.
Latest Nvidia drivers.
conf.ini

[BOB]
EpilepsyFilter=0

[window]
DepthBits =24
StencilBits=8
DrawIfNotFocused=0
SaveAspect=0
Render=D3D10_0
width=1680
height=1050
posLeft=0
posTop=0
ColourBits=32
FullScreen=1
ChangeScreenRes=1
Frequency=59

[NET]
speed=100000
localPort=27015
serverName=My Server
serverDescription=IL-2 Sturmovik: Cliffs of Dover
serverInfo1=
serverInfo2=
serverInfo3=
serverInfo4=
VAC=1
maxPlayers=16
socksEnable=0
socksHost=
socksPort=1080
socksUser=
socksPwd=
host=216.52.148.29
port=27016

[Console]
IP=20001
UseStartLog=1
WRAP=1
PAUSE=1
HISTORY=1024
HISTORYCMD=1024
PAGE=20
LOG=1
LOGTIME=0
LOAD=console.cmd
SAVE=console.cmd
LOGFILE=log.txt
LOGKEEP=1

[rts]
tickLen=30
ProcessAffinityMask=14
maxTimerTicksInRealTick=20
; 0 - not use, 1 - show cursor and not capture, 2 - not show cursor, and capture
mouseUse=2
; 0 - not use, 1 - use if hardware exist
joyUse=1
; 0 - not use, 1 - use if hardware exist
trackIRUse=1
DisableIME=0
culture=en-GB

[rts_mouse]
SensitivityX=1.0
SensitivityY=1.0
SensitivityZ=1.0
Invert=0
SwapButtons = 0

[rts_joystick]
FF=1

[core]
RandSeed = 0
TexQual=2
TexFlags.PolygonStipple=0
Shadows=1
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
LandShading=2
LandDetails=2
Sky=3
Forest=2
VisibilityDistance=3
LandGeom=2
DrawCollisions=1
Water=1
Effects=2
EffFlags.Light=1
EffFlags.SpriteRender=0
Grass=3
CordEffect=1
UseFog=0
UseLandCube=1
UseLandConnectedObject=1
LinearObjectManager=1
Roads=1
Sun=1
Clouds=1
EffFlags.LightSpritesProj=1
ShadowMapSize=5
TexFlags.AsyncLoad=1
TexFlags.ShowTexture=0
SimpleMesh.SWTransform=0
SimpleMesh.QuadTreeClip=1
SimpleMesh.InstancingHW=1
EffFlags.LightContextSprites=1
CloudsFlags.Detailed=1
TexFlags.CreateHDR=1
Decals=2
EffFlags.SWLight=0
TexFlags.CockpitOnePass=0
MegaTexture=0
TexFlags.Reflection=0
RenderTargetQual=3
MSAA=2
MeshStatics=2
MeshStaticsDetail=3
SimpleMesh.QTNoCompose=0
MeshFirstLod=0
MeshShowLod=0
SpawnHumans=1
TexFlags.SSAO=0
TexFlags.VSync=1
TexFlags.FastTransparency=1

[sound]
SoundUse=1
DebugSound=0
SoundEngine=1
Speakers=1
Placement=0
SoundFlags.reversestereo=0
RadioFlags.Enabled=1
RadioEngine=2
MusicVolume=14
ObjectVolume=7
MusState.takeoff=1
MusState.inflight=1
MusState.crash=1
MusFlags.play=1
MasterVolume=14
Attenuation=7
SoundMode=0
SamplingRate=0
NumChannels=2
SoundExt.occlusions=1
SoundFlags.hardware=1
SoundFlags.streams=1
SoundFlags.duplex=1
SoundExt.acoustics=1
SoundExt.volumefx=1
SoundFlags.voicemgr=1
SoundFlags.static=1
VoiceVolume=8
Channels=1
SoundFlags.bugscorrect=0
SoundExt.extrender=0
SoundSetupId=8
ActivationLevel=0.02
Preemphasis=0.8
RadioLatency=0.5
AGC=1
PTTMode=1
RadioFlags.PTTMode=0
RadioFlags.PlayClicks=1
ActLevel=9
MicLevel=10
SoundFlags.UseRadioChatter=0
SoundFlags.AutoActivation=0
SoundFlags.forceEAX1=0
speakers=1
vgMaster=7
vgVoice=7
vgMusic=7

[game]
mapPadX=0.05
mapPadY=0.1104762

Guns sounds far too low
 

The guns sound volume is too low

errrr... how do you know? have you been in a WWII fighter shooting somebody? :grin:

Yep Gun sounds too low in the RAF planes, also no change in sound when opening and closing canopy. Even a slight muffling of sound when canopy closed would be good if possible Luthier?

State of sunwashout now:

After patch... looks awful in my eyes:

http://dl.dropbox.com/u/7721109/IL2%...908_110315.jpg

And pre-patch:

http://dl.dropbox.com/u/7721109/IL2%...908_110818.jpg

I got the static shadows on the gauges back in the 109 (didnt check remaining planes)
When i remember correct, these were already introduced in the first CoD version.
http://img220.imageshack.us/img220/3...1090700030.jpg

Stutters in low level flight (below 300m) got more.When deactivating the trees stutters are gone again!
As trees have no function but eyecandy, ill keep them deactivated online to gain more perfromance in MP.

FPS drop of 10-15% at all towards version 1.02.

Noticed flaws on two of the new MP maps (attached shots)

(i7 920@3.99ghz;HD5870;6gig Ram;Win7 64bit)

Kinda right tbh :cool:

Fiats were crap but hey... it's fun to fly crap planes!

Had I the possibility to fly a Defiant or even a Battle, I'd be the first one to fly it consistently. ;)
And somebody has to do it!

Cheers

COrn/wheat in fields coming through bottom of cockpit.

Used to have a Moto Guzzi SP1000 (couldn't afford a Le Mans III) and recently sold my Alfa 156 for a Fiat 500 nuevo.
Italian engine craftmanship has improved for sure!! :-D Alot of soul in those machines.
I'd kill for a Maserati GT Quatro Porte but then I would have to kill again to afford the annual service. :-D

Hey, you're supposed to report bugs, not features. Bon Apetit!!:-P

Yup, i noted that in my earlier post to nephris. One other thing i had not long ago that i should chuck in, i started getting heavy stuttering a few minutes into a flight. I thought the game was going to come to a standstill and lock up. Hit escape and turned tree's off, silky smooth again.

The sound of the bullets wich hit the plane of the pilot
 

The sound of the bullet holes that affect the aircraft is not strong enough
as the guns sound. I think it is necessary to fully immerse themselves in the game as if it is not entirely exact

you can stop the engine in the BETAversion ?
because in the prebeta magnetos and fuelcocks (in cockpit mousecursor and shortcuts)are not working in the G.50.

Also in my opinion, and flying at extremely low altitude near QFL (Quota Filo Erba in Italian :)) it look quite worst compared to prior the patch.
Maybe because there's a sort of blu/grey filter applied to the whole screen.

In the HE-111 the bomb sight altitude increments are not displaying right there fine up until 1000m then look like this 960 970 980 990 1000 1000 1000 1000 1000 1000 1000 1000 1000 1000 1100 1100 1100 and so on.

Dropping bombs from the bomber position works thanks for that.

Hi Vengeanze, I'd kill for a Maserati Granturismo, awesome car.
But I'd kill twice for mantaining it as well :)

JG53Frankyboy: you're right. The engine can't still be stopped in the G.50, justr tried it out. Magnetos don't seem to work.

The ambient sound (other plane, vehicles...) change when canopy is closed, the engine sound sometimes change, sometimes not

I have seen wingtip vortices (condensation trails) hang in the air permanently at least one after a plane producing them has crashed - one possible occurance (though it may be a trail from something else) can be seen in "the black death" track, the other I saw while playing online.

Edited this post to revise.

Don't if it has been reported already:

BF109 E4/B is not dropping bombs!
I press the ordenance release key (working perfectly with Ju87 and 109 E3B) and bombs just dont leave the bomb rack.

Weird :D

Last night I followed a Hurricane down in flames and the the fire was coming from the side of the plane, bout two inches to the right and not from the actual plane itself.

Hi. How do I completely turn off the clouds. The largest decreases FPS I have now because of the clouds.

Q6600, 3.0 GH, Gf 9600 GT, 4 GB Ram, Win7 64 bit.

Admittedly, I noticed on my PC not too strong, that the inclusion of Land shading on the medium does not cause such a drastic drop in performance as before the patch

this is what i noticed so far..
-Horizonmeter in Cockpit still no work correct (it goes contra here)

- saw a train going over a moutain over the moutain top instead of going through the tunnel and after it was not on the tracks but on the left of it besides the tracks

-i still see no crews at AAA guns or anywhere else for that mather

-in a BF109 i cannot slide ope the cockpit window on left side when have internal view

-the sound is very fainth and setting is at the loudest the voices however are about 8x as loud as theplain sounds internal and external

-still the AI pilot is very poor he just follows the waypont ines and does not reacte on any enemy plane

-no campaign missions for new airplanes

- a good and inelligent AI is welcome for me aswell as good campaigns (the campaigns now are total crap) because i have to go for business all over and 90% it's crap internet so i cannot fly online, but with IL-2 1946 i could entertain myself for hours just by letting the AI fly for me in my hotelroom. That i cannot do anymore and i miss that dearly tbh..

-The AI pilots crash into a lot with me

-I hardly ever see flak when fly over enemy territory.

-Goog things are the colors and less stutters atm since the patest patch. (LOVE THE COLORS) Keep up that good work aswell as the new sounds they are very good.

Ok well maybe you have some kind of super-eyes that can look directly into the setting sun and still see stuff, but I can't. That washed out look is exactly what happens to me when I try to, for instance, drive towards a sunrise or sunset. It's because the irises in your eyes close to pinholes. It is actually quite a convincing lighting effect.

My problem is that it happens too much and gets annoying but it's a good effects just they should make it only happen when you look directly at the sun not when it has just slightly crept into view.

Please re-read my post, all I said was that it looks awful to me, nowhere did I state anything about how realistic or not it might be.

i read the Ju88 Gyro compass is still not working ?!
If true, it would be nice to have a look in it :)

Don't know if it's been mentioned yet but after a bit of damage the mirror shows up when it is turned off. Only seen it on a hurricane though.

you mean like this? it's old bug but they never said anything about it, it's like you have 2 cockpits


http://i56.tinypic.com/2num9w2.gif

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

No dont like it at all...bad patch... is a step backward in my opinion, the sound is ..ok... the colours are awful and make whole sim seem like a GAME , my fps is better but the game crashes more often , if this becomes a mandatory install then that will be about enough of this rubbish for me , the whole process has become so tiresome and tedious for what looks to me like one step forward and two steps backwards with every new patch.

guy... it is a BETA patch!

Taking a note from Insubers thread here is a compilation of the bugs found so far.

1. FPS Drop (Roughly 10%).

2. Gunsight Dimmer no longer works.

3. Landing gear hydraulic noise can be heard when player switches to neutral gear down postion.

4. BF 109 E4 Window opens up the wrong way.

5. BF 109 E4 Can't drop bombs, SC50 bomb rack positioned incorrectly.

6. BF 109 E4 No Auto Prop.

7. BF 110 Instrument Panel lights are always on.

8. BF 110 No mine shells!!!

9. Cockpit glass appears opaque rather than transparent in outside views.

10. Target Dots should be modified and removed from ground targets and can be seen through ground and clouds.

11. Tiger Moth can crash the game.

12. Black areas in red out and injured pilot effect.

13. Contrails need work, they do not start off at the wing tips and are a bit to thick at the beginning.

14. Sun blinding effect needs more work, happens to often.

15. Horizon can be seen through aircraft.

16. Game crashes more often.

17. Sometimes you can hear cockpits after bailouts.

18. Stuka smoke cant be seen by pilot, but can by other players.

19. Stuka rear gunner ammo hang in mid air after canopy ejection.

20. Ammo counters don't work (needs verification).

21. Effects have a box/outline. Nvidia users can remove this by rolling back to patch 275.33.

22. Lights visible through cockpit.

Furbs do you want to add this to your original post?

Rgr, cheers!

Whoooosh!!!

It's a beta so we can report bugs we find and air our opinions on it.

Gonna check the counters myself, just was compiling the comments from all users and only those specific to the patch.

Rolling back (and I assume you mean driver version rather than patch) had no effect on my system, effects still show boxed outlines.

Sorry my bad. Yes it was confirmed by Tree and another user supposedly.

True, true and true

Another bug to add Furbs.

We still see the old E1/E3 cockpit in the E4 instrument panel reflections :confused:.

I know its not a real time reflection so they just need to take another picture... not too much work hopefully.

Hi friends, I have a question for all....

It is posible bomb with the 109 E3B or / and E4B online and offline with the new Beta patch ????

I am configuring setting to bomb... but me bombs dont exploude....

Need help...

It should work everywhere with the E3B, but I have problems offline (probably me) but E4 is bugged.

Probably reported but with beta patch i got many CTDs - every my game was crashed after some time.

http://forum.1cpublishing.eu/showthr...380#post333380

I got Quad 3.0, 4 GB Ramm, GTX280, Win 7 64 bit, graphic drivers 197.45

Im having alot of FPS drops when Ive got effects going off in front of me..explosions etc

Didnt have this before patch

Same here, dust, clouds and anything along those lines cause massive drops in frame rates now.

also when your engine in a spit caught fire

Yes I think the same. Talking about it, I like very mutch what happens looking to bright places when I play ARMA2, like the irises that need some time to adjuste itself to the new bright level and after that you can see better

+1 and dont work SLI

Aircraft Showing Wheels down.

They do that when landing Tree you damned VULCHER :P.

Well, no doubt there is some kind of memory leak present now... Have been playing multiplayer the last three nights which must be the first time ;) Like many others have reported it crashes after about an hour. Looked down on my Logitech display last time it got stuck (10 mins ago) and it was on 65% memory usage... And as I have 8Gb that sounds leaky to me as the game previously was on about 44% when I checked half an hour earlier. And it gets completely stuck and I have to use the task manager to kill it. Memory dumps available on demand ;)

Was flying the Spit and shot down a 109. I opened my canopy when next to the burning 109 you can hear the pilot screaming in horror and agony. Nice touch.

you r joking right

Planes still moving too much on the ground - ie I spawned into a plane and it was sliding backwards down a hill! Eventually slid so far and fast it blew up! Also planes slowly rotating on the ground even though engine isnt started yet.

"Was flying the Spit and shot down a 109. I opened my canopy when next to the burning 109 you can hear the pilot screaming in horror and agony. Nice touch."

Seriously !!! and with open canopy .. please do something about that.. Is this became a game?

That's the red-out/wounded effects artifacts i saw in the 109E-4. So i guess it's a universal thing. Good, because it probably will be easier to fix that if it was specific to a single cockpit :-P




Have a look at the sticky FAQ thread on the main forum page, the first thing it explains is how to configure the info windows.

For starters, make sure your mouse cursor is enabled (default toggle key is F10 to switch between mouse look and mouse cursor), then hold down your alt key and left click on the window to select it. Now that it's selected you can right click on it to display the menu and select "close" from the options there.



It will automatically overwrite it like it did for every other patch up till now ;)




The flaps on the 109 are manually operated, to simulate this you need to keep the button pressed otherwise the moment you stop pressing it they stop retracting/extending. They work fine for me.




Radio commands were not supposed to be in this patch because they are not finished yet (new ones are being added on top of the previously existing one). Some of them work, the rest are placeholders (just the titles/text in the menus). That being said, some of the new placeholder fields in the radio commands menu are very promising. Fly a bomber and have a look, they are apparently working on individual crewmen commands ;)




That's an old issue with the track viewer and not specific to this patch.

The problem is probably the CEM, it's way too complex to have it on for all aircraft (costs about 10 FPS per aircraft), so the AI are simply flying with artificial rules in place so that they don't "cheat" and not the full CEM available to us.

That's probably what's confusing the track player, since track playback is essentially an AI re-run of your control inputs during the mission. It's a known issue, so i guess we'll see fix for it at some point. Probably they will make the tracks record the CEM parameters too on top of our stick inputs, but i don't know how that would play out for tracks taken in multiplayer with a bunch of aircraft needing "CEM rules" enabled for the track.




Hahahaha, cool story. Gasoline or not, flying a 6 hour escort deep into Germany and back, or even worse, a shuttle mission to Russia would surely get tedious at times: i woudn't settle for just an ashtray, i'd ask my ground crew to fit a folding dinner table and maybe a portable toilet too :-P

Flying Spit IIA and noticed a few bugs:

1. Sometimes the engine sound cuts completely instantly on negative g instead of spluttering a bit first (bug?)

2. Headshake is far too strong now. I don't care if this is realistic (which I doubt) but it verges on unplayable with headshake on. EDIT: It was my freetrack! Sorry about that, a corrupted profile...

3. Mirror bugs seem even worse after patch? They always flickered on when you got a bit close (ahem) to an enemy plane but now they also seem to respond to damage sometimes with weird colours that look a bit like heat maps. I'll try and get a screenshot.

Bug: White dots appearing attached to all units (ships/planes/aaa etc) - often visible through land:

http://img32.imageshack.us/img32/7159/aircraftd.jpg

http://img856.imageshack.us/img856/161/ships.jpg

This is new with this patch, wasnt present before.




Nvidia GTX 570, most graphics options maxed out.

Confirm this as well, ATI 5780 11.6...

Love the air pollution, but unfortunately it doesn't mask the incorrect green terrain tiles of London when viewed from a distance:

New bug.

When you get close to a ju88 (player aircraft at least) you see a lot of smoke coming from the engines and a massive decrease in fps.

Is that before or after you've shot him? ;)

I want add that the blenheim don't release the bombs also.

Merlin engine cuts too readily on negative G. This has been covered before and was improved before this patch. Please revisit.

I have 5.1 6-channel sound (front pair, rear pair, centre and subwoofer) on my headphones. When I close the canopy the engine sound levels do not change but a friend with stereo phones says the engine sound reduces when he closes his canopy.

I wish I knew which FM is correct in this regard. This and the earlier models are harder to fly but more satisfying (and really not that difficult) but I suspect they are incorrect.

Love the new sounds and new coloring, got a few bugs though.

1. Often when looking straight ahead there is no engine sound after start up, sound is there when looking left or right but not straight ahead on both E-1 and E-4. This is an intermittent fault, if it's ok when you spawn no problem, but next time you spawn it may be faulty and will stay so unless you respawn a few times.

2. No sound from the nose mg's of the 109 E-1, and E-4

3. The glare when looking toward the rough direction of the sun is a bit overdone I feel, at the moment as soon as you look anywhere that the sun is on screen you are affected. It is a cool effect but should be more specific to when the sun is near the center of the screen. Are AI affected by this in any way?

4. Occasional launcher crashes, 3 in 6hrs of play


Specs.
i7-950
Asus Sabretooth MB
6gig corsair 2000mhz ddr3
Asus GTX580 1.5gig 260. Drivers from memory
120gig SSD win7 64pro, CloD, RoF, ARMA II
1Tb seagate storage drive
1000w corsair psu
24" LED Benq monitor
Logitec 5.1 speaker system
CH 568 combat stick, pro throttle, pro pedals
TrackIr 5


Most settings are high/medium apart from forests set to low
Game plays smooth as silk, with only occasional stutter when bomber flights or custom skins load!

Over all, I like it, very promising!

Cheers
Craig

clocks in at least the german airplanes no longer work

Also now getting launcher crashes now I've started attempting to fly missions, this is what's shown in my event logs:


Log Name: Application
Source: .NET Runtime
Date: 09/09/2011 10:39:18
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: BUCKET
Description:
Application: Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at System.RuntimeMethodHandle._InvokeMethodFast(Syste m.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)
at System.RuntimeMethodHandle.InvokeMethodFast(System .IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)
at System.Reflection.RuntimeMethodInfo.Invoke(System. Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.Invok eImpl()
at System.Windows.Threading.DispatcherOperation.Invok eInSecurityContext(System.Object)
at System.Threading.ExecutionContext.runTryCode(Syste m.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, 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.Windows.Threading.DispatcherOperation.Invok e()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.InvokeImpl(Sys tem.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame)
at 8bmNtSUta20YjMe6dtA.rA8OfiU8vkvdyWuW0mx.b61XQqm8xc d()
at 0om9nvUxwie5DBGtYiZ.FFA4GGUKKnOrk510583.dQ33G9ZnfY 1d1KMHGHEL(System.Object)
at 0om9nvUxwie5DBGtYiZ.FFA4GGUKKnOrk510583.907h67V0QZ N(0om9nvUxwie5DBGtYiZ.FFA4GGUKKnOrk510583, System.String[], System.String, System.String)
at 7lZ0hMxlcF9iXr2DQKW.ISVLmDxsWjl4fjhmwoj.xWVsgLE4qm l(System.String[])
at maddox.Launch.Program(System.String[])
at Launcher.Program.Main(System.String[])

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-09-09T09:39:18.000000000Z" />
<EventRecordID>9527</EventRecordID>
<Channel>Application</Channel>
<Computer>BUCKET</Computer>
<Security />
</System>
<EventData>
<Data>Application: Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at System.RuntimeMethodHandle._InvokeMethodFast(Syste m.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)
at System.RuntimeMethodHandle.InvokeMethodFast(System .IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)
at System.Reflection.RuntimeMethodInfo.Invoke(System. Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.Invok eImpl()
at System.Windows.Threading.DispatcherOperation.Invok eInSecurityContext(System.Object)
at System.Threading.ExecutionContext.runTryCode(Syste m.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, 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.Windows.Threading.DispatcherOperation.Invok e()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.InvokeImpl(Sys tem.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame)
at 8bmNtSUta20YjMe6dtA.rA8OfiU8vkvdyWuW0mx.b61XQqm8xc d()
at 0om9nvUxwie5DBGtYiZ.FFA4GGUKKnOrk510583.dQ33G9ZnfY 1d1KMHGHEL(System.Object)
at 0om9nvUxwie5DBGtYiZ.FFA4GGUKKnOrk510583.907h67V0QZ N(0om9nvUxwie5DBGtYiZ.FFA4GGUKKnOrk510583, System.String[], System.String, System.String)
at 7lZ0hMxlcF9iXr2DQKW.ISVLmDxsWjl4fjhmwoj.xWVsgLE4qm l(System.String[])
at maddox.Launch.Program(System.String[])
at Launcher.Program.Main(System.String[])
</Data>
</EventData>
</Event>






Log Name: Application
Source: Application Error
Date: 09/09/2011 10:39:18
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: BUCKET
Description:
Faulting application name: Launcher.exe_Launcher, version: 1.0.0.0, time stamp: 0x4d6e3d08
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe0434352
Fault offset: 0x0000b9bc
Faulting process id: 0xdec
Faulting application start time: 0x01cc6ed3e57ab79e
Faulting application path: C:\Steam\il-2 sturmovik cliffs of dover\Launcher.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 9669b553-dac7-11e0-8ba9-f46d04157eaa
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-09-09T09:39:18.000000000Z" />
<EventRecordID>9528</EventRecordID>
<Channel>Application</Channel>
<Computer>BUCKET</Computer>
<Security />
</System>
<EventData>
<Data>Launcher.exe_Launcher</Data>
<Data>1.0.0.0</Data>
<Data>4d6e3d08</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.17651</Data>
<Data>4e211319</Data>
<Data>e0434352</Data>
<Data>0000b9bc</Data>
<Data>dec</Data>
<Data>01cc6ed3e57ab79e</Data>
<Data>C:\Steam\il-2 sturmovik cliffs of dover\Launcher.exe</Data>
<Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
<Data>9669b553-dac7-11e0-8ba9-f46d04157eaa</Data>
</EventData>
</Event>

same on JU-87`s

Part of the aircraft paint + great customizing "visual weathering" effects do not works anymore correctly this beta patch (sometimes), also some with a number of squadron numbers of the characters changed too gray in color → example when these should be in black.

The massive clouds became too white (day time) - The previous version, also all of these were in my view quite well (the cloud textures intermittent flashing of the reading, the texture flickering does not appear only in the clouds, but it does occur from time to time in many other textures (little flickering – not all place or all the times). User videos please note that the same problems occur also with other PCs configurations - the latest nVidia graphics cards driver install just removed this problem "GTX 500 series", but not completely my case).

The above-mentioned problems are particularly unpleasant to CloD film-makers. I had yet to return to the previous version because of these (however that is yet beta patch).

In fact, I considering seriously, so anymore meaningful to do make sim machinima, maybe must be near future switch completely to make only 3D animations short films, because game world's is limited access (I mean also gameplay camera views handling etc.) and numerous visual problems are perpetual absurdity, and I think this is precisely the fact which makes this very difficult and unnecessary time-consuming work, when forced to take the same scene several times in the video captures, and hope that one of them should not be the graphics texture problems (My case 40% CloD movie making time lost this - will always think about and apply that to how to circumvent the many problems and i don't mean only visual problems).

A number of games, bugs and bugs are an eternal problem, and it just seems to grow with it what we often, in particular, these simulation games are changing.

However I understand very well aware that this is not really no longer an easy thing to do on each PC configuration fully functional games, especially on this scale hardcore simulators like example CloD is. Clod is best WW2 sim anyway and RoF is best WW1 combat fly sim a today = Very hard and difficulty projects - But of course this is just my opinion.

Many of the radio commands still doesn't work. Hopefully they will in the final patch?

Cable in the sky ???
 

A cable cut the sky

Unable to turn weathering off on Spitfires??

Track-Ir will no longer center via F12 while in game, I have to alt-Tab out, Center then alt-tab in, had the same problem for a little while when I first installed 2 patches ago so I'm not sure if it's related to this patch. Can still see object "dots" through aircraft, terrain, not as bad as before but still visible. Seems like brakes on Spit and Hurri are either full on or full off and if they are on a key press a single tap can ground loop an aircraft, is this correct?

Hey guys I just created a how-to thread in regards to the importance of making your crash dump files available for download for the developers and how to upload them to the forum.

For those who have had the game crash with the beta patch its worth doing to help the developers fix up any issues.

Here's the thread: http://forum.1cpublishing.eu/showthread.php?t=26007

Was going to build a mission on the channel map and this happened for no apparent reason:

Looks like more "vegetation" issues.

http://cloud.steampowered.com/ugc/57...647054FFAD7C9/

I'm getting weird discoloured german tactical codes. For example what was black before is now a very dark grey ... as if the new gfx adjustments have a negative influence on the markings. The Balkenkreuze, however, are fine. Curious issue ...

Are you sure? First thing i tried with the new patch was the Blenheim to test the bombsight. Bombs released fine and i got some good hits on the target ;)


That's because they didn't announce they would have completed radio commands for this patch, it's only the graphics and new sounds for this one. What you see in the radio menu is mostly placeholder commands that will come in another patch ;)

Strange.. Mine still works Bong.. what version of TIR do you have? I have 5 with the latest software running.. Sounds like you have the F12 key asigned in game maybe? As in the game is digesting the F12 press before TIR sees it.. Maybe try asigning it to a different key that you know you are not using in game and see if that works

Not sure if this has been posted allready?

Not sure if this is a ground physics bug or an aircraft bug.. But basically the wind is causing the planes to spin while sitting on the ground.. And by ground I mean grass field, not cement runway. It is most notable in the Spitfire..

And it happens at very low wind speeds, much lower (more than half) than the min speed that warnings would be sent out to local air fields in the real world.

Change the default key from f12 to numlock

Still cant change ammo in SP?

really? from the pilot view or bomber view? I tried only from pilot.

today flying online on REPKA server my FPS dropped at about 1 FPS/sec. had to exit and reconnect, never happened without the beta patch. Also seems that the flames from the exhaust are a big FPS hit now.

[QUOTE=Krt_Bong;333803]Track-Ir will no longer center via F12 while in game, I have to alt-Tab out, Center then alt-tab in, had the same problem for a little while when I first installed 2 patches ago so I'm not sure if it's related to this patch. QUOTE]

I switched to F11 for this long ago and all works fine.

[QUOTE=Catseye;333977]I cleared all view keys as I have TrackIR and set centring on keypad 8. I use F9-F12 for Teamspeak/Ventrilo channel and whispers as they are also redundant for me in CoD/Il-2.

Not sure if it's related to sound but if it is it's worse than the previous sound bug.

Sound stops and game freezes. have to ctrl alt delete out. never had this problem.

Gollum

bugfix BF-109-E4 ...
 

... the clock is not working properly. Only the handle for the minutes is moving, the one for the seconds is not.
Also noticed that there is no force feedback when flying the Emil-4.
On all the other planes I have force feedback on my MS Sidewinder FFB2.
Not so on the Emil-4.
Would be nice to get that fixed in the final version of the new patch !

Thank you.
:)

I don't have time to read the entire thread for repeats but here are my findings. All these bugs were experienced online on the ATAG server. Probably this late in the list nobody will read it anyway.

1. Sound bug, after a respawn the spitfire engine sounds very quiet and like a bee buzzing, the airflow sound was almost louder than the engine. 2 respawns later the sound came good again.

2. No cannon sounds in MP.

3. No FFB on shooting, probably a good thing as it's overdone on the 109.

4. Right after takeoff the screen froze and the Spitfire cockpit I was in disappeared. The game didn't crash however, chat and the menus still worked but the landscape was frozen. A respawn fixed this.