Hi Snapper! With the G.50 I didn't have a CTD, unfortunately I stalled in a tight turn trying to turn tables on a pesky Hurricane and landed on the water. I am a beginner on that plane. Did you see me warping?

Cheers!

Oh good to know, thank you Bliss!

Ah, must've been the stall I saw -- it was only for a split second that I saw you before splashing in -- and mistook it for CTD/warping.

Planes disappearing, 109 spin recovery, wing surface textures
 

Confirmed planes disappearing at medium ranges.
I thought it was my imagination but I found it real hard to track planes from distant to close. Tonight I watched a plane completely disappear at about 3-4km and reappear at 1.5-2km. I had him backgrounded against the sky and approached at an angle so it didn't have anything to do with AA. Edit: It was a Spitfire that disappeared...looks like this may be a spit only feature.

Also, What is with the 109 flat spin. Almost impossible to recover now.

Still can't get original textures on my 109. I hate looking at these wings that look like they were painted by Cezanne.

wrong!
i had this for the first time after the alpha patch, before the hotfix.i was already crossing the channel started from france, climbed to 4000meters, and when i reached dover, my game suddenly disappeared mid air, and i was left in the air.i couldnt look around anymore,like some kind of static camera.but this happend 15minutes after take off.

i noticed the same thing happening as well, if your plane gets damaged, or if you are going to bail out.then the pit will suddenly go into a really low textures image...

Yeah it was some 10 min after T/O.

Nope afraid your wrong, I have had this as well and bliss is correct I had flown quite far and it suddenly did what you have mentioned but I did see it come up saying I had just landed, only experienced it once but you can fly quite far before the server despawns your aircraft.

:o only since today, the server list is showing again

ok i didnt notice that message, but i only wanted to state, that it doesnt necessarily have to happen directly after take off....for me it was 10 to 15minutes after that.
did you guys notice this before the beta patch as well?for me it happened only once, and it was the day of the beta release.

I have had it only once and a few months back.

You can now use emergency power and partial flaps.

With the patch i can easily take off in the previously impossible cross country quick mission...with 100% fuel and a full bomb load :cool:

How to:

Mixture auto rich (levers full back) and prop pitch fine for high RPM (levers full forward)

Start engines on outboard tanks and get them to about 130 degrees cylinder temps and 50-60 degrees oil temps. They warm up much faster now so pay attention if you are used to warming them up with closed cowl flaps. You also spawn with the parking brakes on, so you can run them up a bit. At this point you can throttle them up enough to taxi to runway.

Once aligned with the runway, open your radiators fully and come to a stop. Calibrate your compass, center your rudder trim (it still spawns with starboard trim dialed in) and set your flaps to 20 degrees.

To set flaps: we now have flaps up, flaps down and flaps neutral, this governs the flap motors. So, press flaps down until the motor is set to lower them, then once you hit 20 degrees press flaps up to bring it back to neutral and keep them there.


For take-off: Engage boost cut out. Smoothly advance throttles to maximum. If your cylinder temps are below 150 you might get a big of sputtering from the engines, so you could check and momentarily close your cowl flaps before takeoff to bring it back up.

Roll out, lift off at about 70 mph and retract gear as soon as you have a positive rate of climb. Keep climbing at full emergency boost, just watch your cylinder temps (mine hover around 230 during this part) and don't climb too steep. Steep = slow = no airflow = overheating.

Climb to 500ft or so above ground and let your nose drop to level flight in order to speed up and increase airflow over the engines.
At this point you can configure for cruise/climb and save your engines from further heating. Retract flaps, pull prop pitch back to coarse, throttle back to +3 and disable boost cut out. Switch to inboard tanks.

You will lose a bit of altitude during this last part, but once you get to 140 mph it flies and climbs beautifully on coarse pitch all day long (i only use fine pitch for take-off, approach and landing).
Just monitor your temps during the flight and you'll be fine. It's much more forgiving now and you need less open cowl flaps once you are moving at a good pace.

Agree on that one. I think what would fix all issues would be a slider that lets the user decide wich drawdistance of planes he wants. Currently the planes still get rendered as dots when pretty close and their silhouette is already good to see when zoomed in.
I think there should be a bigger drawdistance and no dots at all. I know dots are good for the performance wut they hugely take from game immersion and playability.

Winger

Dammit Blackdog now my fingers are itching to get back in the old dog, hopefully all aircraft will be a pain/so much fun to fly!

