BETA PATCH v.1.08.18956 - August 3, 2012

[flyingblind]

They also seem to be off by default when you start a mission. But they are still a chocolate teapot for seeing what is behind you.

[DairyAir]

Precisely.

I.M.H.O.
As indicated in several charts of the time period.
The cut-out should not occur until the aircraft reaches -.9G.
Not as it is now, where the slightest nose down, causes an instant cut-out.
Accompanied by an equally unrealistic airspeed drop. Mass and Momentum of the Aircraft damp this Airspeed loss down considerably in real life.

2 cents Eh!

Originally Posted by Bokononist

Dairy.air is well aware that it is a factual issue, which is why he is using real life facts (he flies a cessna with a carburreter fed engine) to suggest that the negative g cutout is not modelled correctly.

[IvanK]

Originally Posted by DairyAir

Precisely.

I.M.H.O.
As indicated in several charts of the time period.
The cut-out should not occur until the aircraft reaches -.9G.
Not as it is now, where the slightest nose down, causes an instant cut-out.
Accompanied by an equally unrealistic airspeed drop. Mass and Momentum of the Aircraft damp this Airspeed loss down considerably in real life.

2 cents Eh!

As posted the Actual documented figure is Neg G effects commence at +0.1G that is a 0.9G decrement from 1G flight. What we NOW have in Ver 1.08 is pretty close to the mark.

If you are not running Ver 1.08 you will be seeing the Old value that was way to sensitive.

WRT to Dates. The Schiling orifice didnt come into service until Post BOB. The graphic below comes from the UK National Archives document AVIA 13/234. The image is the first page of this file and is a covering minute to the file. As you can see its dated 21St Feb 1941. This document is the source document with measured G onset values of the cut as well. As can be seen even in the covering minute the values of +0.1 ---> 0g is quoted. This has all been debated (and proven) in numerous debates on this forum over the last 12 months.

[DairyAir]

I stand corrected.

IvanK is correct, Ver. 1.08, does in fact feel pretty good.

Originally Posted by IvanK

As posted the Actual documented figure is Neg G effects commence at +0.1G that is a 0.9G decrement from 1G flight. What we NOW have in Ver 1.08 is pretty close to the mark.

If you are not running Ver 1.08 you will be seeing the Old value that was way to sensitive.

WRT to Dates. The Schiling orifice didnt come into service until Post BOB. The graphic below comes from the UK National Archives document AVIA 13/234. The image is the first page of this file and is a covering minute to the file. As you can see its dated 21St Feb 1941. This document is the source document with measured G onset values of the cut as well. As can be seen even in the covering minute the values of +0.1 ---> 0g is quoted. This has all been debated (and proven) in numerous debates on this forum over the last 12 months.

[Outlaw]

Originally Posted by Baron

(As far as i know we still cant assign vital functions to keys, can we? Isnt working for me at least ).

I have not changed my key/stick mappings since the initial US release and I can control everything required for CEM without the mouse.

--Outlaw.

[Baron]

Originally Posted by Outlaw

I have not changed my key/stick mappings since the initial US release and I can control everything required for CEM without the mouse.

--Outlaw.

Finally got it to work to. I have no idea why it hasn't worked before.

Makes flying and df`ing at the same time a whole lot easier let me tell you.

[4./JG53_Task]

Can anyone help me with this issue. I can not find a solution after trying everything anywhere.

I just bought/downloaded the game on steam, verified the game cache, THEN unrar'ed the beta patch folder 'parts' into my main CoD root folder and overwrote anything that it asked me to.

Now when I try and start the game, either normally and also tried running it as administrator, the launcher spits out an error saying "Launcher.exe has stopped responding" and the game simply doesn't start.

I followed the instructions exactly, my flight buddies did the same thing with no issues, but I'm having some f'ing bad luck here.

[Anders_And]

Originally Posted by 4./JG53_Task

Can anyone help me with this issue. I can not find a solution after trying everything anywhere.

I just bought/downloaded the game on steam, verified the game cache, THEN unrar'ed the beta patch folder 'parts' into my main CoD root folder and overwrote anything that it asked me to.

Now when I try and start the game, either normally and also tried running it as administrator, the launcher spits out an error saying "Launcher.exe has stopped responding" and the game simply doesn't start.

I followed the instructions exactly, my flight buddies did the same thing with no issues, but I'm having some f'ing bad luck here.

I might be wrong so might want to confirm this. Start by reverting back to a clean install in steam..
Once back there, instead of using winrar, use the program 7-zip or winzip indtead. I think this is a known bug when using the the wrong unziping program. Dont ask me why...

[Rangi]

Task did you start the game once and ran a mission before installing the beta patch? There seems to be some 'things' it needs to do first. i had launcher crashes until i:
verify game
start clod and start a mission
delete cache
unpack beta patch (i also had a corrupted file at one stage when downloading from airwarfare)
good to go.
hope this helps

[JG26_EZ]

Originally Posted by Anders_And

Once back there, instead of using winrar, use the program 7-zip or winzip indtead. I think this is a known bug when using the the wrong unziping program. Dont ask me why...

The above advice is wrong from what I have heard. Should be the other way around.. Don't use winzip