Axis checked and re-adjusted, thanks for the tip.

However throttle response is still very twitchy. It's tolerable with some a/c, but too twitchy on others, particularly Spit II.

Also my rudder control sensitivity is now set at 10% but still too twitchy (spikey is probably a better term).

G940 HOTAS here.

The whole 110 cockpit looks like that.

Hi Fruitbat,
Maybe check your settings- I am not experiencing the cockpit degradation at all. Could it be something in your options, either in-game or Nvidia?

does not you have blurry textures in 90 FOV ?

I've been experiencing 110 texture problem. When I start up, its ok. Then I switch to external view, and after few switches they will not load properly and look like... well like others have posted. Then few switches to external, and they are back to normal.

The problem is that the texture cache don't draw correctly the textures, its in the know issues list :

Would be interesting if we can expose a pattern, but the reports are useless without your hardware configuration, as video card and his memory capacity.

I have this issue, everything at default in ATI panel and everything on high in-game, also textures in "Original".

All settings are identical.

Game crashed after 10 minutes



AMD Phenom(tm) II X4 965 Processor 7.4 5.9
Determined by lowest subscore

Memory (RAM) 8.00 GB 7.5
Graphics NVIDIA GeForce GTX 560 7.7
Gaming graphics 4096 MB Total available graphics memory 7.7
Primary hard disk 696GB Free (931GB Total) 5.9
Windows 7 Professional

System
--------------------------------------------------------------------------------

Manufacturer Gigabyte Technology Co., Ltd.
Model GA-MA790XT-UD4P
Total amount of system memory 8.00 GB RAM
System type 64-bit operating system
Number of processor cores 4

Storage
--------------------------------------------------------------------------------

Total size of hard disk(s) 1863 GB
Disk partition (C:) 696 GB Free (931 GB Total)
Media drive (D:) CD/DVD
Disk partition (F:) 70 MB Free (100 MB Total)
Disk partition (G:) 761 GB Free (932 GB Total)

Graphics
--------------------------------------------------------------------------------

Display adapter type NVIDIA GeForce GTX 560
Total available graphics memory 4096 MB
Dedicated graphics memory 1024 MB
Dedicated system memory 0 MB
Shared system memory 3072 MB
Display adapter driver version 8.17.13.124
Primary monitor resolution 1920x1080
DirectX version DirectX 10

What settings did you use? Because the first thing i did, was checking throttle mapping to see, if anything was screwed up. I even reassigned throttle axis, the problem is still there. Checked input vs output, which is the same as before the patch.

yeah i think its the new "flight model" which makes it harder to give accurate inputs on rudder,aileron and elevators...regarding the throttle, i didnt notice a difference, but then im a 109 driver as you know Urizen:grin:

I've tested the Spit IIa on ATAG, I must say that the throttle bug is quite annoying.

I spoke to soon in regards to the patch being Ok for me..

I CTD 3 times in 90mins yesterday on ATAG...Logs sent

Ive got settings on High and grass trees etc all on so might have to do some experimenting

Here you go Uri.

messed up windshield after crash land; new look of the rear view mirror turned off, after taking shots..

maybe nothing new, just adding to the mess up on Spit IIa after taking damage

http://img687.imageshack.us/img687/2...oroff20120.jpg

lol the take off could do with a Benny Hill comedy tune; as good as i am getting airborne with the 109, with the same problem it would be more like The League of Gentleman

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

Aircraft twisting around after landing.

Repeatable bug. Aircraft move around there own axis after shutdown. Not wind affected.

Thanks Dutch, though i fear, that it won´t help me, as my settings are already very near yours. but testing them anyway.

CTD all the time, no performance change at all, it even seems like the FPS has gone down. But I am sure you've all heard about this...:mad::mad::mad::mad::mad:

^S^

Here are my "bugs"

System

Win 7 ultimate 64 bit (fresh install)
I7 2700k
16 GB ram
Nvidia 270 gtx (driver 296.10)