Nice post Blackdog....just what I've been looking for, a quick Bleneim fly guide. Wish we had a thread for such posts, a simple "How to fly a ---- in 10 basic steps". I think such posts could help get people off the ground so that they can learn to better fly a ---- overtime.

Problem is such a thread would soon get polluted with everyone's opinions on how to fly a ---- such that the simple goal of helping people try other planes would get lost in a bucket of bile :(

Oh well....thanks for the post though!

Bravo dude nice post It'd be great if you could see your way to a sticky for it

Any news today BlackSix?

The disappearing ac/LOD's is worse with this mini fix.

Had my first Screen Freeze and Launcher crash on ATAG about 30 min after joining. Files sent.

Stutters and huge FPS jumps over certain areas of the map (even at 18k) are also back. Locking Vsync to 30fps seems to have cured that problem.

Will do.

Done ;)

Re: Low Rez Cockpits/Skins
 

I've noticed while flying the He-111 and Stuka that some cockpit textures as well as external skin textures are low resolution when below 1000m, when you exceed 1000m of elevation the high resolution textures kick in.

Last night I did a dive bomb attack with a Stuka and noticed the low resolution textures had come back when I pulled out of my dive.

You know you wanna... :-P

The only reason i'm not flying the Blenheim more is that i'm making up for lost time with the Ju88. Previously my CPU would occasionally overheat and force a full PC reboot, but with the 88 it happened each and every time. Now that the new patch gives slightly lower CPU loads my temps are nice and cool and i can fly the 88, so i'm focusing on that one for a while. :cool:

I've had low-res textures since forever, not just with the latest alpha patches. I think it's a combination of the way textures get loaded, as well as available video RAM (and maybe plain RAM as well).

What you are describing to me sounds similar. Not enough memory to load everything at the detail settings you choose, but as soon as you climb a bit and the ground LOD transition kicks into effect some resources are freed to load up your cockpit textures. As soon as you dive below that altitude the ground loads again at increased detail, it's out of resources again and the cockpit textures drop in detail to compensate.

HI all i fly few hours on ATAG and is better but DEVS pls is so hard to fix BF-109 landing gear open bug its really shame when u fight whit 109 and u see so he have gear landing open at 5000ft

There are many others:

- DM bugs - glycol leak casue no damage, sometimes 109 blow up (visual effect) and still normaly flying - probalby many others + visual bugs after damage plane in cocpit

- very low FPS at maximum zoom over land during online dogfight with other planes

- still there are occasionaly CTDs

- FM and performacne bugs - there are a lot of them ( wrong maximum engine settings, wrong performacne, wrong working slats, hard spins in 109s, strange controls responsive expecially rudder etc.)

Do you mean the water radiator for glycol leak? THe damage effect is not immediate, and usually sets in 5-20 mins depending on damage.

About the explosions. They are from fuel tanks. If only one fuel tank 'exploded', there may be another un-punctured one to keep the plane flying.

I have no idea why 109 light up so easily though...

This still exists, happens when aircraft takes hits and canopy becomes dirty by smoke, low resolution and extra stick.

http://i8.photobucket.com/albums/a23...5-14_00001.jpg

Another thing is the com from ground control RAF he says bearing ninety instead of zero-nine-zero which is better to understand.

Yes, there seems to be something similar going on here:

http://i739.photobucket.com/albums/x...3-20-01-85.png

As soon as the wing fell off:

• the damage textures appeared as low quality
  
• The crosshair became visible outside of the reticle
  
• The mirror morphed into the one from the external view.

If there's a firey explosion underneath and inside your aircraft (the fuel is probably not politely waiting until it is all outside of your fuel tank before igniting and expanding rapidly), then I think you're going to have more problems than zoom climbing and then killing the RAF plane that shot you.

If that's not what this is, then seriously make that explosion graphic smaller because nothing should keep flying just fine after the thing that we see right now.

Is anyone else not getting smoke from aircraft at all after the fix? I swear they made it impossible to light engines on fire, or maybe they are, and the smoke isn't rendering at all?

For the Spit IIa I noticed when my elevator controls got damaged and was unable to use them i could still use the trim to control them. Im not 100% if this is a bug or if in real life they had separate control rods for the trim?

Havnt tested this for any other controls or planes yet.

That would seem entirely possible. Though not Spitfire I know of at least one occasion when an RAAF Winjeel lost its primary elevator cables. A tailslide gone wrong ended up shearing elevator cables.

The aircraft was recovered on trim control alone.

anyone having landing issues the plane will not stop, it's as if the grass is ice?