1. Red square at startup (as posted before)
2. Low res instruments (as posted before)
3. The "Launcher stopped working) after about 5-20 min ( every time i play single or multiplayer)
4. Lots of "micro stutter" (mostly in multiplayer)
5. Still cant get AA to work

Fps is from 30 - 60

problems
 

red dot at the launch screen,
and when I tried to play, I heard the engine throttle up and down on command and so, but I have a black screen or the splashscreen of my pc, but i can't see the airplane :(


fps: can't now for sure now due to black screen :p

same here F-ing frustrating ive always supported the IL-2 brand but this is making me feel so annoyed that i feel like leaving. I just wanted to play, fps isnt that important to me i have 4 amd 7950s in XFire on my main rig but only a GTS 450 on the one im using atm, i was just comparing the patches but no it doesnt want to play ball

Hey KK get yourself a new videocard, it will make wonders for CLOD!! I just got a cheap second hand gtx580, upgraded from gtx280, and the game went sooooooo smooth! well that was before the last alpha patch....

I just tested on ATAG. Findings:

1. With all maxed out - except for SSAO , and VSync on, I reduced the stutter and increased FPS.
2. I tried a turn fight with a Spit IIa, on my E-4, and the Spit outturned me in less than two turns. As it must be. Augh.
3. The sound radar is gone for Spit behind a 109.
4. The sound radar is still there for a 109 approaching a Spit with open canopy, but less noisy than before

That's all folks ... ah, no CTDs for an hour.

Cheers!

got rid of my launcher crash
 

i noticed in my event viewer that the launcher crash was something to do with .net framework and this was written in my log file:

System.NullReferenceException: Object reference not set to an instance of an object.

plus a load of numbers and lettersafther this. i got one of these after each crash.

i looked up the meaning of this and from what i understood this error is when the code tries to use a setting that is set to 0 or "null" and cant handle it. so i decided to turn all of the video options in graphics settings on. just flew my first sortie that lasted over 20 mins (ran outa ammo with vulchers at manston). and second that was 40 mins, would have lasted longer but 109 got me over france. i have no idea if the log file error was to do with the graphics settings lol!

the settings i had to change were:

SSAO to ON
V Sync to ON
Grass to ON
shadows to ON

I have left anti aliasing off but all other settings are on (at least on low for each, some medium, but the above were the only ones i changed as they were off entirely)

my fps took a bit of a hit but its playable.

i think there is a problem with not having one of the above not turned on, at least for me. i will test each one tomorrow to see which was causing the problem for me.

I have atleast 2 of those turned off, but if it works for you it works for you :)

Brilliant finding macro! Setting VSync to ON eliminated stutter for me (0.5-1 s freezes), and I didn't have CTDs for an hour or more. All the other options were on already, except for SSAO which I disabled for the test.


http://img.photobucket.com/albums/v2...ideoCloD-1.jpg

Cheers!

^S^

Im looking at the Nvidia 570 gtx :grin:

i just played with ssao off so dont think its that

Intersting Macro. I play with grass and roads off and am having CTD's with the new patch, with the same 'NullReferenceException: Object reference not set to an instance of an object.' error in the logfile.

I wonder if people that have messed with their config files are having more issues than those that havent, if you move the config files out will the game recreate them? Wonder if its something to try??

Same here!

What I don't fully understand is why I don't get CTD on another full real server such as 'Kampverband' but constant CTD within minutes on ATAG using the same settings?

How does your ping compare on those 2 servers?

Go to video options and set the full screen option to "pseudo" then play.

Afterwards you can put full screen back to "on"

124 on ATAG around 65 on Kampverband but......just had a CTD on Kampver within 10 minutes but flew for am hour or so earlier with no probs. Ah well, keep plugging away.....in SP (at least that works!) :grin:

Could be to do with the amount of players on each as well, how did that compare? I've never had them, one of the lucky few I guess, and on two very different machines as well. Doesn't make sense.
No bugs to report that haven't been reported by many others already, but the most annoying one for me is the throttle/boost situation in the spit IIa. Feels to me like some horrible compromise they've made to make the spit match their idea of what the FM should be.

An ATAG gentleman explained me today that this behavior of the Spitfire IIa throttle is historical, below 30-40% the throttle was erratic.

Cheers!

Interesting, ive never heard that before. where did he get his info from?

Whoever he is.....HE LIES!!!!! HE LIES!!!!! LOL

(Actually, I have no idea. I'm just trying to figure which one of us is a "gentleman"! ;) )

It's also a possibility of scripts causing a CTD? I haven't had a CTD in months, but after installing the Wicks vs Dundas campaign, I got ctd'd twice on the RTB from the first mission. No settings changed, but there are a ton of scripts I haven't used in those missions.

Well it's not me for sure. I call a spade a bloody shovel. Can't think which 'ATAG Gent' that could be............? :confused:

He said he spoke with other ATAG guys. Additionally he said that in 1946 the Spit IIa behaved the same. Honestly I didn't remember that.

He was ATAG fermen or fastmen or farmen or something like that.

Cheers!

Its just hard to imagine the RR engine behaving like that, plus ive read most books on the BOB and most of the books by the pilots that flew in the battle and ive never heard that before. Not saying the guy is not telling the truth but im sure i would of come across that info on the spit2.

I agree. Funny because he was flying red ;-)

There's a Spit IIa in 1946? I don't remember that.

Real easy test for the throttle comparing to 46: Take a spitty up in 46 and overheat it. Notice how much throttle you have to let off before A.) it cools down and B.) the RPMs move. From memory (haven't played 46 in well over a year) the last 30% of the throttle in 46 moved RPMs a measly 10rpms, don't remember boost though. That's exactly how IL2CODs spittys act now. The lower end of the throttle I don't know/remember. But the upper end never worked the same way as the old game. To me, again from memory, it does. From memory, all the variants (early and late) acted the same way in 46. I'm not saying it's correct. I've never flown in a spitfire. But it acts like the old game to me now.

There is in UltraPack, but not 4.11 vanilla.

There is a problem with the CSP Spits, particularly when landing - you can haul throttle right back, RPM falls but Airspeed correction (and engine sound) seems unresponsive and incorrect to me. I am having to make a much longer approach using Prop Pitch to kill speed as well as throttle, flaps, etc. Its an initial impression as I have spent most of my time trying to get my patch to work in MP rather than focus on FM. Also interesting that a lot of comments have been made about the Spits ability to turn tight with the current FM and possibly related to this lack of throttle control.

EDIT. Throttle is like a two position ON - OFF Switch - RPM drops and thats about it! A digital Merlin Engine....

FPS (Frames per second) are worse with this patch.

I do not get as many launcher crashes, "Launcher.exe has stopped working", but I often get 1-2 FPS when I would normally get the launcher crash in the previous version.

I can not explain when I get low FPS in multiplayer because it completely random. The game is unplayable.

I also get many launcher crashes in the FMB, multiplayer, and game menus.

The FMB also has a visual bug where text overlaps. (When there is a drop down menu, the text overlaps with all of the menus below)

Windows 7
Nvidia GTX 480
Intel I7
8gb DDR3

Tested yesterday over 2 hours and no CTD (ATAG server). But I got Launcher has stopped -error after I closed the game. Have to test more today.

Can't remember the source, but I'm sure I read that at idle the Merlins were a snarling angry beast.

I guess like any engine with a high overlap cam, they need high revs to breath properly.

Near Calais in free flight...

http://img140.imageshack.us/img140/971/landerror.jpg
By furbs9999 at 2012-05-08

All twins cannot take off on the Quick mission set in England with the picture of the Blenheim. They just won't power up enough to take off. Can someone else test in case in doing something wrong?

My realism settings were complex engine on but temp conditions off.

Was it fastfed?

Sent from my SCH-R910 using Tapatalk 2

Its porked.

"Off you go laddie, finest aircraft in the world. Just one thing, the throttle's a bit of a bugger, only controls the boost over about 0.1% to 40% of its movement and you can't get her down to idle, but you can cope with that can't you? Eh? Rolls Royce? Nothing to do with them its just the way Supermarine designed the throttle installation. We've asked them for an upgrade but everyone's working on Seafires now. Current spitties won't be changed."

Thank you Klem, post of the week!

From my understanding the early Merlin engines had 43 degrees of valve overlap. This the period of the rotation of the camshaft at the end of the exhaust stroke and at the beginning of the induction stroke when both the inlet and outlet valves of the combustion chamber are open. It allows the cylnder to fill as completely full of fuel air mix as possible before the combustion cycle continues.

This allows the engine to produce more power at high RPM. Unfortunately the flip side of the equation is that she idles like a dog and run rough at low speeds.

Later Merlins like the 70 series, had overlaps increased to about 70 degrees. They will really run rough at low revs.

I experienced a bug in the 109 (other planes not tested yet)
If I want to land my plane, lowering my gears and lowering my flaps I cant change my throttle anymore. The current set throttle position stays hard as a rock till I pull the flaps back in. This is one pretty deadly bug!

But maybe this is ja specific G940 problem? :confused:

EDIT: Sorry I had antropomorphic controls switched on which would explain why I cant change throttle due to the large amount of time lowering the flaps in a 109 need! Bug is most commonly a feature ;)