I'm landing at 90 to 70 mph and still sliding off the runway its like the breaks don't even work now.

Hawkinge airfield, Manston, Ramsgate.

Agree there Mastiff. Maybe 20% brakes left on her.. Low landing speed now..
Altso I always get fuel "troubble" when 5% left. Less usable now..

~s~

Mastiff,

+1.

I am now in the habit of cutting off my fuel as soon as the wheels hit ground, it's the only way I can stop...

~Deacon

According to spitfire Performance site the landing run with brakes should be about 265 yards (from touch down?) or 335 odd yards from the 50' screen.

http://www.spitfireperformance.com/n3171.html

What we need to test is a runway with regularly spaced objects as markers.

May be a Friction issue. On spawning aircraft weathervanes into wind even with light winds implying little or no friction.

In addition to weak breaks the nose tipping tendency is way to much which doesn't really help as you cant get the brakes on aggressively enough as it is.

LOL I think you mean 'rolling resistance', Ivan. I wondered why some of my spawn experiences have the plane slowly yawing to one side - probably not modelled yet; hence the long roll-out after landing?

I think your latter comment is a contradiction though; it is the braking torque that is tipping up the plane! Probably also a pilot error; best not to apply the brakes unless you have all 3 points on the ground? I always end up on my back too!

;-)

Marx

The aircraft do seem to float a fair bit, but get the speed down to where it should be like around 70mph and it feels ok to me.

The rev counters on the Blen are still fuzzy though. :(

I only hopped in a Blenheim once or twice before the recent patching, but yeah - everything in that cockpit still feels a little blurrier than I remember.

On a plus note I managed to take out the JU88s at Oye-Plage myself last night!

same problem
 

I also have same problem so its not gonna be an ATI issue..

____________
Intel Q9650@3,6GHz water cooled, 8GB DDR3 1600MHz, Asus Striker II Extreme MB, BFG GTX280OC2 1GB, Win7 Ultimate x64

Have you tried setting textures to Original? I havent flown that plane recently, but I have noticed anything below Original seems to make the cockpits blurry...

Yeah, I have my textures on Original. I just don't think they put as much work into the Blenny textures. Or maybe the did and there's a bug preventing them from showing.

It'd be nice to have a little more freedom of movement for your view in the Blenheim in the pilot and bombadier positions via Track IR. It feels like the movement box is fairly small. Especially in the bombadier spot.

I think its a bug, I'm sure the rev counter used to be higher texture.

I agree with the second part, even using the mouse to lean/slide around the cockpit there's hardly any room, I can barely see the behind the seat controls (mapped to joystick so doesn't matter too much). Also not much room to look behind for enemies or friendlies. I'd like to be able to turn my head and look at the airspeed/altitude indicators in bombadier seat when looking through sight too as I dont seem to be able to click all the buttons when zoomed out. Might be better to put that on the keyboard too I suppose.

Blenheim Tacho "fuzziness" seems to vary for me. Sometimes its nice and sharp then it develops a slight blurr... 5 mins later its sharp again.

Found an interesting bug tonight.

While flying a HE-111 with ATAG_Doc in the bombsight position, everytime he made adjustments to the bombsight controls (increase bombsight altitude, series length, etc) it would cause freezes to me as the pilot. Small adjustments would cause temporary lockups but adjusting the bomb sight altitude from it's starting point up to 6000m was enough to cause a permanent lockup and eventually being dropped from the server causing the plane to nosedive. Once I was out of the server Doc was able to jump into the pilot's seat and take over the plane.

Every time I froze I got red messages in my chat window, like:

asdfsdfjlskdfjsldfkjsldfkj
sdfslkdfjsldfkjsldfkj(Object)
at
adsfjsdfisaslkdfjlasfjsdfl
asdfjsldfkjsfdlskdfj(Object)
===========
=================

I bet they've only designed it to be flown by 1 person, and it's looking for the autopilot instead of a person to be "flying" the plane.

This did not happen before the patch and Mini fix.

Lookaloft, i dont know if you got the game running yet but i finally got mine to start. What made mine work was that i deleted the conf.ini in the 1C SoftClub folder (in "my documents")

Make sure you copy the conf.ini before you delete it, just in case. ;)

Hope it helps.

Hi folks,
and gratulation @BS and Devel-Team. Running quite cool now. Made a Video of me flying in a Spit over a big german city.

http://www.youtube.com/watch?v=I6wQF...ature=youtu.be

Little micro stutters, no problem for me.