You sure you havent got that setting enabled?..cant remember what its called, some BS setting where you cant do 2/3 things at once

Anthropomorphic controls.

NullReference Exceptions
 

Sorry for sounding 'Techy', but I call myself a 'software engineer', and I too have had CTDs with this given as a reason. Either the report is incorrect (which doesn't make it very helpful for debugging), or it's true. If true, then something is very, very seriously wrong with the initialisation code of objects, because this should NEVER be seen. There are 2 levels of object initialisation - at start-up e.g. objects within the cockpit, and the more demanding level - dynamically i.e. in-flight. I wonder if the dynamic initialisation is falling behind, out of sequence when the method on the object is called? To me, this sounds like a basic threading error; probably difficult to reproduce, but a closer look in the code design/architecture at anything that affects the completion of the initialisation thread seems to be in order. I would have thought that test code could readily be instrumented to log when an object's method is called before the initialisation is complete? It certainly suggests to me that 'defensive' programming isn't being used............


Marx

My menus are pretty sluggish now. Takes a long time to load, to refresh the server list, that sort of thing.

A bigger bug that I've noticed is that the Blenheim's mixture controls are the wrong way around. 0% gives best power at sea level, and at altitude 100% seems to work better than 0%.

Really only this?
 

Well.......

What can i say....
I can´t tell you how the game runs on my PC....
What I can say is that I don´t have CTD anymore.
Of course, this might be cause the game does not launch at all. If i don´t enter the game, i can´t be sent to the desktop as i never left it.
Really, a good solution to the problem. How didn´t I realiced before?

Keep up the good work.

Perhaps in a few years we can play a red baron like game on our flamant new PC.
:confused:

Just had my first ever offline crash in a quick battle.

Log sent.

Just checked through my ccpcrash folder and i have 2000 files, 537mb!

You think Luthier wants the whole lot? :)

Maybe i should zip them up and mail the lot.

Engine failure bug?
 

I just had a strange bug in Spit2a on ATAG patch server, took off Manston flew south and climbed to 12,000 feet, everything good, watched temps & rpm all the way, then the engine failure effect kicked in - but with no damage as I have my engine info window display damage. rpms and temps were still good, gear/flaps were up, (unless my cockpit indicators were faulty as there is no external view) but the screen is shaking madly and horrible grinding metal noise. Tried cycling mixture, no effect - slightly lower rpms on lean. I recorded a short track to review, but guess what? in the track there was no shaking, no grinding metal, and steady(ish) needles for rpm/temps. mind you the track record is still not getting the engine right so I don't know.