BUT then suddenly the screen turns to black and me spitti splattered into the earth.

Greetings
Daniel

Sure you didnt take a FLAK shot to the face, if you are killed in your seat the screen goes black till your plane craters...

Hi,
in fact this happened, i did not hear a boom. Well, if it is a direct hit, I think lights go out instantly.... not being able to hear this "boom". :)

Yes, its hard to hear the boom when your ears are blown out of the cockpit :)

THIS is fascinating. That is exactly the sort of code that comes out of just flailing your fingers on the keyboard like so:

asdflkjasdfkljasdlfkjasdlkfj

Obviously no one actually typed that in during the game. It has to be somewhere in the code.

Placeholder data? Deliberate sabotage!?

Let the conspircy theorism begin!

No, lets not. If its a bug, the devs will hopefully squash it.

Hi Baron
Got the beta patch 17582 working now, thanks to your advice. Deleting the conf.ini in the SoftClub folder as you suggested, did the trick.
Starting the game after extracting the patch till thusfar ended in CTD, although I observed the instructions given on this Forum meticulous. Verifying the integrety of the game cache via Steam; deleting the cache folder in 1C softclub etc. I did it all but evidently this was not sufficient in my case. Now thanks to your addition the patch struck home and I got the red square after starting up the game.
I thank you very much, Baron. You made my day.

Salut!
Lookaloft

I said the error was like that, just random digits and letters. That isn't a copy paste. ;)

Lol, okay.

I'm so used to everyone being super specific about their bug reports now :P

Conspiricists! Stand down!

NP, glad it worked :)

Another finding

Flying 109 get easy in spin and is very hard to recover from spin.
Overdone I would say.

Worse than pre-patch for me
 

Well, I get excruciatingly slow framerates when other aircraft are near.
It's worse than it ever was in that respect. Even after deletion and complete Steam restore + patch + hotfix + cache delete + AMD driver update.

56RAF_phoenix

Q9550 @ stock 2.83 Ghz
5 GB RAM
AMD 6970 2GB (well, a 6950 flashed into a 6970)
SSD

Someone had benefits by deleting the conf.ini in the Documents\1C SoftClub folder. Make a backup copy just in case.

Cheers!

Running gamebooster is definitely causing my game to crash. Without fail.

I have had the full version since I bought IL2 and havent had any issue with it, might be something in your config for Gamebooster.

I'm sure you are correct. I had not experienced issues with it until i updated it a couple of days ago and ran a new configuration, now however if it's running I'll crash within 5 minutes. On the face of it there is nothing in my configuration that should cause that.

All of the above fine and granted.
I can get the game to run with the beta+mini patch, but just for once.
Before each game start I have to redo the above mentioned steps: Delete conf.ini, empty cache. Otherwise I end up with black mission maps, invisible screen after mission start and the like.

Reverted back to official release version eventually since I could not get any improvements from the latest beta patch either.

System specs:
i5-2500K
8GB RAM
Nvidia 550ti GPU

Best regards - Mike

yep, same here. Also with GB my menus get corrupted, turn off GB menus fine and no crash in 5 mins.

Regarding GameBoost, it basically shuts down services and applications running in background. I suggest you to configure manually the list of services, and keep alive the nvidia related ones. Maybe GB is shutting down the nvidia control panel and this messes up the game-specific nvidia settings.

Cheers!

ah just get more ram, your better off. than using those 3rd party priority turn off (resident programs) running dormant. or do what I do right click and turn them off yourself.

I just turned GB off, i prob dont really need it anyway.
I did check what it turned off, no Nvidia stuff.

anything that claims to increase performance is stupid... is for those that have like... 1GB of ram... and don't know how to click start and type msconfig in the search bar.

all they do is clear any excess memory usage... or shut down programs that you're not using... things that anyone can easily do themselves... just by not downloading stuff that claims to increase performance, and by not running programs you're not using while you're playing... by shutting off programs that start when your computer starts, or setting them to not start when your computer does...

Ignorance is bliss. You have no idea what you are talking about.

Gamebooster does more than msconfig can. Not everyone has a dedicated game PC, a lot of us actually use it for more than gaming, where services & background apps are required and these do use up resources not need for gaming.

Gamebooster for me, even on a very well maintained Win7 frees up about 300MB Ram and kills quite a few CPU threads not needed. If you think i'm gonna go through the services maanger and close unnecessary services manually before gaming your nuts.

GB cannot help a poorly setup / configured PC but it does free up resources a hell of a lot easier than any other method i know.