Anyone else had this one? I think that's twice for me, the first time I thought I'd cooked the engine but now I'm pretty sure this is a bug.

Regards, Sam.

Yes!

I experienced this a couple of days ago on ATAG. Spit IIa, departed Ramsgate, headed south up to 12,000 just like you (to rendezvous with some Blenheims). Engine conked out for no apparent reason and I had to divert to Hawkinge (whereupon I borked the landing).

I was sure I'd done nothing wrong in terms of engine management, so your report kind of supports that.

The Merlin engine does fail in CoD if you maintain max boost and max revs for long enough and probably also if they are higher than recommended. I think its the Constant Speed unit that fails and that doesn't involve excessive engine temps. I don't know that its accurately modelled but its happened to me several time when I've been pushing too hard for too long.

OK, thank you. does this not register in the damage window though? governor failure or something? I held 3000 rpm for climb, and found that after I could still fly effectively, no loss of power, rpm control etc working fine just with the screen+needles shaking it was unplayable. I don't use the boost, as the throttle in spit 2a maxes out the manifold pressure at about 40% throttle currently, and the push lever stays where it starts locking max throttle at 100%

Also, no failure in the replay - but then replays are not working properly.

Is it just me being a newb then? what is the correct protocol for quick climb and boost control on the Spit2a? I've heard folks talking about the boost, but for me there is no difference between 40%-110% throttle other than manifold pressure going through the roof as far as I can tell, no extra rpms, no extra speed etc... :confused:

Regards, Sam.

I don't use the damage window but I just had a failure of a SpitII engine, it simply failed. I was down to 5 gallons and running low rpm/boost to stretch it out. After a while it begamn to misfire under low fuel pressure, causing intermittent vibration and eventually it stopped and wouldn't restart.

I don't know if this is what heppened to you? Failed fuel pressure?

The throttle currently controls boost levels over about 0-40% ov its range which is obviously a bug. I can get boost pressures between -4 and +6 but its hard to get exactly what I want and have to settle for about +/- 1lb.

Here are the boost figures from SpitIIa pilots notes for the Merlin XII and the Hurricane Merlin III (Spitfire will be the same). You'll find these splattered all over the forums.

i think you're on to something! from the moment i enabled SSAO and VSync i had no more crashes! been having them all time, never reaching the 30min mark. this should be shared with everyone, just in case :grin:
_______________

Q6600 2.4GHz oc 3.3GHz / GTX 570 1280MB (Gainward) / Asus P5K-E / 8GB DDR2 800 / Corsair 850W
Windows 7 64bit / nvidia Driver: 296.10

but that's a report with 100 Octane there not using that in this version. 97oct is what I was told there using.

I applied the patch and tried to start the game, ctd every time. The little gunsight comes on my screen but it doesn't go any further. I am not sure what the path is to the crash log file, but I did turn them on in my config.

Is anyone else getting text overlaying text in the FMB? Like when you go to Object Browser, the text overwrites itself, making it hard to read?

I can confirm the same thing in the 109, I let the RPM get too high for too long, and no damage messages, but definitely ruined my engine.

Its 87 Octane we're using and the SpitIIa figures have the 87 octane boost numbers in brackets. At the time it would have been possible to have either 87 or 100 octane although 100 octane was the fuel used during the BoB. We should get that eventually otherwise its not 'The BoB' but don't restart that discusion here, its been done to death in other threads and its in the Bugtracker now.

Hi - did you extract files with WinRar or 7zip? If you use Winzip straight it won't extract all the files.

OK, I guess the bug is - damage occurring but not registering on the damage output window.

Regards, Sam.

You might want to check your conf.ini. In the [Window] section there is a value that needs to read Render=D3D10_0 if it does not the patch will not work and it means you are using DirectX9 NOT DirectX10. The patch is only compatible with Dx10. I had the same problem as you and this fixed it. It caused another problem but at least I can play single player now without crashes.

I have a general decrease in performance with many more stutters than before the patch.