But i'm the same as Furbs.. i dont rely on it.. game runs fine without GB.. turned it off, no drama or issues.

in other words... all it does is shut down programs (the only things that use threads and ram) to free up threads and ram... and services are just programs that run in the background... gamebooster and stuff like those just do some of the work for you that want to be ignorant... about how your machine works, and whats required for it to work and what isn't

guess what I'm saying is... a machine is only so fast... aside from overclocking, no program is gonna speed up your computer, just turn off stuff you can turn off yourself, and in doing so yourself, have 1 less program running because of not having gamebooster or whatever you're using running too :P

new issue for me... when in multiplayer, and i am in my plane, if i hit esc the game will go to the desktop as if i alt tabbed...

Issue fix: Don't hit esc.

i have this problem since the release version of the game...sometimes i need to hit esc 10times before it brings me back to the menu..

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: launcher.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 4d6e3d08
Problem Signature 04: maddox
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4fa4f711
Problem Signature 07: 4aa
Problem Signature 08: 8
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

since installing patch and min patch I get CTD at start up every single time, this didn't happen before installation.

well its very annoying because everytime i finish a flight i have to restart the game...
:-x


edit...
aparrently this issue only occurs at 1024x768 res

Weird because since mini patch I have quit restarting game and I have yet to CTD. Don't even clear cache the next day when I play like I use to.

Did you clear the cache?

yes, i've now re-installed it and the same issue is occurring, so its not the patch, event viewer is saying its something to do with .NET framework...

If it says it's a .NET issue, try reinstalling it. There's a redist folder inside the simulator's installation folder under steam, which includes the redistributable libraries for .NET, directX and something else.

If you want to go all out, try the following.

Revert to the latest official patch (verify local file integrity through Steam).

Clear your cache.

Reinstall the redistributable libraries.

Apply the test patch and hotfix.

Launch the sim and fly a quick mission for a couple of minutes to rebuild the cache.

Restart the sim and fly.

I hope this gets it sorted, cheers ;)

Hi, I did all that, it is still CTD at start, i have had no problems with start up at all in the past..

radman I have similar problem too and have cleared cache, reinstalled game, etc. Checking through other threads I see we are not alone.

This has only happened since I tried to install the new patch I think, certainly for the last year, COD has been fine overall..

could it be a recent Vista update...

Well, i'm lost then.

I only have one more piece of advice to offer in this case, if you haven't already done it: sending 1c information about the bug to correct it themselves.

Going to your "documents\1c softclub\IL2 sturmovik cliffs of dover" folder you should see your conf.ini file. Edit it in a text editor and where it says "LOG=0" set it to "LOG=1". This enables logging of CTDs and will create crash dump files that describe the bug.

In that same folder there's a "cppdump" or "cppcrash" folder (not sure which one, it's either of the two so you'll find it easily). In there you can find your crash dump files. You can email them as attachments to 1c (Luthier's address is on the top of the beta patch thread).

They are going through each single file sent to them and fixing issues as they pop up, so if you haven't emailed them the crash log files it's definitely worth a shot. You not only stand a better chance of getting it to run well on your PC after another patch or two, you also prevent it from happening to others.

I hope you manage to get it sorted (either manually or through a subsequent patch) and get back to flying, cheers ;)

Skins:- in the beta i'm getting upto half of a squadron/staffel failing to display the mission allocated skin, displaying the default skin instead. This also seems to be occurring for enemy groups.
There appears to be a pattern to which planes are affected, with flight 1 being ok, flight 2 all default skins and 3rd flight 2 planes showing correct skin, other 2 showing default skin

This is in offline mode both in single mission and campaign modes with missions that worked perfectly in 1.05.

Possibly related to the reported lack of display of selected skins in plane options- fmb preview seems to work after hiding/ re viewing 3d preview?.


Anyone else seeing this?


For what it's worth, rig specs:- 920@4.0, gtx580 1.5gb, win 7 pro 64 bit, 6gb ram.

Don't think it has any bearing on the patch mate,I have never seen anymore than 4 out of the 12 skins that I have applied to my 'mission editor' Squadron.The rest just show up as Default skins.It's been like this from day one for me.

Of course If anyone out there can fault me,please let me know,if there is an answer to this I would love to know,maybe I'm missing something here.

bug report (just in case somebody at 1c actually reads this and is paying attention)

the new prop spin visual effect is ugly, unrealistic, prevents normal vision (worsened in certain sunlight directions) and gives me a headache (literally) after just a couple of minutes of play.