No Anti Aliasing
No clouds
Grass in Hangers
Mirror only displayed a frame in the air but when I land, it works.
Saitek Pedals brake axis was recognized in the setup menu, but didn't work in game (Saitek driver 6.2.2.0)

In the Spitfire on the first familiarization campaing mission in it, the compass heading is 170 degrees out and the artificial horizon was all over the place.

Intel i7 3930K
16GB Quad channel RAM
Gigabyte 7970 Windforce Edition - Catalyst 12.4

I got similar problem with engine broken at + 9lbs in SPit II even during short time of using - 1-2 minutes. I think temperatures was ok - radiator open. I was
surprised by what happened initialy thinking i got hit in engine but it was just engine broken - probably after some dive.

Ive seen messages that the exhaust manifold has failed when running at max boost for too long. I guess thats what they've modelled which the temp gauges dont pick up!

Pedals are usually assigned to Bf109 toebrakes. The Spitfire and Hurricane have a 'handbrake' mapped to a key or other axis although at the moment it is only modelled as on/off instead of 'progressive'. Differential braking is achieved using handbrake plus rudder bias.

The Bf-110 and Bf-109 have a different engine dopplar type effect durning outside view/ flyby view. I believe that you guys Luither Inc. had it correct last patch which everyone I know was very happy with the DB601 engine sound. I ask sincerely to keep that old patch engine sound. I say that bc many people like myself really want a sound really close to the real thing as possible. Now with the nw BETA patch the outside view sound of the DB601 is just not good. It sounds like a motorbike driving by. I am not sure if the sound is still being modified for the next offical patch or not but I think and many many other customers perfer the last patch engine sound. I suggest Luither and developers return the old engine sound and not worry about something that is already perfect and spend time on other bugs or enhancements that need to be fixed or added.

So in short thanks for all your work you guys do but the outside view DB601 engine sound was perfect last patch and many wish it would be returned. Thanks.

S!
Bf110Pilot
109 flybys :P

http://http://www.youtube.com/watch?v=5nj77mJlzrc

I always throttle back and reduce revs in a dive to avoid over-revving the engine. Perhaps they have modelled over-revving and you exceeded the max? See attached. Although The Spitfire Pilots Notes are for the Spitfire I it covers Merlin II and Merlin III engines and the other attachment is the limitations for the Spitfire IIa with Merlin XII. Note what these say about the dive rpm limitations.

Looking in SPit MK II manual there is limiation for 87 Octan fuel ( + 9lb):

- climb ( 30 minutes) - + 9lbs at 2850 RPMs
- all level ( 5 minutes) - + 9 lbs at 3000 RPMs
- max dive (20 second limit) - + 9lbs at 3600 RPMs

I think i dont broke these limitation in my flights when my engine was a few times broken.

Also i notice that Spit dont slow on landing after touch down - it seemed like bug.

Strange for me is also rudder responsive expecially in 109 - i fly planes and gliders but it seemed that it is too high roll interia during rudder operation

Other thing are slats in 109 which open too late - at too low speed and too high angle of attack.

I think there are a few FM problems which should be noted and fixed.

One thing I noticed is that there are important differences between online and ofline flight when it comes to CTD.

I bought DESASTERSOFT adons, which is really good and well made. But when I have flown in ofline mode for about 30 minutes I get CTD. The same applies to the Quick mission. When I fly online (ATAG), I can fly for hours without it. Odd but nonetheless an event worth noting.

Anyone els have the same issus?

Ok, beta patch test notices. The Good, the Bad and the Ugly.

The Good:
New FM, more dynamic, demands more pilot input. After a learning curve I start to like it. Good elevator trim is even more important with this new FM. Tested 109, 110, spit, hurri and fiat G50.
Direct X10 makes game look better, silhouette of aircraft look better, could see marking on a/c from far distance. Tracers and bombs look better. Saw pilot bail out from far, small dot in fact but could see arms and legs!
New sound, heard new sound of a/c hits, you can hear the sound of your chute. New sound for Fiat G50 and Stuka.
Finally contact possible with home base, vector to home base used it a lot already.
Game is running smoother, especially when flying low.
AI is better now they seem to bleed energy close to player flown A/C. That is great improvement.