the only "opinion" on this that matters is from those that have spent time in small prop planes and now what SIMULATING it should look like (no, movies dont count because the camera alters what is captured and then displayed)

visually the new current prop visual effect has a strobe like lighting effect which is very unpleasant to look at, and significantly distracts from how clearly you should be able to look at objects directly in front of you. if anything in a modern game will pose an epilepsy danger for the few whom are prone to it, this one surely will. imho also looks like nothing that i have seen in real life in small prop planes.

from my experience in small prop planes in real life, at high rpm the prop spin should just cause a small mild amount of blurring (at the edge of the prop partic), and and under most conditions be barely visible. instead right now we have this massive strobe like flashing thing in front of us which blurs significantly what you can see, and makes it a very significant distraction. to me it is unpleasant, ugly and visually irritating to look at

in the later versions of the previous il2 series, and in the current DCS p51 for ex, this prop spin visual effect was pretty good, mildly visible but not distracting or unpleasant. imo if ever there was going to be an epilepsy trigger concern in those that are prone to it, this current visual effect would be a perfect candidate

specs: intel i5 @ 3.6 (dual core), 8 gb 1600 ram, ati 5770 (1 gb), win7 64 bit

Just for the sake of completeness, link to the prop thread to get more opinions on the matter: http://forum.1cpublishing.eu/showthread.php?t=32234

I'm still not convinced either way, some people say it's overdone, some say it's actually worse in a real plane.

I don't consider this a bug though. It's a mater of personal taste. Maybe an option to choose between prop representations would be in order.

Its possible that there a bug behind the issue, screenshots :

http://img406.imageshack.us/img406/8209/69462015.jpg
http://img29.imageshack.us/img29/6819/99905735.jpg

is the texture of the prop effect pixelated due to a over scale issue ?

If so that could explain why the effect is overdone ...

I don't know if any of you have witnessed this,but when you use the Hurricane on 'Quick Missions'/Cross Country there are problems that were'nt there before,I'm sure.

Firstly you'll notice the skin on the aircraft does'nt appear until some time into the mission,mine appeared just as I took off,prior to this you have a grey blank of a skin.

Secondly and more importantly,you start off as always in the Cross Country mission on the deck and ready to take off.However there is now a bug where as you enter the mission the engine is allready working and the propeller is going round,well just finishing actually as if you've just switched off.

Unless you immidiatley switch on you're rad,the engine will perforate your water rad........this is with the throttle at it's minimum too:rolleyes:

I'm not sure what'll happen if you choose any other aircraft for this,but this can't be right,and I'm pretty sure it was ok prior to the patch,please tell me if I'm wrong.

I totally re-installed COF after having major problems, (now I think not connected to patch) however, with the new patch and core fix, i get the red triangle on start up, the game is running much slower and then crashes after about 1 minute of gameplay, citing 'core.dll' as the issue...

decided to go back to earlier version, verified files, etc, now core dll issue, and CTD, plan to delete full game and re-install to earlier version.

Yes, exactly the same issue with the Spitfire 1a too.

I have exactly the same problem - oil temp starts on about 85 and the radiator 115. It's pretty frustrating (especially since i've spent ages trying to perfect take off on realistic mode so I can stand a change in the multiplayer world.. Bit of a shame now).

Gonna uninstall and re reinstall with older patch I thinks. Glad somebody else is having this problem anyway!

Or....you can make up your own training flights as I do in FMB,this way I know it'll work.

......I just feel sorry for all the new guys trying to get to grips with this for the first time,it must seem very confusing,and this sort of thing does'nt help at all,I would imagine.

However it has to be said,this is after all an Alpha patch and this sort of thing is the norm in Alpha patches,so let's hope it's addressed in the next upgrade.

With the patch you do not need to warm up the engine, this is maybe the effect the dev team was after but the temp of oil and water is at the high end. To counter this open your radiator at max for 5 minutes during take off and fligth until it is (the oil and water temp) normal again. The most annoying is the power/throttel setting in the Spitfire MK Ia and IIa is wrong and is nearly impossible to use.:evil:

Not happy with this patch a lot if CTD's. Propellor effect is overdone and so are the spins, a little move can bring you in a spin and is very hard to recover. No improvement for me.

the problem with the skin it appears to be to all the flyable arcraft not only the HURRICANE

anyone else having the auto prop pitch not working in the 109e4? Its like it was a few patches ago, have to change to manual, increase, decrease and so on, changing to auto again and its ok.