The Bad:
Lot of CTD, only had few before, already discussed a lot.
Game freezes when I do refly for mission.

The Ugly:
Yes you already guesed; the blurred panels, assume this will be fixed in the final patch. I really got used to these fine looking cockpits.

Bug in realism settings.

Disabling 'Wind and Turbulence' and 'Headshake' stops 'clouds' rendering even though enabled.

Unchecking 'Wind and turbulence' on its own does not affect 'clouds' rendering and is correct.

Wierd bug in the Bf109, when your engine stops fuctioning the RPM guage does not registar even though it is spinning. Also on these occasions there is no oil on windscreen and no obvious sign of damge. No loss in fuel or oil pressure. No loss of fuel... Everything is normal except the engine is off and no RPM... ATA still registers... :confused:

Well I finally downloaded the Beta/Alpha patch. I also changed the video file as suggested. Wow what a difference. A huge improvement in Frame Rate. It's heaps easier looking around using my TrackIR. There were a few issues though.
There seems to be an issue with the Spitty and Hurri. The Spitty's throttle seems weird and I cooked the engine continously. The same with the Hurri. It just didn't feel right and the engine suddenly stopped even though it wasn't over heating.
In multiplayer I didn't get and CTD. In single player though the screen froze. It didn't CTD but stayed frozen.
Besides those, which is probably significant, it was a real pleasure to fly. I only had clouds turned off as well.

Huge slow downs for explosions and smoke, specially when they happen close to you.

I see people talking about issues with clouds, but because they stated issues with clouds I have them turned off, doesnt it make sense that testing without clouds should be what we are doing right now? Goes with grass as well as both have issues?

I have this bug in the 109: low resolution Revi.

game crashes or has huge freezes when enemy aircraft is around

Hi guys!

I have a problem with the new beta patch. When I installed the game, I try it, it runs. Then, I unzip into CloD folder the beta patch. Now, here is my problem. First start I got blue death because display driver. Then I tried again, Fraps OFF, and while I started the game, I got this message.

"Driver not responding but has recovered.

The NVIDIA Windows Kernel Moder Driver Version 301.24 display driver not responding but has recovered."

When I want to fly and I don't saw the map and my plane before start, and then I press fly button, I hear the game and it runs, but I don't see the picture.

Some pics:
1
2


Can somebody help me?

~S~ Mijki

EDIT: I downloaded and installed 296.10 driver...but same problem. And my DirectX is the newest. I have GeForce Gt240 card.

This error message is from the display driver crashing. It is the drivers of your video card, not the game. I notice you said you had driver version .01.24 then installed 296.10 (an older version) over the top, which is likely to cause problems. My advice would be to download the newest version of drivers, uninstall the old ones, then install the newest. Otherwise you might get conflicts between installed versions. Try again after cleaning up the drivers and see if the game runs.

I unistalled 301.24 and restarted the computer before I installed 296.10.

Oh ok. I found the 296.10 drivers gave me lots of driver crashes and installed the newest beta drivers (the ones that brought in FXAA) and haven't had a crash since but I think those were the 301.24 version.

Still huge FPS drop over land when you use max ZOOM IN ( gunsight view).

Other hand i still dont get why they cant make smooth ZOOM like it is in other sims from years???

I got sometimes graphic bug in CLoD that after some time of playing my screen is divided on half or something. Game still work not crash. When i back to windows screen i got still the same bug and i need to restart my system.

I never had these with other game or soft.

I got ATI 6870 cat 12.1, Win7 64 bit.

crash luancher stop responding Mini Fix
 

71st AH Squadron we all crashed at the same time with heavey action over Dover 9,000ft.

On ATAG beta patch server.

Sent ily a report on his email
Ill report here just incase his email is still full