4.09 - Support & Bug Reporting

[mkubani]

Hello gents,

On behalf of Daidalos Team, I would like to thank you for your support and patience while we have been finalizing 4.09 patch. We hope you will have as much fun playing with it as much we have enjoyed working on it.

Even though we have dedicated several months to internal and external beta-testing, it is possible that we might not have been able to identify all issues. Thus, we would like to ask IL-2 community for a feedback related to 4.09 content only. If you find any suspicious issue/bug, please report it in this thread, ideally backed with some hard evidence (screenshots, tracks, etc.). In order to report only those things that are not known to us, please read the PDF Guide first.

We are committed to look at each of the problems and try to fix it in our future release.

Thank you.

Daidalos Team.

[Zalex]

I can't run patch in Vista 64 OS. Did sombodey run, who have Vista 64 ?

[Brain32]

I have Windows7 x64 and it worked fine...

[Zalex]

Rgr. I'll try to reload from another source.

[KG26_Alpha]

Works fine under

Win7 64
Vista 64

Turn off UAC and run as administrator :)

[HarryKlein]

Hi ! many thanx for the patch Ü

I've just noticed a small issue with the I-16 type 5
the 3D model have no flaps (wich is correct IIRC )
but when you press the flaps key the message "landing flaps" is diplayed

[ivagiglie]

Hi DT, thanks a lot for the 4.09!!!

The SM79 is a masterpiece (cockpit detail is great) and flies beautifully, but there's a texture issue on the bombing sight right brace, see here, it's indicated by the red arrow:
http://i664.photobucket.com/albums/vv4/ivagiglie/IL2_bug/SM79_texture_issue.png

[_1SMV_Gitano]

Hi DT, thanks a lot for the 4.09!!!

The SM79 is a masterpiece (cockpit detail is great) and flies beautifully, but there's a texture issue on the bombing sight right brace, see here, it's indicated by the red arrow:
http://i664.photobucket.com/albums/vv4/ivagiglie/IL2_bug/SM79_texture_issue.png

No, it is correct (but don't ask me why it was done that way... :D)

[Zalex]

I have'd reload, there is OK with Vista 64. Thank you.

[rakinroll]

I think somethings wrong with SM.79's gunner MG modelling. Gunner MG belt looks strange. It looks like bullet belt comes from up invisible belt box.

http://img19.imageshack.us/img19/672/sm79.jpg (http://img19.imageshack.us/i/sm79.jpg/)

[Warhound]

For me the fine and coarse pitch in the SM.79 can't be done manually as stated in the PDF. Tried turning off autopitch like with 190/109, but it does nothing.

Guessing this was changed as too many pilots would kill their engines? Just reporting it since it's different from the info in the PDF.

[IvanK]

It works just fine for me.

Whatever you use to adjust pitch just move it to 0 that = Coarse
Move it to 100% that = Fine

(sure the changeover is near the 50% position but its not critical you only need the two settings).

[FS~Hawks]

is there a mirror in Australia ? corz it's goning to be a 12hr down load if there is not ?

[Romanator21]

I've just noticed a small issue with the I-16 type 5
the 3D model have no flaps (wich is correct IIRC )
but when you press the flaps key the message "landing flaps" is diplayed

The type 5 does not have the central split flap under the wing. However, you will notice that the ailerons lower instead. The type 18/24 has both the dropping ailerons and the split flap underneath.

[kennel]

There is a setting in the config file that no longer works, HakenAllowed=1 placed in the [game] paragraph used to allow historical markings on the Finnish aircraft as well as the swastika on the tailplain of the German aircraft.

This setting did work in 4.09b as well as 4.08m

[inferno7312]

New maps doesn't run smooth on my machine.
Especially, in the cockpit view. if I do a fast turn, Game will be a little stuttering.. It is not so bad, but it is not as smooth as old maps.
I don't think my hardware is too low. I checked the FPS. it showed 56-60.

My system
Q6600 @ 3.0G
4GB RAM
8800GT 512M
vista 32


little stuttering only occurred in cockpit view. if I use outside view, everything is OK.

[HarryKlein]

The type 5 does not have the central split flap under the wing. However, you will notice that the ailerons lower instead. The type 18/24 has both the dropping ailerons and the split flap underneath.

thank you for the information Ü

[FC99]

There is a setting in the config file that no longer works, HakenAllowed=1 placed in the [game] paragraph used to allow historical markings on the Finnish aircraft as well as the swastika on the tailplain of the German aircraft.

This setting did work in 4.09b as well as 4.08m
It only worked in Russian or modded game, International version doesn't support HakkenAllowed due to legal issues.
FC

[Azimech]

The QMB maps Bessarabia and Slovakia, although beautiful by themselves, have starting positions near the edge of the map, which is ugly. Why not place them a bit towards the center?

Also, is the Fokker really so hard to fly? It stalls or snap when using full aileron.

[6S.Maraz]

Hi DT, thanks a lot for the 4.09!!!

The SM79 is a masterpiece (cockpit detail is great) and flies beautifully, but there's a texture issue on the bombing sight right brace, see here, it's indicated by the red arrow:
http://i664.photobucket.com/albums/vv4/ivagiglie/IL2_bug/SM79_texture_issue.png

It's not a bug, it's an elicoidal scale present in the original gunsight

Maraz

[6S.Maraz]

I think somethings wrong with SM.79's gunner MG modelling. Gunner MG belt looks strange. It looks like bullet belt comes from up invisible belt box.


Usually IL-2 aircraft have no ammo belts, for SM.79 we decided to do something new and provide an ammo belt. Of course it cannot be animated in a completely realistic way, but if you shoot at enemy planes it wil look just good.

Maraz

[FC99]

The QMB maps Bessarabia and Slovakia, although beautiful by themselves, have starting positions near the edge of the map, which is ugly. Why not place them a bit towards the center?

That's unfortunate but if we put them in the middle of the map than AI will have problems with mountains if player set their flight low. So we had to chose between "boring" scenery and AI crashing all the time.


Also, is the Fokker really so hard to fly? It stalls or snap when using full aileron.
Reports says that it had nasty tendency for wing tip drops.
Quote from Finnish pilot:
"we found soon that it is pleasantly stable when firing. Its behaviour was quite good, but tad some temperament, that could make things hot for unprepared pilot. Stalling without any warning, even in higher speed, could be very surprising for a unexperienced pilot, but most dangerous was landing. Nose pointed high up and tailplane losed effectivness. If the speed dropped too much during approach, you had to have a lot of luck and we really lost couple of planes during landing"

[EJGr.Ost_Caspar]

The QMB maps Bessarabia and Slovakia, although beautiful by themselves, have starting positions near the edge of the map, which is ugly. Why not place them a bit towards the center?



Because we had to make sure, that quick missions work even if you start with 16 AI-planes on 200m altitude. As AI would probably have difficulties in areas with hills and mountains, a relative flat area was chosen to let the things happen.
Its a compromise.


EDIT: FC99 was faster. Good morning! :D

[Viikate]

Also, is the Fokker really so hard to fly? It stalls or snap when using full aileron.

Yes, Fokker was a nasty plane to fly. Several finnish pilots were killed because of this behaviour. And you probably mean full elevator?

[SturmKreator]

Great patch guys, I apreciate your work very much, but i ahve a few qustions:

1.- I thin with the new patch you could optimized de game for multicores?
2.- Ta-152c turn better, but is to slow, maybe you could fix that.
3.- Ta-152H-1 in the real life have a lebel stabilizer, you could fix that to?

Very well guys I like your jobe

[gbollin]

I made a clean install of il2. Patched the the game to 4.08. Downloaded
the English international version from Misson4today.
I made sure the game ran in 4.08 then installed the patch. The game will not
even start to try and run just sits at the desktop screen.
I have the US release of IL2 Sturmovick 1946.

[satan]

Firstly thanks for the great work in 4.09.

I am in love with the i-16 t6, in particular the exposed wheel wells, great details.:grin: ( i did some rata skins a long time ago with exposed wheels and have been waiting for this)

The sm79 damage model needs examining.

I accidentally ran a hurricane wing through the sm79's wing the result being hurricanes wing torn from the root as the sm79 flies along no problems.

I have repeated this several times with the usual loss for the sm79 being a flap. ( no big deal for the flying tank!!)

SM79 was a tough plane but not that tough!

[Asheshouse]

Yes, Fokker was a nasty plane to fly. Several finnish pilots were killed because of this behaviour. And you probably mean full elevator?

I am so pleased that its not just me that has the stall problem.
On the plus side, I just love the damage model --- which I've now seen from many angles.

Ashe

[Ojisan_bart]

Hi, in the Slovakia W map are the rivers land if you drop bombs on it or land on it.....

http://i9.photobucket.com/albums/a68/Ojisan_bart11/lonwater.jpg

[Seamus]

Hi,

I just finished installing a clean copy of 1946 and patched it up to 4.09. Now Im ready to fire it up, but I can't get past 95% loading mark at the splashscreen:(
What do I do?? I'm running Win7 x64.

Tnx in advance,
Seamus

[Viikate]

Seamus & gbollin. Have you tried this DLL change?

http://forums.ubi.com/eve/forums/a/tpc/f/23110283/m/6001031497

[Seamus]

Tnx for your reply, but no, no joy.

Besides, 408 itself didnt come withnew dll's nor did 4071. Anyway, I tried the dll's of an other installation I got which worked on that installation (ie. modded)
but no joys.

Why is it always so difficult to get a game running after a new patch, 'so called' fix?!?! Its always the same story :evil:

Seamus

[LLv24_Pehmis]

S! all

I would like to note here a possible bug. And this one might be already noted, or might not be a bug (doubt it).

We were flying with some fellow squad members "testing" the new Fokkers. One of us was flying a TB-3 and the rest of us trying to shoot it down. None of us have a real lot of experience flying the TB-3... but here is what we found:

The (possible) bug we found:
The TB-3 can takeoff from a distance of only ~50-100m and sometime even less? Even with a full bomb load. (meaning rolling started from zero speed)

Nothing serious, and possibly known but thought to let you guys know of this.

Thank you Oleg & DT for this patch!

Pehmis
Squad leader
www.llv24.com

[laurek]

After applying patch 4.09m i cant run Il2 either. I have tried a complete reinstall from the DVD and patched it up to 4.08m as it says in the readme. I also tried to copy the Dll's mentioned above from a backup folder i made but to no avail.
My previous install ran without any problems and i didnt use any mods. I use Vista 32bit if thats any help

[Lucas_From_Hell]

Just found this one less than 5 minutes ago:

In QMB, Slovakia map (I only tested it on Winter, but I think it's also worth for Summer too), when you set your side to "Axis" and the Target as "Scramble", you take-off from an Allied base. I was a little bit surprised to see cannon shells exploding around (and at) me while I was starting the engine.

[FAE_Cazador]

Fokker DXXI Early, with skies, in QMB Moscow Winter map.

When landing on a snow covered airstrip, the skies "submerge" under snow, as does wingtip, if plane rolls, without neither crashing nor breaking.

Also, if you press on wheel brakes, you still can hear the sound of brakes as in a wheeled plane.

Track available, sent to DT email adress.

BTW, very nice D-XXI, and excellent cockpit, really a very high-quality work.

[gbollin]

That worked for me the dll change did the trick. Thanks

[Aviar]

I don't think this is a bug exclusive to 4.09m, but I will report it anyway.

Take a P-38 up high and you will notice that the contrails for this plane are not appearing DIRECTLY behind it like other planes. The contrails are actually appearing ABOVE and behind the plane.

I have screenshots if you would like to see them. Obviously, this is in a totally unmodded 4.09m.

Aviar

[FC99]

I don't think this is a bug exclusive to 4.09m, but I will report it anyway.

Take a P-38 up high and you will notice that the contrails for this plane are not appearing DIRECTLY behind it like other planes. The contrails are actually appearing ABOVE and behind the plane.

I have screenshots if you would like to see them. Obviously, this is in a totally unmodded 4.09m.

Aviar
Please post it, I was testing something with contrails few days ago so if there is something wrong with contrails now is good opportunity to fix it.

In QMB, Slovakia map (I only tested it on Winter, but I think it's also worth for Summer too), when you set your side to "Axis" and the Target as "Scramble", you take-off from an Allied base. I was a little bit surprised to see cannon shells exploding around (and at) me while I was starting the engine.You are correct, unfortunately I made mistake with AAA, we will correct it for next patch, I'll have to redo all QMB missions for it anyway .:)

[Aviar]

FC99,

Notice the P-38 contrail is ABOVE and behind the P-38. The contrail behind the P-47 is directly behind the P-47. As far as I know, this only appears with the P-38 (all 3 models).

Aviar

[csThor]

Eh, Aviar ... was it really necessary to save those screenshots in this large resolution and as BMP? JPGs of 800x600 would have been sufficient and much faster in loading. :(

[ramstein]

Hi DT, thanks a lot for the 4.09!!!

The SM79 is a masterpiece (cockpit detail is great) and flies beautifully, but there's a texture issue on the bombing sight right brace, see here, it's indicated by the red arrow:
http://i664.photobucket.com/albums/vv4/ivagiglie/IL2_bug/SM79_texture_issue.png



I found a bizzare issue with the SM.79. it is the only plane in all of the planes in IL-2 that the controls do not respond to key inputs for the flaps. Why does this only happen to this plane?

Thanx..

[csThor]

Auto-flaps, ramstein. Auto-flaps. ;)

[ramstein]

Auto-flaps, ramstein. Auto-flaps. ;)

Yeah, I was just reading about these... No control at all at certain speeds..
wtf... why would anyone design it like that.. no wonder the plane was outdated by 1940..

I was getting some other weird responses from certain key commands, but decidecd not to bring those up intil I fugure out what else this plane is weird with..

[jurinko]

Hi, in the Slovakia W map are the rivers land if you drop bombs on it or land on it.....

http://i9.photobucket.com/albums/a68/Ojisan_bart11/lonwater.jpg

It is a compromise - the map is defined as a winter one, but with liquid water. You get winter default skins and solid water.

Still I do not understand how someone tries first to land on the water :-P but the screen is beautiful :-)

[Ojisan_bart]

Thx, first i try to land on a river in the zero seaplan and than i saw somthing wrong so i did it again in this byplane to take the pic... enyway this is a great addon to the game, thx very much..

[Lucas_From_Hell]

Guess what! A Jesus-style aircraft. It walks over water too :p

[Viikate]

Fokker DXXI Early, with skies, in QMB Moscow Winter map.

When landing on a snow covered airstrip, the skies "submerge" under snow, as does wingtip, if plane rolls, without neither crashing nor breaking.

Track available, sent to DT email adress.


Sorry I coudn't find the track from the email, but I think I know what you mean. Problem with recorded tracks is that they don't store enough information so that all visual element could be replicated perfectly. However in game itself they should work ok.

For example skis are not aligned with ground when plane lands, since there is no information available that when they should turn. Problem doesn't exist with Gladiator's skis since they are always alignd with ground, but that's slightly incorrect behaviour for the skis.

[TheGrunch]

Please post it, I was testing something with contrails few days ago so if there is something wrong with contrails now is good opportunity to fix it.
I believe the P-51 is the same, I'll test some aircraft later today, though.

[Aviar]

Actually, I just checked the P-51 (all models) and the contrails look fine.

Aviar

[TheGrunch]

Actually, I just checked the P-51 (all models) and the contrails look fine.

Aviar
Yeah, I just checked, you're absolutely correct. I wonder what aircraft I was thinking of...

The 38 is definitely off, though.

[Azimech]

Yes, Fokker was a nasty plane to fly. Several finnish pilots were killed because of this behaviour. And you probably mean full elevator?

Unfortunately, no. I really mean full aileron.

[Ritchie]

Hi Ubies,

I'm Ritchie, new to this forum, fresh from the file front.. First, hats off & many thanks to Team Daedalos for the terrific 4.09 patch, great stuff!

I installed directly upon 1946 4.08m DVD version, German language.
Everything works fine, but there's one glitch that spoils it again for me:
When flying offline, German radio traffic is mutilated. Voices are constantly cut off, on and off, on and off, it's hardly understandable.

Can't get it back to normal! Maybe somebody out there has an idea.

Tried out a couple of things, inside and outside IL-2, but still can’t get a grip on this nervy voice problem. That is, about half of the radio in-flight communication appears as it should, the rest is just dropped. Easy to notice because the written text lines are all complete.

Strangely, it’s not always the same modules that are missing, it’s totally unpredictable.
Example:
> text should be:
- No. 2, verstanden
- No. 3, verstanden
- No. 4, verstanden

> it comes out once as:
- No. 2, ---
- --- , ---
- No. 4, verstanden

> the next time it is:
- --- , ---
- No. 3, verstanden
- --- , verstanden

and so on

As if the virtual playback mixer could no longer count to three.

conf.ini is o.k. & unchanged. Music & sound is o.k. anyway. The. wav voice module files in the speech folder are all there , unchanged and intact.
So the bug – if it is one- is messing up coordination of the voice modules.
Now I’m not a programmer. I’ll post this around and then call it a day.

Have a nice flight

Ritchie

[FAE_Cazador]

Sorry I coudn't find the track from the email, but I think I know what you mean. Problem with recorded tracks is that they don't store enough information so that all visual element could be replicated perfectly. However in game itself they should work ok.

For example skis are not aligned with ground when plane lands, since there is no information available that when they should turn. Problem doesn't exist with Gladiator's skis since they are always alignd with ground, but that's slightly incorrect behaviour for the skis.

Thanks, mate, I understand what you mean. In fact, when I landed I didn't notice what happened, just from the cockpit. It was later when I watched the track that I realized the funny "inmersion" effect.

I attach here the .ntrk file in a Zip package. As I attached it in my last mail directly as a .ntrk file, perhaps something went wrong and you couldn't find the attachment.

Kind regards.

[II/JG54_Zent]

I installed the 4.09m patch international version on a clean 4.08m vanilla version...
I checked the 4.08m version before installing the patch. It worked fine.

After patch 4.09m my game doesnt even start. If i click on the exe nothing happens.

I doubleckecked the downloaded patchfile. It has the correct (i suppose) 566MB. In order to single out a possibly corrupted file i downloaded the patch from another source and tried again... same... no reaction at all...

I run WinXp service pack3, all latest patches, Athlon XP 3200, 2 gig ram, Nvidia 7900 GT 512 MB vram...

As i read in this thread it seems i am not alone..

Guys, i am sorry to say but after all this time for producing the patch you produced a huge bug i would say.

Any help appreciated.

II/JG54_Zent

[ramstein]

do you have the dvd in the drive?

I installed the 4.09m patch international version on a clean 4.08m vanilla version...
I checked the 4.08m version before installing the patch. It worked fine.

After patch 4.09m my game doesnt even start. If i click on the exe nothing happens.

I doubleckecked the downloaded patchfile. It has the correct (i suppose) 566MB. In order to single out a possibly corrupted file i downloaded the patch from another source and tried again... same... no reaction at all...

I run WinXp service pack3, all latest patches, Athlon XP 3200, 2 gig ram, Nvidia 7900 GT 512 MB vram...

As i read in this thread it seems i am not alone..

Guys, i am sorry to say but after all this time for producing the patch you produced a huge bug i would say.

Any help appreciated.

II/JG54_Zent

[brando]

I had a similar problem with installing over a clean copy of 4.08m - a SecuRom error! It's been a long time since I saw one of those :(
Even when I put in the disc it wouldn't work: told me I had the wrong disc and shut me down. To get around this, I asked a mate of mine who had a non-SR version with 4.09 installed to send me his il2fb.exe file, and that worked just fine.

Also, I fixed up a mate of mine by getting him to substitute his new mg_snd and mg_snd_sse dll files for the originals in 4.08. He was having the same symptoms as you Zent, and has a similar rig also.

B

[flyingbullseye]

One small problem for me. When I finish a offline mission all the buttons at the bottom of the screen such as the refly, main menu, apply and save track are gone and so is the mouse icon. The text is still there but that's it. I've never had this problem and installed the patch over a completely clean 4.08m version. Any ideas?

Flyingbullseye

[Igo kyu]

One small problem for me. When I finish a offline mission all the buttons at the bottom of the screen such as the refly, main menu, apply and save track are gone and so is the mouse icon. The text is still there but that's it. I've never had this problem and installed the patch over a completely clean 4.08m version. Any ideas?

Flyingbullseye
First off, I don't know what causes this.

I have seen it before, it's not happening to me currently. I think it may be connected to the latest Ati drivers. When I recently reinstalled Vista, it selected it's own driver for my card and I've not upgraded from that for fear of this. When it did happen to me, switching from open GL to Direct X fixed it, there may be something cleverer that also fixes it, if so I'd like to hear about it. Could be Vista isn't part of the problem, but it is what I'm using.

[karvis]

Hi, one problem which I have: I understood that there should be a possibility to save/load different joystick profiles in Input Options Setup page. I saw some video in youtube which was telling about this. But at least in my version this is not visible. The drop-down list for four different joysticks aren't there, actually that Input page looks excatly same as in 4.08m version. Should it be enabled somehow somewhere or... (conf.ini?) am I missing something. I installed 4.09m patch to well-working 4.08m (no mods...) and everything has worked fine for six years now. Any help would be appreciated. Thanks.

[karvis]

Hi,
I read the SimHQ.com article again: http://www.simhq.com/_air13/air_420b.html

I'd guess that joystick profile feature wasn't included in the 4.09m package after all. Would have been nice feature though. ??

[kennel]

Hi Ubies,

I'm Ritchie, new to this forum, fresh from the file front.. First, hats off & many thanks to Team Daedalos for the terrific 4.09 patch, great stuff!

I installed directly upon 1946 4.08m DVD version, German language.
Everything works fine, but there's one glitch that spoils it again for me:
When flying offline, German radio traffic is mutilated. Voices are constantly cut off, on and off, on and off, it's hardly understandable.

Can't get it back to normal! Maybe somebody out there has an idea.

Tried out a couple of things, inside and outside IL-2, but still can’t get a grip on this nervy voice problem. That is, about half of the radio in-flight communication appears as it should, the rest is just dropped. Easy to notice because the written text lines are all complete.

Strangely, it’s not always the same modules that are missing, it’s totally unpredictable.
Example:
> text should be:
- No. 2, verstanden
- No. 3, verstanden
- No. 4, verstanden

> it comes out once as:
- No. 2, ---
- --- , ---
- No. 4, verstanden

> the next time it is:
- --- , ---
- No. 3, verstanden
- --- , verstanden

and so on

As if the virtual playback mixer could no longer count to three.

conf.ini is o.k. & unchanged. Music & sound is o.k. anyway. The. wav voice module files in the speech folder are all there , unchanged and intact.
So the bug – if it is one- is messing up coordination of the voice modules.
Now I’m not a programmer. I’ll post this around and then call it a day.

Have a nice flight

Ritchie

I am having the same trouble as Ritchie confused comms running a Kurland DGEN campaign, ask ground control for heading & u only get the subtitles & in the next message he talks to u.

[MicroWave]

Hi,
I read the SimHQ.com article again: http://www.simhq.com/_air13/air_420b.html

I'd guess that joystick profile feature wasn't included in the 4.09m package after all. Would have been nice feature though. ??

At the start of the video there is a message:

Everything shown in this video
is still WIP
and will be released after 4.09

[II/JG54_Zent]

do you have the dvd in the drive?

i tried both with Drive and original il2fb.exe and also with non SR exe.
If i use the original Disc and exe the securom testing icon (rotating disc) appears and then nothing anymore....

if i use a modified exe the hourglass symbol appears for a few secs and then finish...

II/JG54_Zent

[andrea78]

S!

my 4.08 starts without problem: after 4.09 patch, the game CTD after 5% loading (even with old dll).
I play it under vista32 (with administration privilage).
Any suggestion? Thanks!

[II/JG54_Zent]

The problem seems to be in the mg_snd and mg_snd_sse dlls ... i exchanged those with the files from the 4.09 beta and game loads up normal and runs... the new planes maps etc. all available..
So one could say problem solved.
But i wonder what is the difference with the new mg_snd dlls ? Where will my game now be different. Will i be really online compatible or have strange problems ?
With other words: What has been changed with the mg_snd dlls ????

Any answer from Daidalos team ?

II/JG54_Zent

[csThor]

Those DLLs come from Maddox Games (or rather through them - don't know their origin). Not sure if our coding gurus can make statements about.

[FC99]

But i wonder what is the difference with the new mg_snd dlls ? Where will my game now be different. Will i be really online compatible or have strange problems ?
With other words: What has been changed with the mg_snd dlls ????

Any answer from Daidalos team ?

II/JG54_Zent
DT didn't change anything in dll files, I'm also using old mg_snd.dll and mg_snd_sse.dll files, mine are from 2006. I think that Oleg didn't change dll's either, I don't have 409 dll's but I bet they are from few years ago.

Same problem with dll's was here with 409 Beta and maybe even earlier but most people forgot about it. When you add various mods to the equation than complete mess is expected. We must get used to live with SNAFU. :grin:

FC

[andrea78]

DT didn't change anything in dll files, I'm also using old mg_snd.dll and mg_snd_sse.dll files, mine are from 2006. I think that Oleg didn't change dll's either, I don't have 409 dll's but I bet they are from few years ago.
FC

I agreed, I don't think it is a dll problem: I changed them without solve the issue...:(

[II/JG54_Zent]

DT didn't change anything in dll files, I'm also using old mg_snd.dll and mg_snd_sse.dll files, mine are from 2006. I think that Oleg didn't change dll's either, I don't have 409 dll's but I bet they are from few years ago.

Same problem with dll's was here with 409 Beta and maybe even earlier but most people forgot about it. When you add various mods to the equation than complete mess is expected. We must get used to live with SNAFU. :grin:

FC

This is a probably a quite realistic and open answer but i think a very problematic one too.
It shows no real sense of responsibility for the game at either Daidalos team and/or Maddox team. As we all know the devil is in the details, if an important technical part of the game is not working properly in the new "standard" installation it is not a trivial thing, its a major bug and should be adressed by a responsible developer.
Either a game is supported correctly and then it is necessary to research and solve such issues in a responsible manner. Or it is not supported and then there should be nothing such as an official patch, then 4.09m should be regarded as a Daidalos Mod or such.
I am used to live with SNAFU regarding Il2 since the mods came out, but really SNAFU kills the fun... endless incompatibilities, empty servers because this or that special mod is needed, a general splitting up of the online community in specialied fan groups of this or that mod. I had some hope for 4.09m to establish a new basic ground for us, but that casual manner of treating severe bugs makes me feel sceptic about this.

As a technical side note: dll problems may not be the problem for ALL non game start problems, but at least in my case they are clearly the responsible files. The new 4.09m dlls are listed with 372 Kb each, dating from 05.06.2007.
The old beta 4.09 are 304 and 348 kb from 04.09.2006...

I would be happy about an INFORMED answer to what problems this might cause and whether it will be solved or not or if it is no problem, even on crt=2 servers and such to run the old dlls.

Anyway, thx for the effort which goes into developping all this stuff.. but dont get sloppy...it would spoil all the great work..

II/JG54_Zent

[cmirko]

there is no problem with CRT=2 settings on server and client with different sounds dll's...

cheers

[mkubani]

Hello Zent,

Do you think I was sloppy when I used to fly with you in II/JG54? ;)

We tested 4.09 for months. None of us and external testers had the problem with those dll files. It's more a hardware (sound card) related issue than a software one related to IL-2 or even 4.09. And out of many thousands people who have downloaded the patch, only very small % has this problem. So how were we supposed to catch this one? We can't test every HW out there. No game developer can. So how do you relate this to DT not being responsible or detail oriented? The dll fix is out there and it's simple one. So use it please.

I think you had received an informed answer from other DT members before. Just try to understand it.

Martin (used to be II/JG54_Jopo)


This is a probably a quite realistic and open answer but i think a very problematic one too.
It shows no real sense of responsibility for the game at either Daidalos team and/or Maddox team. As we all know the devil is in the details, if an important technical part of the game is not working properly in the new "standard" installation it is not a trivial thing, its a major bug and should be adressed by a responsible developer.
Either a game is supported correctly and then it is necessary to research and solve such issues in a responsible manner. Or it is not supported and then there should be nothing such as an official patch, then 4.09m should be regarded as a Daidalos Mod or such.
I am used to live with SNAFU regarding Il2 since the mods came out, but really SNAFU kills the fun... endless incompatibilities, empty servers because this or that special mod is needed, a general splitting up of the online community in specialied fan groups of this or that mod. I had some hope for 4.09m to establish a new basic ground for us, but that casual manner of treating severe bugs makes me feel sceptic about this.

As a technical side note: dll problems may not be the problem for ALL non game start problems, but at least in my case they are clearly the responsible files. The new 4.09m dlls are listed with 372 Kb each, dating from 05.06.2007.
The old beta 4.09 are 304 and 348 kb from 04.09.2006...

I would be happy about an INFORMED answer to what problems this might cause and whether it will be solved or not or if it is no problem, even on crt=2 servers and such to run the old dlls.

Anyway, thx for the effort which goes into developping all this stuff.. but dont get sloppy...it would spoil all the great work..

II/JG54_Zent

[II/JG54_Zent]

Hello Martin/Jopo,

as you can see in this forum there seem to be a few more people who have start problems, interestingly under many different systems and OS versions. I have a regular Creative Audigy Soundcard install with latest drivers and no issues -nothing exotic here..

I dont know whether you are sloppy or not from your past in II/JG54. You were a great and very intelligent pilot and a good helpfull comrade, but a bit unreliable in participation and communication with us, thats all i know and i think it has nothing to do with this issue.
But i understand that you say that you made a huge effort that this patch is good and as bugfree as possible and i am sure that is true and i know your great dedication to this game. Thank you a lot for this immense work from which we all profit !!

But if a patch is issued and dlls are included which have a known issue which is not adressed, no remark of it in the readme or anything... this is at least somehow not so clever, isnt it ? Imagine someone maybe not so familiar with Il2 as us who patches his game and then at startup...blupp.-.nothing... actually i was puzzled myself and a bit upset.... i didnt and couldnt know that there is a rather simple solution to it... its clear now that those dlls come from Maddox and its their responsibility that this bug was never adressed. But Daidalos knowingly integrated them in the patch without any remark about those problems.
So change your readme and maybe integrate the old dlls as alternative in the patch and nobody can say anything about sloppyness...hey... and dont let a little provocation get under your skin dude.. you are too good for that..

yours,
Zent

[Brain32]

The dll issue is nothing new and has been present in v409 too, IIRC it was related with older AthlonXP processors meaning ONLY owners of old AXP CPU's had such a problem.

Also if we want to talk problems here, a 50$ blockbuster game; "Call Of Duty MW" had the same(similar) issue and one had to mess around with it alone as nobody on official places knew wtf were we talking about...so I would say this is pretty much making a big deal out of nothing really....

[Billy885]

Zent,

I am glad Zent that you think the creative drivers are good one. I found out differently with my Creative sound card and went to "kX project" drivers and had no more problems with my creative sound card.

[Dash 8]

I am having the same trouble as Ritchie confused comms running a Kurland DGEN campaign, ask ground control for heading & u only get the subtitles & in the next message he talks to u.


I too have the issue with the speech being cut off or not spoken at all on the radio. I had this with the 4.09beta too, so I've stayed with 4.08 all this time.

Everything installed as instructed: 4.07 off the disc, 408m patch, then the new 4.09m. I've had no other issues other than speech being cut off or missing completely, just like the beta had.

Using an Audigy 2 sound card if that helps.

[csThor]

Did you perhaps try the older versions of mg_snd.dll and mg_snd_sse.dll? Perhaps the new ones cause this as well? Mission4today.com has an older set under DOWNLOADS - PATCHES - DLL PATCHES ... Backup your current ones, copy these into the Il-2 root folder and see if the problem is cured.

[andrea78]

The problem (in my config) is not dlls, but files.SFS: mantaining the old one (from dvd), the game starts, while with the newer it crash just after loading.

ps: with old files.SFS, the game starts with older/newer dlls

[csThor]

WTF? That's a new one for me ... :shock:

[Dash 8]

Did you perhaps try the older versions of mg_snd.dll and mg_snd_sse.dll? Perhaps the new ones cause this as well? Mission4today.com has an older set under DOWNLOADS - PATCHES - DLL PATCHES ... Backup your current ones, copy these into the Il-2 root folder and see if the problem is cured.

I did as you suggested and got the older sound.dll's from Mission4today and IT WORKED! No more cut off and missing speech in the radio transmissions. I tested it in 2 different missions in 2 different Dgen Campaigns and no issues with the radio.

So I guess these older dll's fix a loading error for some people (which I didn't have), but also fix the speech cut off/missing error that I had. Thanks for the idea; I didn't think to try it since I had no trouble starting the sim.

[andrea78]

WTF? That's a new one for me ... :shock:

I forgot to write the without new files.SFS the game works but the patch is not actived (I don't see new planes)

[Billy885]

I forgot to write the without new files.SFS the game works but the patch is not actived (I don't see new planes)

If you are using the 4.08 (files.SFS) then you are running 4.08. That is the file that tells the game what SFS files to load and not load.

If you are having trouble with 4.09 files then I would suggest downloading again from a different source and try again. One of the files might be corrupt.

Good luck to you.

[JG27_brook]

The 109,s flight controls at 400kph is PORKED

[IvanK]

No changes were made to BF109 flight controls they are the same as they have been since way back.

So Brook please be more specific other than Porked ? How about a detailed list of what you consider is wrong, how it should be unporked and provide the references to support your case.

[MicroWave]

I forgot to write the without new files.SFS the game works but the patch is not actived (I don't see new planes)

Are you sure that your game is v4.08m before you applied the patch?
You can see the version when the game is loading.

[kennel]

Did you perhaps try the older versions of mg_snd.dll and mg_snd_sse.dll? Perhaps the new ones cause this as well? Mission4today.com has an older set under DOWNLOADS - PATCHES - DLL PATCHES ... Backup your current ones, copy these into the Il-2 root folder and see if the problem is cured.

Thankyou csThor, those files you suggested have done the trick,no more speech errors.

[csThor]

:cool:

[andrea78]

downloaded from another link, now it works.... and it is absolutly fantastic! Thanks!

[JG27CaptStubing]

No changes were made to BF109 flight controls they are the same as they have been since way back.

So Brook please be more specific other than Porked ? How about a detailed list of what you consider is wrong, how it should be unporked and provide the references to support your case.

Mark Hanna's comments about the BF109 from an article written in Flight Journal Magazine.

Handling

Once settled down, with your adrenaline level back down to just plain high, you can take stock of the situation. The initial reaction is of delight to be flying a classic airplane, and the next is the realization that this is a real fighter. You feel aggressive flying it. The urge is to go looking for something to bounce and shoot down!

The roll rate is very good and very positive below about 400 km/h, and the amount of effort needed to produce the relevant nose movement seems exactly right. As the stall is reached, the leading-edge slats deploy-together, if the ball is in the middle; slightly asymmetrically, if you have any slip on. The aircraft delights in being pulled into hard maneuvering turns at these slower speeds. As the slats pop out, you feel a slight "notching" on the stick, and you can pull more until the whole airframe is buffeting quite hard. A little more and you will drop a wing, but you have to be crass to do it unintentionally.

Pitch tends to be heavy above 400km/h, but it is still easy to manage up to 500km/h, and the aircraft is perfectly happy carrying out low-level looping maneuvers from 550km/h and below. Above 550km/h, one peculiarity is a slight nose-down trim change as you accelerate. This means that when you run in for an airshow above 500km/h, the airplane has a slight tucking sensation-a sort of desire to get down to ground level. This is easily held on the stick, or it can be trimmed out, but it is slightly surprising initially.



Kinda interesting isn't it...

[TheGrunch]

Kinda interesting isn't it...
I think it is. Mark Hanna had plenty of experience flying Spits and 109s (such a pity he was killed), but without any information about the model of 109, details about its restoration and any kind of comparison to other contemporary aircraft it's not so much use to DT as otherwise. I'm sure you can easily provide the first two, though. Was it a Merlin-powered Buchon? Decent reference for an Emil, at least.

[udidwht]

Updated.

Possible bug.

When choosing from within the 'Single missions' USN>F6F-3>Carrier take-off mission the aircrafts main gear set slightly above the deck. Not sure if this is happening with any other mission/s. Running version 4.09m no mods clean install. Just to add I confirmed this issue only appears with the F6F-3 aircraft within the Single missions>aircraft take-off.

System specs:

WinXP Media Center 2005 Service Pack 3 (fully updated clean install)
Pentium D 930 3.0Ghz
2GB RAM PC2 DDR2-5300 667mhz
DirectX 9.0c Aug 2009
Gigabyte Radeon HD 4670 512mb (CCC 9.9)
Sound Blaster Audigy SE (drivers are current)
32in LG LCD
Thermaltake 430w PSU
DVD/CD-RW DL Lightscribe
DVD-ROM

[Ritchie]

Still referring to that voice bug.
Almost forgot to thank all you guys for pointing me to the right direction.
The mg_snd and mg_snd_sse dlls...exchange trick just did it for me. V 4.09m over 4.08m is now running smooth & fine. :grin:
A bit strange though that nobody can be more specific about the possible "side effects" of the twist - but then, I haven't noticed any so far. Has anybody else?

Now I don't feel like insisting on problems I do no longer or not yet have, I'm just glad the mill is grinding round again, and that's it for me.

Seems to be a real expert forum here! Will drop in in from time to time, for some exchange or just a chat.
CU

[IvanK]

There are plenty of references both modern and from WWII evaluations of most BF versions describing pitch response versus airspeed.

Out of interest in game BF109G2 at 500Kmh IAS you can obtain 6.8G and maintain it in a descending spiral.

Now where does that fit into the Porked index scale ?

We all know the in game 109 gets heavy on the stick at the higher speeds. Its been that way since IL2 hit the shelves many moons ago. The attempt to recreate the known pitch heaviness of the real aeroplane. Now if you think its overdone then at least detail what you expect. References to support your argument will also help.

There is some reasonable achievable G versus Airspeed data for late model BF109 available, and slightly more detailed than Pork ratings...

[JG27CaptStubing]

There are plenty of references both modern and from WWII evaluations of most BF versions describing pitch response versus airspeed.

Out of interest in game BF109G2 at 500Kmh IAS you can obtain 6.8G and maintain it in a descending spiral.

Now where does that fit into the Porked index scale ?

We all know the in game 109 gets heavy on the stick at the higher speeds. Its been that way since IL2 hit the shelves many moons ago. The attempt to recreate the known pitch heaviness of the real aeroplane. Now if you think its overdone then at least detail what you expect. References to support your argument will also help.

There is some reasonable achievable G versus Airspeed data for late model BF109 available, and slightly more detailed than Pork ratings...

Ironically nobody tends to complain about the G2s elevator response. It's all the other 109s.

You would be incorrect about the 109s behing heavy on the stick since it hit the shelves. I think it was 4.04 that introduced the cement elevator. Regardless of references most other planes in the game don't have this problem.

If it's supposed to be modling accuracy then I would ask the same from you. What references were used to support the idea of heavy controls at certain speeds. I can't find any so far. Most of what I have seen said it had excellent handling through out the entire flight regime but then again these aren't tests.

[Hood]

This is a bug reporting thread, not a flight model whine (even if that whine may be justified) thread. Take the argument elsewhere fellas.

[IvanK]

Hood I am a DT member.

Capt Stubbing try ANY of Eric Browns or the RAF's evaluations of the 109. There are numerous discussions of all 109 variants and elevator pressures and pitch response.

Get a copy of Wings of the Luftwaffe by Eric Brown or Augsberg Eagle by William Green which contains numerous reproductions of RAF evaluations.
Another good source is Peter Caygill's "Flying to the limit Testing World War II Single engine fighter aircraft". Messerschmitt BF109 at war by Armand van Ishoven also contains large junks of RAF evaluation reports describing BF109 control forces etc. Just about every single evaluation of the 109 makes reference to heavy elevator loads.

[JG27_brook]

Please explain about what to the 5000 or so Germans that flew the 109 in WW2 , and Oleg bases 109 on a brit that never even flew it in combat ?

Me 109 G-6:
Me109 was almost a dream come true for a pilot. Good controllability, enough speed, excelent rate of climb. The feel of the controls were normal except when flying over 600km/h - some strength was needed then.
- Erkki O. Pakarinen, Finnish fighter pilot, Finnish Air Force trainer. Source: Hannu Valtonen, "Me 109 ja Saksan sotatalous" (Messerschmitt Bf 109 and the German war economy), ISBN 951-95688-7-5.

Well 1/3 faster than what we now have in Olegs IL2 . HOPE you will be doing better in BOB !!

[IvanK]

Go and read the Evaluations then come back, they are a little more technical than the narratives you quote :)

[JG27_brook]

Go and read the Evaluations then come back, they are a little more technical than the narratives you quote :)

Maybe we should be basing the spit on German reports with that logic

[IvanK]

Most of the evaulations are quite complimentary on the 109 in a number of areas in handling etc .... but as you say these were written by a "brit that never even flew it in combat" ....so should we discard these nice bits as well ? Just about every source available both Allied and axis is used in an attempt to make the in game aeroplane as accurate as possible.

You are being silly Brook. Make the effort read the reports, it might alter viewpoint though I doubt it.

[brando]

Maybe we should be basing the spit on German reports with that logic

Well, maybe so, if any of those documents survived the war. The point of importance is that the evaluations made by the English test pilots were absolutely clinical in their accuracy because of the work they were doing. It was about both improving the British aircraft to compete, and about giving the British pilots accurate information on their opponents' aircraft. Propaganda has no place in these tests.

B

[fuzzychickens]

Please explain about what to the 5000 or so Germans that flew the 109 in WW2 , and Oleg bases 109 on a brit that never even flew it in combat ?

Me 109 G-6:
Me109 was almost a dream come true for a pilot. Good controllability, enough speed, excelent rate of climb. The feel of the controls were normal except when flying over 600km/h - some strength was needed then.
- Erkki O. Pakarinen, Finnish fighter pilot, Finnish Air Force trainer. Source: Hannu Valtonen, "Me 109 ja Saksan sotatalous" (Messerschmitt Bf 109 and the German war economy), ISBN 951-95688-7-5.

Well 1/3 faster than what we now have in Olegs IL2 . HOPE you will be doing better in BOB !!

There is such a thing as a dive back then, since the context in which he describes 600km/h isn't clear - one can't rule out that he was refering to the plane when diving from altitude.

Also, pilot accounts really shouldn't be turned into performance data. The data collected when these pilots test aircraft under controlled conditions are much better than making a plane do 600km/h level based on "X" pilot's account.

[Brain32]

For me and I did read A LOT on it quotations from both camps are more or less the same - anegdotal. I yet have to see somebody showing some technical evidence for this phenomenon. What is it?

I mean heavy controls - so OK, heavy for who? Take it to the daily basis, although rare if not extinct today there was a time when not every car or even truck had a servo steering wheel. Anybody ever tried to drive such a car or even a truck? It's damn harder to pull some "stunts" you do in your new car with two fingers while typing an SMS to your gf every day.
Both hands on the wheel buddy, and if you are not quite used to it it will take what will seem like A LOT of strenght to do it(LADA NIVA parking anyone?) Yet people that were/are used to it can still do it with one hand while typing an SMS!

Let's get back to airplanes, my point is that pilots that learned to fly and flew for years even in combat a plane which needs like 5lbs of power for pitching will surely get totally suprised and find it unpleasant to fly a plane that needs 20-30lbs or even more than that.
Does that mean that only Superman, Governer of California and Shaq O' Neal can fly that plane on the whole planet? I don't think so, and that's why I find this invisible force questionably realistic, yes not completely because I surely do not know all the details, but as things are now - I am not quite convinced...

[Oktoberfest]

Happy to see you here talking about the 109 FM, Brain.

OK, let's take a good start. DT is obviously more open minded about FMs and DMs issue that Oleg lately, and I'm sure that with good quotations and arguments, it will be possible to fix the issues that we've seen for the last years on the 109. The KI61 thread linked by another forum user comes to my mind.

Now, for DT, I would politely ask you about one thing to do about the 109s FMs : Can you verify if some datas where not misused when the 109's FM was "fixed" with 4.04 ?

The issue 109 pilots obviously face is that the elevator becomes concrete at higher speeds than 350 kph. It's contestable that this speed is very low to have a concrete elevator, but here is not my point. It seems that the speed taken to make concrete elevator was TAS and not IAS as it should be. With this possible mistake, the 109 keeps being relatively manoeuvrable at low to mid altitudes, but becomes uncontrolable at high altitude.

Over 7000 m, the 109's elevator don't respond at all anymore when you have around 220 kph indicated in IAS. In fact (and I could test it extensively), the Bf110G2 is better in manoeuvrability than the 109K at speeds above 250 kph at that altitude (from my POV, but I flew the 110G2 extensively the last years).

I'm sure Brain, that has a large collection of documents about various 109s will be able to deliver you the documents he has about the aircraft in a structured manner, but could you please check that first issue first ? (mixing between IAS and TAS for locking of the elevators at high altitudes) ?

Thank you very much.

[Bulau]

I, and a few others, have had a problem with the 4.09 Server Patch. After applying the patch to a working 4.08 Dedicated Server, on startup the server crashes to desktop with no error messages, before completely finished loading.

In my own case, I have resolved this problem by replacing the following new .dlls with the old ones from the working 4.08 server:

il2_core.dll
il2_coreP4.dll
mg_snd.dll
mg_snd_sse.dll

I did not individually test to see if any one of those was the only culprit.

My server runs Win2KPro and AMD Athlon 1.6GHz.

[Lazarus]

So have a lot of the FM's been altered? Planes I've flown for years are flopping and stalling. Even the MC205 seems much more spineless. :(

If so, do you have a report listing the planes that underwent FM modifications and why? I'll apologize now if this has been discussed and hope some one can link me to the answer and/or the list of altered planes.

Thanks!:)

[blowpipe]

I ran into a weird thing;

Playing a track of sm-79, the skin has been changed from the track.
When I change the skin in the original mission in the FMB ,it also changes the skin in the track??? after recording?

When I belly-land the SM-79 , the engines (propellors) keep on turning.

And is it possible to make the instrument lights somewhat brighter? for better reading?:rolleyes:

[csThor]

No FM work was done by Daidalos except the minor issues listed in readme. Yet ... :cool:

[Lazarus]

No FM work was done by Daidalos except the minor issues listed in readme. Yet ... :cool:

I know that many don't think highly of the 185, but it seems that something has definitely changed. It does nothing but stall. The MC205 also seems a lot more unstable.

Could it be stick settings? I have always used Crazy Ivans stick settings. Would this, some how, be different in 4.09?

Is your "yet" a polite indicator that recent FM changes have Maddox finger prints on them?:o It is what it is.....it's ok if the FM has been changed, but I would like to know before I go ripping into my stick configurations.

[csThor]

Can't say anything regarding Maddox Games. I - personally - don't think they touched anything (since they're up to their elbows in work for SoW) so I'm not sure where the effects come from. I just don't know ... maybe placebo rearing its ugly head again? :mrgreen:

[Aviar]

A tiny bug to report on one of the new 4.09m QMB missions.

Map: MTO
Target: Airbase
Defence: None

Although Defence is set to 'None', there is still a nasty AAA Tank (Coelian) defending the base. There should be no AAA on the base at all. (There is a seperate AAA setting for that).

Aviar

[Lazarus]

Can't say anything regarding Maddox Games. I - personally - don't think they touched anything (since they're up to their elbows in work for SoW) so I'm not sure where the effects come from. I just don't know ... maybe placebo rearing its ugly head again? :mrgreen:

Oh I have no doubt it could be a sugar pill. The weird thing is, several had mentioned a huge light difference in the planes I mentioned earlier. I remained skeptical until I flew them. It wasn't subtle. Maybe I will get a few more hours sleep tonight.:grin:

[FAE_Cazador]

A tiny bug to report on one of the new 4.09m QMB missions.

Map: MTO
Target: Airbase
Defence: None

Although Defence is set to 'None', there is still a nasty AAA Tank (Coelian) defending the base. There should be no AAA on the base at all. (There is a seperate AAA setting for that).

Aviar

Same bug with Crimea map in QMB: with No AAA, ships still fire to blue SM-79 .

[Lucas_From_Hell]

Well, if they changed the M.C.200 flight model to increase drag because of its airframe, it's possible that it also affected other Macchis like the M.C.205, considering that they have a similar airframe, after all...

[Lucas_From_Hell]

"with No AAA, ships still fire to blue SM-79"

This has always occured. I think this comes back from the first IL-2, but I don't remember exactly. But I'm 100% sure it happened on 4.07 and 4.08.

[brando]

"with No AAA, ships still fire to blue SM-79"

This has always occured. I think this comes back from the first IL-2, but I don't remember exactly. But I'm 100% sure it happened on 4.07 and 4.08.

I also recall this always being so. "No AAA" affects only airfield-defence-type fixed guns. Ships and tanks are not (and never were) affected by this setting.

B

[IvanK]

The MC200 FM was the only one adjusted the 202 and 205 were untouched.

[Romanator21]

Regarding MC 200s: When firing the guns of the type 7 and type 7 fighter-bomber, the muzzle flash is very bright and annoying. On the type 3 it is nonexistent. Whichever is the correct version, I don't know, but maybe it should be looked at. :confused:

[Bel Air]

IL-2 sometimes fails to initiate when I try to start the game. Occurs directly from the executable and from the Hyper Lobby. I have to restart Win XP to get the game to start.

When I restart Win XP it says DIEm Win is still running and I have to end program to restart.

Any help would be appreciated.

[Peteriong]

Two minor bugs in 4.09 QMB:

Side: Axis
Map: Pacific islands
Target:Armor
Error me ssage "Data file corrupt"

Side: Axis
Map: Pacific islands
Target: Bridge
No bridge spawn for bombing

[brando]

IL-2 sometimes fails to initiate when I try to start the game. Occurs directly from the executable and from the Hyper Lobby. I have to restart Win XP to get the game to start.

When I restart Win XP it says DIEm Win is still running and I have to end program to restart.

Any help would be appreciated.

After a lot of Googling I found this explanation here at simhq (http://simhq.com/forum/ubbthreads.php?ubb=showflat&Number=2508875) Hope it helps you clear it up.

B

[Aviar]

Here are two long-time bugs I forgot to mention earlier:

1. When playing online, if a twin-engine plane has one engine damaged (prop not spinning), other players viewing the plane will see both props not spinning. It's shocking to see the plane flying in this state.

2. 'Type 94 Truck' (Japanese vehicle, both Stationary Object and Moving Vehicle) is not able to be padlocked by the player. To be honest, this does not seem to be 100% of the time. In my experience, I can't padlock this vehicle about 95% of the time.

Aviar

[MicroWave]

Two minor bugs in 4.09 QMB:

Side: Axis
Map: Pacific islands
Target:Armor
Error me ssage "Data file corrupt"
Confirmed.
It should actually be the old mission present in 4.08 and 4.09beta. I wonder was it working back then? From what I can see there is a small bug in the mission file in the latest patch (4.09 final).


Side: Axis
Map: Pacific islands
Target: Bridge
No bridge spawn for bombing
It was like that even in earlier patches. There are simply no Bridges on Pacific Islands map. I don't know why it was included like this, but maybe it can stay as a curiosity. ;)

[Aviar]

Another long-time bug:

On the Italy_Online map.....the Genova Airbase. Jet planes will not take off from that base. Neither players nor the AI can start a jet plane engine on that airfield. Prop planes can be started normally.

Aviar

[F19_Klunk]

maybe it has to do with the length of the runway?

[MicroWave]

Yes, I think this issue was explained when Italy map was released.

BTW, I checked Pacific Island Armor attack in QMB on 4.09beta and the mission wasn't working even then.
So the good news is, DT didn't introduce this bug, and another good news is, it will be fixed.

[Aviar]

Yes, I think this issue was explained when Italy map was released.

If you know what the issue is, would you mind explaining what it is? I've never heard an explanation.

Also, to be accurate, I just found out that this particular issue does not affect every jet plane on the runway. Only the LAST plane on the runway has an issue. So, if you place a flight of 4 jets on the Genova runway, only the last jet will have a problem starting it's engine.

Aviar

[jlan5031]

I hate to confess my ignorance, but I can't figure how to open the dorsal hatch for the top gunner. Any ideas?

[jlan5031]

Never mind. I just found the directions. He who can read can rule the world.

[Shrike_UK]

Im having problems in the full mission builder. Apart from placing units of a type and the type not being what i selected, which seems to be erratic, one problem i get EVERY time is a minimizing to desktop every time i try to change the loaded map. It seems IL2 now remembers the last map you had loaded when you launch it, rather than the FM builder being empty on start, so this means that the screen freezes sometimes when trying to load a different map. its odd really, because it will either Minimize to Desktop or i will have to task switch around then back to IL2 to load a map, or it will minimize itself.

Ive no idea whats causing this. Im on Vista32 with Clean Install of IL21946 with 408m and 409m, both downloaded from 1C FTP server.

I found it odd that noone else has mentioned it yet, so i thought i would ask.

[Viking]

4.07 runs OK and updating to 4.08m no problem. Game runs OK both with CD and nocd file.

Updating to 4.09m and game won’t run with or without nocd patch. With CD I get the disk icon for a few seconds and then nothing.

Installed in C:\games\il2\. Tried to run in XP comp mode and as admin to no avail.

Regards

Viking

[zaelu]

4.07 runs OK and updating to 4.08m no problem. Game runs OK both with CD and nocd file.

Updating to 4.09m and game won’t run with or without nocd patch. With CD I get the disk icon for a few seconds and then nothing.

Installed in C:\games\il2\. Tried to run in XP comp mode and as admin to no avail.

Regards

Viking

It happened to others too... It seems to be a problem with missing sfs files after patching and/or missing dll files.

Try reinstall and check archives for problems.

[Viking]

I have reinstalled 5 times and tried with different ideas eg defragged between each patch.
Everything is OK untill I update with 4.09m.

What to do?

Do you have a differnt nocd crack?


Regards

Viking

[zaelu]

unfortunately is not about the no CD

I can't link to helping forums due to some rules...


use google... he's still friendly ;) .

[Viking]

unfortunately is not about the no CD

I can't link to helping forums due to some rules...


use google... he's still friendly ;) .

Sooo... How about a message?

Regards

Viking

EDIT; Problem solved with "new" mg_snd.dll and mg_snd_see.dll files!

[mkubani]

Viking, have you read this whole thread? I believe your problem is linked to the new .dll files that 4.09 comes with. These files don't work with everybody's PC. You need to replace them with older ones.

[Shrike_UK]

Has anyone even tried the Full mission builder? you load a map, then exit, then go back into full mission builder and try to load another map and it minimises to desktop and you have to task switch to desktop then back to the game to get the map to load.

Also, If you then try to load any mission at all after using the FMB the same happens again, and you have to task switch around to desktop then the game to get it running.

This is getting very annoying now keeping doing this every 10 minutes, making missions is now extremely frustrating. 408m never had this problem. worked perfect no bugs whatsoever.

Can anyone tell me if they have tried it or am i the only person with this problem?

[Viking]

Running the track”P51 vs. V1” the V1 now flies 50m on the left side of the P51!
Regards
Viking

[Shrike_UK]

Hi, has anyone tried the full mission builder out yet? im still having the problem, for past few weeks, left a note here, a few times explaining my woes.

Im not playing IL2 anymore at the moment, as i tend to use the full mission builder, build my own missions and fly them online as co-ops. So this means i cant really play it anymore as i used to. So is there anyone out there that could please put me out my misery and tell me if it works for them, so i can work on if i have some incompatibility.

Thanks.
Shrike

[KG26_Alpha]

Has anyone even tried the Full mission builder? you load a map, then exit, then go back into full mission builder and try to load another map and it minimises to desktop and you have to task switch to desktop then back to the game to get the map to load.

Also, If you then try to load any mission at all after using the FMB the same happens again, and you have to task switch around to desktop then the game to get it running.

This is getting very annoying now keeping doing this every 10 minutes, making missions is now extremely frustrating. 408m never had this problem. worked perfect no bugs whatsoever.

Can anyone tell me if they have tried it or am i the only person with this problem?



Hi, has anyone tried the full mission builder out yet? im still having the problem, for past few weeks, left a note here, a few times explaining my woes.

Im not playing IL2 anymore at the moment, as i tend to use the full mission builder, build my own missions and fly them online as co-ops. So this means i cant really play it anymore as i used to. So is there anyone out there that could please put me out my misery and tell me if it works for them, so i can work on if i have some incompatibility.

Thanks.
Shrike

All working fine here v408m & v409m

Make sure you don't have any running processes trying to switch to desktop apart from IL2 of course.

[Eldur]

Just found this one less than 5 minutes ago:

In QMB, ...

... when selecting Crimea and Airfield as a target the new advantage/disadvantage selector creates corrupt mission files.

Still I do not understand how someone tries first to land on the water :-P but the screen is beautiful :-)

I used to "drive" on the water with FW-190 back in Il-2... was a lot of fun http://forums.ubi.com/images/smilies/16x16_smiley-very-happy.gif

The problem (in my config) is not dlls, but files.SFS: mantaining the old one (from dvd), the game starts, while with the newer it crash just after loading.

You're basically running 4.07 then... but still it's weird.

Out of interest in game BF109G2 at 500Kmh IAS you can obtain 6.8G and maintain it in a descending spiral.

Now where does that fit into the Porked index scale ?

The others are porked. That's why we have P-51 wing shed whiners around. They can take 15+G with EASE! Should be impossible.

Me 109 G-6:
Me109 was almost a dream come true for a pilot. Good controllability, enough speed, excelent rate of climb. The feel of the controls were normal except when flying over 600km/h - some strength was needed then.
- Erkki O. Pakarinen, Finnish fighter pilot, Finnish Air Force trainer. Source: Hannu Valtonen, "Me 109 ja Saksan sotatalous" (Messerschmitt Bf 109 and the German war economy), ISBN 951-95688-7-5.

I remember that there was some Finnish data around that said it was possible to pull out the 109G-6 from a dive at 800km/h IAS with 4G. There were discussions on the concrete 109 elevator in FB. And I did one thing. Fire up UDP speed with a G-Meter in it, dive and pull at 800m - without even trimming (!) I had more than 4G. I think it was somewhere around 5-6. That would mean, that even the 109 elevator is not "concrete enough". Really, the point is that a lot of the planes just have too much elevator authority. Opposed to that is the lack of rudder authority, especially on ground.

The issue 109 pilots obviously face is that the elevator becomes concrete at higher speeds than 350 kph. It's contestable that this speed is very low to have a concrete elevator, but here is not my point. It seems that the speed taken to make concrete elevator was TAS and not IAS as it should be. With this possible mistake, the 109 keeps being relatively manoeuvrable at low to mid altitudes, but becomes uncontrolable at high altitude.

That's definately a point. It should go along the IAS.

A tiny bug to report on one of the new 4.09m QMB missions.

Map: MTO
Target: Airbase
Defence: None

Although Defence is set to 'None', there is still a nasty AAA Tank (Coelian) defending the base. There should be no AAA on the base at all. (There is a seperate AAA setting for that).

Aviar

I see the same problem on Crimea with the Airbase when flying Allied. And there's LOTs of uber Flak. When flying Axis I really have to switch AAA on to have them there. I think this "bug" is as old as Il-2 itself though. But now, when DT alters the QMB mission, it's the perfect moment to address this issue.

[Shrike_UK]

All working fine here v408m & v409m

Make sure you don't have any running processes trying to switch to desktop apart from IL2 of course.

Thanks for responding. I definateley dont have anything else running. No MSN, no Anti-Virus installed, no Firewall even, only processes running are normal Vista 32 OS processes, and ATi Control Center (ccc) and Sound Card control centre. I have UAC off since install of OS. Installing game and patches as administrator and launching as admin.

I dont actually get the same result on 2 different PCs, both Vista 32, but my other one is Dell XPS 1210 Laptop with nVidia graphics card rather than ATi completeley different mobo and Sound card, i do not get the issue at all, so i beleive it has something to do with a hardware incompatibility.

My Desktop PC which it doesnt work on: (all with latest drivers)
nForce 520LE Motherboard socket AM2 using Onboard Realtek HD sound card.
AMD Athlon 64 X2 4200+ (2.2Ghz x 2)
MSI - ATi Radeon X1950 Pro 256mb DDR3, DX9, shader 3.0
Driver version = 9-8_legacy_vista32-64_dd_ccc, 2009.0721.1107.18080
2GB DDR2 Ram
Vista HP 32bit

My Laptop which it does work on:
Dell XPS M1210, Onboard sound.
nVidia GForce GO 7400 256mb
2GB DDR2 Ram
Vista HP 32bit.

It is a replicatable bug, i can produce it by launching IL2, opening FMB, then loading a map, (screen hangs quite some time before map appears), then load a different map, and i get a picture of the desktop but no mouse cursor, when i press 'alt', as if im going to alt-tab, theres a screen flicker as if theres some kind of handing over of a process between game and OS, then i press the tab in combo and i get IL2 tab showing as a black screen, i switch back to the black screen, i get a spinning vista waiting circle for around 1 minute, then the FMB and map i wanted appears. Strange thing is, in 408m, i notice you get a dialogue box quoting 'loading map ___ ' but in 409m this dialogue box no longer appears.
(Its strange, its as if IL2 is looking for some screen in the game that dont exist so instead it just hangs on a screenshot of your desktop).
I have a fresh install of Il246 on both machines, making sure i deleted all traces of previous installs.
In 408m, loading a different map works, no task switching required, and new map loads in under 5 seconds. Also, i used the 409 Beta, and never had any problems with that either.

I have tried using the different sound dll's, as once while switching and the map wasnt loaded even though the game thought it was, i heard some sounds of thunder and lightning, LOL. I've switched back to normall sound dll's now though as it didnt solve the issue. I have also tried different screen resolutions, thinking that might cause it, but no.

[KG26_Alpha]

Cat 7.11 was the best drivers for the x1950 pro

try installing those see if theres any difference

http://www.guru3d.com/newsitem.php?id=6150

[Shrike_UK]

Thanks Alpha, That did work, it does now load maps up.

I've gotta say tho i'm very dissapointed i have to use Old drivers with the 4.09m when the 409 beta and 408m worked perfectly with newer drivers. I only hope that my newer games dont require the newer drivers.

[KG26_Alpha]

It shouldn't really make a difference to the FMB but it could be you had a corrupted driver installation on the later ones.

Also be aware of the threads already running here regarding ATI driver problems.

I used to run x1950's in Crossfire & 7.11 were the most stable for that older card.
:)

[Shrike_UK]

Thanks Alpha, and yes i think my next card wont be an ATi. :)
also i've tried the newest 9.11 driver and its nearly the same as the 9.8, the only difference now is i get a warning window pop up all the time which tells me my power supply is underpowered for my graphics card. which it isnt as i have a 700 watt power supply with a cable plugged into the GPU. What a load of tosh lol. Only does that in oGL games.

[hazyubik]

It's not a bug, it's an elicoidal scale present in the original gunsight

Maraz

The correct spelling is helicoidal. I know, I'm a pedant.

[Dark Sky86]

Something strange is happening on Quick Mission builder on the map Coral Sea (maybe on other water based maps haven't tried). Setting up a mission whereby the player is attacking carriers, Japanese aircraft start not on the carriers but in the sea and subsequently sink, also, flying as part of an SBD wing, soon after dropping bombs on the carrier, AI will perform a strange rolling dive maneuvre, followed by pulling up then idling engine and finally crashlanding in the sea. Happens everytime regardless of any damage being taken or orders to go back to base.

[MicroWave]

Something strange is happening on Quick Mission builder on the map Coral Sea (maybe on other water based maps haven't tried). Setting up a mission whereby the player is attacking carriers, Japanese aircraft start not on the carriers but in the sea and subsequently sink, also, flying as part of an SBD wing, soon after dropping bombs on the carrier, AI will perform a strange rolling dive maneuvre, followed by pulling up then idling engine and finally crashlanding in the sea. Happens everytime regardless of any damage being taken or orders to go back to base.

The first part (planes spawn on water) is known to us, but I don't understand the other part about SBD. Does it happen only in that mission or every time you use SBD?

[Dark Sky86]

The first part (planes spawn on water) is known to us, but I don't understand the other part about SBD. Does it happen only in that mission or every time you use SBD?


It appears to be any plane with bombs as payload attacking the enemy carrier - TBF's, SBD's, F4U etc. As soon as they drop their ordnance they crashland in the water. It only happens on that one map - I tried on maps where the airbase was on land and they did not perform this behaviour. I have tried it with AAA and without but it makes no difference. It is as if their landing co-ordinates are not matching where the ships are.

[MicroWave]

It appears to be any plane with bombs as payload attacking the enemy carrier - TBF's, SBD's, F4U etc. As soon as they drop their ordnance they crashland in the water. It only happens on that one map - I tried on maps where the airbase was on land and they did not perform this behaviour. I have tried it with AAA and without but it makes no difference. It is as if their landing co-ordinates are not matching where the ships are.

Probably it's just a different manifestation of the same bug.
Thanks for reporting this.

[Flanker35M]

S!

Noticed a bug/feature on the Spitfire Mk.IXc with 25lbs boost. The original thread is HERE (http://forum.1cpublishing.eu/showthread.php?t=12103) for details. Thank you :)

[Col. Hogan]

G’day all, I have a graphics glitch that I think is related to 409m official

I have several games on this computer; 409m, UI 1.1.1, UI 1.2, HSFX 4.1 and UP 2.0.

The glitch only shows up in the 409m based games, (UI 1.1.1 / 1.2 Run perfect in maxed out settings).

Specs - XP / AMD Athlon 64 Processor 4000+ 2.41GHz / 2 GB RAM / NVIDIA GeForce 7600 GT.

The problem – Parts of the aircraft are missing, (some panels, canopy framework, parts of the ordnance and gear structure), And depending on my view angle some ships and ground structures pop in and out, their shadow footprint is still visible but the object is gone. When I turn on my nav lights the glitch goes away,(only for my plane though), turn‘em off and the glitch comes back.

Been scouring the forums lookin for a fix and the only rumor I’ve heard is it could be AMD related.

Some samples –

http://lh3.ggpht.com/_qnOz7G98koE/SszKrgOMsAI/AAAAAAAABGc/kRuyRMCHGE8/s800/grab0000.jpg

http://lh6.ggpht.com/_qnOz7G98koE/SszKsabMkxI/AAAAAAAABGg/BdZn8Q35DK8/s800/grab0001.jpg

http://lh6.ggpht.com/_qnOz7G98koE/Ss0AX1X5pDI/AAAAAAAABGk/gl9feAQqz4w/s800/grab0003.jpg

http://lh4.ggpht.com/_qnOz7G98koE/Ss0AYa7xLRI/AAAAAAAABGo/oXG_MFpjPco/s800/grab0004.jpg

Cheers,
Hogan

[csThor]

Please clarify - do these artifacts appear with 4.09m vanilla running? Have you tested that?

To me your post indicates that you run 4.09 + UI and have these issues, but then I'd have to say ask the UI creators for that pack is more likely to have been the culprit there.

[Col. Hogan]

Yes, it happens with 4.09m vanilla. I tried several installs(DVD/408m/409m) and even several different 409m patches from different mirrors.

The thing that has me baffeld is that the two games that are 409b1m( UI 1.1.1 and UI 1.2) have zero issues.

[csThor]

Hmmmm ... I'd place my bet on the dlls that came with 4.09 since many people had issues with those, to. Other than that it might be a problem with the gfx driver ... I have the same card and I encounted strange things with some driver versions, too (nothing Il-2 related though).

[Col. Hogan]

You were correct Thor.

I swapped the dll's from 2008-02-27, problem solved!

Most appreciated

!S!

[FredBelge]

Hello,

I cant turn with rudders keys or joystick, when i push the rudder asiigned key my plane turn a little bit and roll in same time. its impossible to play the game with this problem could you fix that ? the gameplay is destroyed with this problem.

I have a bad english so sory if i cant explain me well...
I am the only one that i know that have this kind of problem all others players can play with the great gameplay of the game.
Thanks you very much to make nice games.

Frédéric

------------------
System Information
------------------
Time of this report: 1/3/2010, 20:49:03
Machine name: PC-DE-FRÉDÉRIC
Operating System: Windows Vista™ Édition Intégrale (6.0, Build 6002) Service Pack 2 (6002.vistasp2_gdr.090803-2339)
Language: French (Regional Setting: French)
System Manufacturer: System manufacturer
System Model: P5K
BIOS: BIOS Date: 10/14/08 13:59:09 Ver: 08.00.12
Processor: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz (2 CPUs), ~3.0GHz
Memory: 4094MB RAM
Page File: 2087MB used, 6310MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
DxDiag Version: 7.00.6002.18107 64bit Unicode
DxDiag Previously: Crashed in system information (stage 4)

------------
DxDiag Notes
------------
Display Tab 1: The file atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,at idxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 1: The file ctaud2k.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 2: The file ctaud2k.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: ATI Radeon HD 4800 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI display adapter (0x9440)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_9440&SUBSYS_05021771&REV_00
Display Memory: 2296 MB
Dedicated Memory: 505 MB
Shared Memory: 1791 MB
Current Mode: 1680 x 1050 (32 bit) (60Hz)
Monitor: SyncMaster 226BW,SyncMaster Magic CX226BW(Digital)
Driver Name: atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,at idxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver Version: 8.14.0010.0716 (English)
DDI Version: 10.1
BGRA Supported: Yes
Driver Attributes: Final Retail
Driver Date/Size: 12/15/2009 00:19:54, 4684288 bytes
WHQL Logo'd: No
WHQL Date Stamp: None
Device Identifier: {D7B71EE2-D700-11CF-0D76-0825A1C2C535}
Vendor ID: 0x1002
Device ID: 0x9440
SubSys ID: 0x05021771
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_A ModeMPEG2_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

-------------
Sound Devices
-------------
Description: Haut-parleurs (Creative SB X-Fi)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1373 (English)
Driver Attributes: Final Retail
WHQL Logo'd: No
Date and Size: 6/4/2009 01:49:08, 684312 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

Description: Sortie SPDIF (Creative SB X-Fi)
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1373 (English)
Driver Attributes: Final Retail
WHQL Logo'd: No
Date and Size: 6/4/2009 01:49:08, 684312 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
Description: Microphone (Logitech Mic (Webcam Pro 9000))
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: USBAUDIO.sys
Driver Version: 6.00.6002.18005 (English)
Driver Attributes: Final Retail
Date and Size: 4/10/2009 21:39:36, 98944 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: Entrée numérique (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1373 (English)
Driver Attributes: Final Retail
Date and Size: 6/4/2009 01:49:08, 684312 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: Auxiliaire (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1373 (English)
Driver Attributes: Final Retail
Date and Size: 6/4/2009 01:49:08, 684312 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: "Ce que vous entendez" (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1373 (English)
Driver Attributes: Final Retail
Date and Size: 6/4/2009 01:49:08, 684312 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

Description: Entrée ligne (Creative SB X-Fi)
Default Sound Capture: No
Default Voice Capture: No
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1373 (English)
Driver Attributes: Final Retail
Date and Size: 6/4/2009 01:49:08, 684312 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

-------------------
DirectInput Devices
-------------------
Device Name: Souris
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Clavier
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Ideazon Merc Stealth MM USB Human Interface Device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1038, 0x0510
FF Driver: n/a

Device Name: Ideazon Merc Stealth MM USB Human Interface Device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1038, 0x0510
FF Driver: n/a

Device Name: Razer Imperator
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1532, 0x0017
FF Driver: n/a

Device Name: Razer Imperator
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1532, 0x0017
FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ Concentrateur USB racine
| Vendor/Product ID: 0x8086, 0x2937
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/10/2009 21:39:54, 273920 bytes
| Driver: usbd.sys, 1/21/2008 03:46:32, 7680 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ Périphérique clavier PIH
| Vendor/Product ID: 0x1038, 0x0510
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/10/2009 21:33:42, 22528 bytes
| Driver: kbdclass.sys, 1/21/2008 03:46:34, 42040 bytes
|
+ Périphérique clavier PIH
| Vendor/Product ID: 0x1532, 0x0017
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/10/2009 21:33:42, 22528 bytes
| Driver: kbdclass.sys, 1/21/2008 03:46:34, 42040 bytes
|
+ Pilote clavier de Terminal Server
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 1/21/2008 03:46:34, 64000 bytes
| Driver: kbdclass.sys, 1/21/2008 03:46:34, 42040 bytes
|
+ Souris HID
| Vendor/Product ID: 0x1532, 0x0017
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouhid.sys, 1/21/2008 03:46:07, 19968 bytes
| Driver: mouclass.sys, 1/21/2008 03:46:07, 39992 bytes
|
+ Pilote souris de Terminal Server
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 4/10/2009 23:15:54, 62440 bytes
| Driver: sermouse.sys, 1/21/2008 03:46:07, 26624 bytes
| Driver: mouclass.sys, 1/21/2008 03:46:07, 39992 bytes

--------------
System Devices
--------------
Name: Intel(R) G33/G31/P35/P31 Express Chipset PCI Express Root Port - 29C1
Device ID: PCI\VEN_8086&DEV_29C1&SUBSYS_82761043&REV_02\3&11583659&0&08
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:32, 178664 bytes

Name: Intel(R) G33/G31/P35/P31 Express Chipset Processor to I/O Controller - 29C0
Device ID: PCI\VEN_8086&DEV_29C0&SUBSYS_82761043&REV_02\3&11583659&0&00
Driver: n/a

Name: Intel(R) ICH9 Family PCI Express Root Port 6 - 294A
Device ID: PCI\VEN_8086&DEV_294A&SUBSYS_82771043&REV_02\3&11583659&0&E5
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:32, 178664 bytes

Name: Intel(R) ICH9 Family PCI Express Root Port 5 - 2948
Device ID: PCI\VEN_8086&DEV_2948&SUBSYS_82771043&REV_02\3&11583659&0&E4
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:32, 178664 bytes

Name: Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
Device ID: PCI\VEN_8086&DEV_2940&SUBSYS_82771043&REV_02\3&11583659&0&E0
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:32, 178664 bytes

Name: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
Device ID: PCI\VEN_8086&DEV_293C&SUBSYS_82771043&REV_02\3&11583659&0&D7
Driver: C:\Windows\system32\drivers\usbehci.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:38, 49664 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 259584 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:54, 273920 bytes
Driver: C:\Windows\system32\hccoin.dll, 6.00.6000.16386 (English), 11/2/2006 12:17:29, 10752 bytes
Driver: C:\Windows\system32\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 03:46:32, 17920 bytes

Name: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
Device ID: PCI\VEN_8086&DEV_293A&SUBSYS_82771043&REV_02\3&11583659&0&EF
Driver: C:\Windows\system32\drivers\usbehci.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:38, 49664 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 259584 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:54, 273920 bytes
Driver: C:\Windows\system32\hccoin.dll, 6.00.6000.16386 (English), 11/2/2006 12:17:29, 10752 bytes
Driver: C:\Windows\system32\hcrstco.dll, 6.00.6001.18000 (English), 1/21/2008 03:46:32, 17920 bytes

Name: Intel(R) ICH9 Family USB Universal Host Controller - 2939
Device ID: PCI\VEN_8086&DEV_2939&SUBSYS_82771043&REV_02\3&11583659&0&D2
Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 03:46:32, 29184 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 259584 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:54, 273920 bytes

Name: Intel(R) ICH9 Family USB Universal Host Controller - 2938
Device ID: PCI\VEN_8086&DEV_2938&SUBSYS_82771043&REV_02\3&11583659&0&D1
Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 03:46:32, 29184 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 259584 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:54, 273920 bytes

Name: Intel(R) ICH9 Family USB Universal Host Controller - 2937
Device ID: PCI\VEN_8086&DEV_2937&SUBSYS_82771043&REV_02\3&11583659&0&D0
Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 03:46:32, 29184 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 259584 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:54, 273920 bytes

Name: Intel(R) ICH9 Family USB Universal Host Controller - 2936
Device ID: PCI\VEN_8086&DEV_2936&SUBSYS_82771043&REV_02\3&11583659&0&EA
Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 03:46:32, 29184 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 259584 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:54, 273920 bytes

Name: Intel(R) ICH9 Family USB Universal Host Controller - 2935
Device ID: PCI\VEN_8086&DEV_2935&SUBSYS_82771043&REV_02\3&11583659&0&E9
Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 03:46:32, 29184 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 259584 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:54, 273920 bytes

Name: Intel(R) ICH9 Family USB Universal Host Controller - 2934
Device ID: PCI\VEN_8086&DEV_2934&SUBSYS_82771043&REV_02\3&11583659&0&E8
Driver: C:\Windows\system32\drivers\usbuhci.sys, 6.00.6001.18000 (English), 1/21/2008 03:46:32, 29184 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 259584 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:54, 273920 bytes

Name: Intel(R) ICH9 Family SMBus Controller - 2930
Device ID: PCI\VEN_8086&DEV_2930&SUBSYS_82771043&REV_02\3&11583659&0&FB
Driver: n/a

Name: Intel(R) ICH9 Family 2 port Serial ATA Storage Controller 2 - 2926
Device ID: PCI\VEN_8086&DEV_2926&SUBSYS_82771043&REV_02\3&11583659&0&FD
Driver: C:\Windows\system32\DRIVERS\pciide.sys, 6.00.6002.18005 (English), 4/10/2009 23:15:00, 14312 bytes
Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:26, 49640 bytes
Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.00.6002.18005 (English), 4/10/2009 23:15:02, 20952 bytes
Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:30, 123368 bytes

Name: Intel(R) ICH9 Family 2 port Serial ATA Storage Controller 1 - 2921
Device ID: PCI\VEN_8086&DEV_2921&SUBSYS_82771043&REV_02\3&11583659&0&FA
Driver: C:\Windows\system32\DRIVERS\pciide.sys, 6.00.6002.18005 (English), 4/10/2009 23:15:00, 14312 bytes
Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:26, 49640 bytes
Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.00.6002.18005 (English), 4/10/2009 23:15:02, 20952 bytes
Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:30, 123368 bytes

Name: Intel(R) ICH9 LPC Interface Controller - 2918
Device ID: PCI\VEN_8086&DEV_2918&SUBSYS_82771043&REV_02\3&11583659&0&F8
Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 6.00.6001.18000 (English), 1/21/2008 03:45:58, 17976 bytes

Name: Intel(R) 82801 PCI Bridge - 244E
Device ID: PCI\VEN_8086&DEV_244E&SUBSYS_82771043&REV_92\3&11583659&0&F0
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6002.18005 (French), 4/10/2009 23:15:32, 178664 bytes

Name: JMicron JMB36X Controller
Device ID: PCI\VEN_197B&DEV_2363&SUBSYS_824F1043&REV_03\4&1AD356C7&0&00E4
Driver: C:\Windows\system32\DRIVERS\jraid.sys, 1.17.0052.0002 (English), 10/29/2009 16:14:38, 115824 bytes

Name: Atheros L1 Gigabit Ethernet 10/100/1000Base-T Controller
Device ID: PCI\VEN_1969&DEV_1048&SUBSYS_82261043&REV_B0\4&18BA0AA4&0&00E5
Driver: C:\Windows\system32\DRIVERS\l160x64.sys, 2.04.0007.0015 (English), 11/12/2008 14:42:00, 57344 bytes

Name: Creative SB X-Fi
Device ID: PCI\VEN_1102&DEV_0005&SUBSYS_00211102&REV_00\4&1542FBD&0&10F0
Driver: C:\Windows\system32\drivers\ctac32k.sys, 6.00.0001.1361 (English), 6/4/2009 01:49:00, 580632 bytes
Driver: C:\Windows\system32\drivers\ctaud2k.sys, 6.00.0001.1373 (English), 6/4/2009 01:49:08, 684312 bytes
Driver: C:\Windows\system32\drivers\ctoss2k.sys, 6.00.0001.1373 (English), 6/4/2009 01:49:18, 179224 bytes
Driver: C:\Windows\system32\drivers\ctprxy2k.sys, 6.00.0001.1373 (English), 6/4/2009 01:49:26, 15896 bytes
Driver: C:\Windows\system32\drivers\ctsfm2k.sys, 6.00.0001.1373 (English), 6/4/2009 01:49:34, 213016 bytes
Driver: C:\Windows\system32\drivers\emupia2k.sys, 6.00.0001.1373 (English), 6/4/2009 01:49:42, 118296 bytes
Driver: C:\Windows\system32\drivers\ha20x2k.sys, 6.00.0001.1373 (English), 6/4/2009 01:49:58, 1561112 bytes
Driver: C:\Windows\system32\drivers\pfmodnt.sys, 3.00.0000.0012 (English), 6/4/2009 01:50:06, 16408 bytes
Driver: C:\Windows\system32\drivers\CTEXFIFX.sys, 6.00.0001.1373 (English), 6/4/2009 01:48:50, 1417240 bytes
Driver: C:\Windows\system32\drivers\CT20XUT.sys, 6.00.0001.1373 (English), 6/4/2009 01:48:30, 202776 bytes
Driver: C:\Windows\system32\drivers\CTHWIUT.sys, 6.00.0001.1373 (English), 6/4/2009 01:48:38, 94744 bytes
Driver: C:\Windows\system32\ctdlang.dat, 6/3/2009 23:40:44, 321512 bytes
Driver: C:\Windows\system32\ctdnlstr.dat, 6/3/2009 23:40:44, 56509 bytes
Driver: C:\Windows\system32\CtxfiRes.dll, 6.00.0001.1373 (English), 6/3/2009 23:55:20, 2560 bytes
Driver: C:\Windows\system32\ctzapxx.ini, 6/4/2009 00:37:06, 54 bytes
Driver: C:\Windows\system32\instwdm.ini, 6/4/2009 00:37:08, 21093 bytes
Driver: C:\Windows\system32\CT1MGM.ROM, 2/25/2000 11:49:34, 1048576 bytes
Driver: C:\Windows\system32\CT2MGM.SF2, 9/22/1999 22:18:38, 2167684 bytes
Driver: C:\Windows\system32\default4.sfm, 1/3/2002 14:44:16, 59 bytes
Driver: C:\Windows\system32\default8.sfm, 1/3/2002 14:44:16, 59 bytes
Driver: C:\Windows\system32\default.sfm, 1/3/2002 14:44:16, 59 bytes
Driver: C:\Windows\Temp\ctpxst32.exe, 1.01.0000.0059 (English), 3/13/2007 09:32:14, 89336 bytes
Driver: C:\Windows\Temp\cttele32.dll, 1.00.0011.0000 (English), 2/4/2008 09:27:58, 102400 bytes
Driver: C:\Windows\Temp\ctpxst64.exe, 1.01.0009.0059 (English), 3/13/2007 09:33:30, 99064 bytes
Driver: C:\Windows\Temp\cttele64.dll, 1.00.0011.0000 (English), 2/4/2008 09:28:10, 107008 bytes
Driver: C:\Windows\system32\regplib.exe, 6/4/2009 00:57:18, 18432 bytes
Driver: C:\Windows\system32\ctpxst64.exe, 1.01.0009.0059 (English), 3/13/2007 09:33:30, 99064 bytes
Driver: C:\Windows\SysWOW64\sfman32.dll, 6.00.0001.1373 (English), 6/3/2009 23:36:36, 10240 bytes
Driver: C:\Windows\SysWOW64\sfms32.dll, 6.00.0001.1373 (English), 6/3/2009 23:36:36, 113152 bytes
Driver: C:\Windows\system32\data\cts20x.dat, 6/3/2009 23:33:10, 2091 bytes
Driver: C:\Windows\system32\data\ctd20x.dat, 6/3/2009 23:33:10, 26919 bytes
Driver: C:\Windows\system32\data\CTP0460W.DAT, 6/3/2009 23:36:00, 275836 bytes
Driver: C:\Windows\system32\data\CTP0466W.DAT, 6/3/2009 23:36:00, 275836 bytes
Driver: C:\Windows\system32\data\CTP0463W.DAT, 6/3/2009 23:36:02, 276282 bytes
Driver: C:\Windows\system32\data\CTP0550W.DAT, 6/3/2009 23:36:02, 276094 bytes
Driver: C:\Windows\system32\data\CTP0678W.DAT, 6/3/2009 23:36:08, 357983 bytes
Driver: C:\Windows\system32\data\CTP0679W.DAT, 6/3/2009 23:36:00, 357983 bytes
Driver: C:\Windows\system32\data\CTP0464W.DAT, 6/3/2009 23:36:02, 275836 bytes
Driver: C:\Windows\system32\data\CTP0468W.DAT, 6/3/2009 23:36:02, 275836 bytes
Driver: C:\Windows\system32\data\CTP0465W.DAT, 6/3/2009 23:36:02, 275836 bytes
Driver: C:\Windows\system32\data\CTP0469W.DAT, 6/3/2009 23:36:02, 275836 bytes
Driver: C:\Windows\system32\data\CTP0730W.DAT, 6/3/2009 23:36:04, 277688 bytes
Driver: C:\Windows\system32\data\CTP0760W.DAT, 6/3/2009 23:36:04, 275257 bytes
Driver: C:\Windows\system32\data\CTP046AW.DAT, 6/3/2009 23:36:04, 275508 bytes
Driver: C:\Windows\system32\data\CTP046BW.DAT, 6/3/2009 23:36:04, 275508 bytes
Driver: C:\Windows\system32\data\CTP046CW.DAT, 6/3/2009 23:36:04, 275508 bytes
Driver: C:\Windows\system32\data\CTP0462W.DAT, 6/3/2009 23:36:06, 275836 bytes
Driver: C:\Windows\system32\data\CTP055AW.DAT, 6/3/2009 23:36:04, 275766 bytes
Driver: C:\Windows\system32\data\CTP073AW.DAT, 6/3/2009 23:36:06, 277688 bytes
Driver: C:\Windows\system32\data\CTXFIGM.RFX, 7/28/2006 09:31:42, 41320 bytes
Driver: C:\Windows\system32\data\CTXFIEM.RFX, 7/28/2006 09:31:40, 41788 bytes
Driver: C:\Windows\system32\data\CTXFICM.RFX, 7/28/2006 09:31:38, 41624 bytes
Driver: C:\Windows\system32\data\CTXFICBM.RFX, 6/23/2005 05:58:50, 7352 bytes
Driver: C:\Windows\system32\SBXFi.ico, 2/7/2005 16:45:22, 766 bytes
Driver: C:\Windows\system32\XFi.bmp, 2/7/2005 16:45:20, 3128 bytes
Driver: C:\Windows\system32\ctcoinst.dll, 3.09.0002.0047 (English), 6/4/2009 01:20:18, 73728 bytes
Driver: C:\Windows\system32\ctdvinst.dll, 0.05.0009.0047 (English), 6/4/2009 01:20:18, 217088 bytes
Driver: C:\Windows\system32\UDAAPO64.dll, 1.00.0008.0000 (English), 5/12/2009 11:25:32, 651776 bytes
Driver: C:\Windows\system32\UDAPLD64.dll, 1.00.0008.0000 (English), 5/12/2009 11:25:54, 57856 bytes
Driver: C:\Windows\SysWOW64\ctdlang.dat, 6/3/2009 23:40:44, 321512 bytes
Driver: C:\Windows\SysWOW64\ctdnlstr.dat, 6/3/2009 23:40:44, 56509 bytes
Driver: C:\Windows\SysWOW64\CtxfiRes.dll, 6.00.0001.1373 (English), 6/3/2009 23:55:20, 2560 bytes
Driver: C:\Windows\SysWOW64\ctzapxx.ini, 6/4/2009 00:37:06, 54 bytes
Driver: C:\Windows\SysWOW64\instwdm.ini, 6/4/2009 00:37:08, 21093 bytes
Driver: C:\Windows\SysWOW64\CT1MGM.ROM, 2/25/2000 11:49:34, 1048576 bytes
Driver: C:\Windows\SysWOW64\CT2MGM.SF2, 9/22/1999 22:18:38, 2167684 bytes
Driver: C:\Windows\SysWOW64\default4.sfm, 1/3/2002 14:44:16, 59 bytes
Driver: C:\Windows\SysWOW64\default8.sfm, 1/3/2002 14:44:16, 59 bytes
Driver: C:\Windows\SysWOW64\default.sfm, 1/3/2002 14:44:16, 59 bytes
Driver: C:\Windows\SysWOW64\a3d.dll, 80.00.0000.0003 (English), 6/3/2009 23:57:38, 60928 bytes
Driver: C:\Windows\SysWOW64\ac3api.dll, 6.00.0001.1373 (English), 6/3/2009 23:56:36, 48640 bytes
Driver: C:\Windows\SysWOW64\eaxac3.dll, 1.01.0002.0000 (English), 7/11/2001 09:51:00, 77824 bytes
Driver: C:\Windows\SysWOW64\ctosuser.dll, 6.00.0001.1373 (English), 6/3/2009 23:36:38, 74752 bytes
Driver: C:\Windows\SysWOW64\ctemupia.dll, 6.00.0001.1373 (English), 6/3/2009 23:40:12, 114688 bytes
Driver: C:\Windows\SysWOW64\piaproxy.dll, 6.00.0001.1373 (English), 6/3/2009 23:36:28, 80896 bytes
Driver: C:\Windows\SysWOW64\ctdproxy.dll, 6.00.0001.1373 (English), 6/3/2009 23:37:02, 61952 bytes
Driver: C:\Windows\SysWOW64\devreg.dll, 6.00.0001.1373 (English), 6/3/2009 23:31:56, 36864 bytes
Driver: C:\Windows\SysWOW64\ctasio.dll, 6.00.0001.1373 (English), 6/3/2009 23:37:06, 51712 bytes
Driver: C:\Windows\SysWOW64\ct_oal.dll, 6.00.0001.1373 (English), 6/3/2009 23:37:06, 193024 bytes
Driver: C:\Windows\SysWOW64\oalinst.exe, 2.00.0006.0000 (English), 4/23/2008 05:07:50, 805400 bytes
Driver: C:\Windows\SysWOW64\ctpxst32.exe, 1.01.0000.0059 (English), 3/13/2007 09:32:14, 89336 bytes
Driver: C:\Windows\SysWOW64\AddCat.exe, 0.00.0000.0001 (English), 12/5/2006 13:52:40, 48400 bytes
Driver: C:\Windows\SysWOW64\UDAAPO64.UDA, 5/12/2009 17:46:58, 8886 bytes
Driver: C:\Windows\SysWOW64\CTMLFX64.UDA, 6/2/2008 10:11:28, 5530 bytes
Driver: C:\Windows\SysWOW64\UDAAIM64.exe, 2.47.0000.0000 (English), 3/26/2009 15:10:04, 600211 bytes
Driver: C:\Windows\SysWOW64\AppSetup.exe, 1.00.0018.0005 (English), 5/18/2009 13:34:30, 22691984 bytes
Driver: C:\Windows\SysWOW64\UDAAPO32.dll, 1.00.0008.0000 (English), 5/12/2009 11:24:44, 511488 bytes
Driver: C:\Windows\SysWOW64\CTxfiBtn.dll, 6.00.0001.1373 (English), 6/3/2009 23:55:20, 41472 bytes
Driver: C:\Windows\SysWOW64\CTxfiSpk.dll, 6.00.0001.1373 (English), 6/3/2009 23:55:18, 39424 bytes
Driver: C:\Windows\SysWOW64\Ct20xspi.dll, 6.00.0001.1373 (English), 6/3/2009 23:50:04, 15360 bytes
Driver: C:\Windows\SysWOW64\CTxfispi.exe, 6.00.0001.1373 (English), 6/3/2009 23:49:56, 1213440 bytes
Driver: C:\Windows\SysWOW64\Ctxfihlp.exe, 6.00.0001.1373 (English), 6/3/2009 23:55:16, 25600 bytes
Driver: C:\Windows\SysWOW64\CTxfiReg.exe, 6.00.0001.1373 (English), 6/3/2009 23:50:08, 47104 bytes
Driver: C:\Windows\SysWOW64\enlocstr.exe, 6/3/2009 23:33:04, 7680 bytes
Driver: C:\Windows\SysWOW64\killapps.exe, 1.00.0000.0001 (English), 6/3/2009 23:32:54, 12800 bytes
Driver: C:\Windows\SysWOW64\kill.ini, 5/27/2009 08:49:00, 285 bytes
Driver: C:\Windows\SysWOW64\data\CTXFIGM.RFX, 7/28/2006 09:31:42, 41320 bytes
Driver: C:\Windows\SysWOW64\data\CTXFIEM.RFX, 7/28/2006 09:31:40, 41788 bytes
Driver: C:\Windows\SysWOW64\data\CTXFICM.RFX, 7/28/2006 09:31:38, 41624 bytes
Driver: C:\Windows\SysWOW64\data\CTXFICBM.RFX, 6/23/2005 05:58:50, 7352 bytes
Driver: C:\Windows\system32\CTMLFX64.dll, 1.00.0004.0000 (English), 6/2/2008 08:42:46, 72704 bytes
Driver: C:\Windows\system32\drivers\drmk.sys, 6.00.6001.18000 (English), 1/21/2008 03:45:59, 122368 bytes
Driver: C:\Windows\system32\drivers\portcls.sys, 6.00.6002.18005 (English), 4/10/2009 21:39:40, 218112 bytes
Driver: C:\Windows\system32\WMALFXGFXDSP.dll, 11.00.6001.7000 (English), 1/21/2008 03:45:59, 1391104 bytes
Driver: C:\Windows\system32\SysFxUI.dll, 6.00.6001.18000 (French), 1/21/2008 03:45:59, 376832 bytes

Name: Contrôleur audio haute définition
Device ID: PCI\VEN_1002&DEV_AA30&SUBSYS_AA301771&REV_00\4&21D451D8&0&0108
Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.00.6002.18005 (French), 4/10/2009 21:39:42, 948736 bytes

Name: ATI Radeon HD 4800 Series
Device ID: PCI\VEN_1002&DEV_9440&SUBSYS_05021771&REV_00\4&21D451D8&0&0008
Driver: C:\Windows\system32\DRIVERS\atikmdag.sys, 8.01.0001.0984 (English), 12/15/2009 01:22:00, 6175744 bytes
Driver: C:\Windows\system32\DRIVERS\ati2erec.dll, 1.00.0000.0019 (English), 12/14/2009 23:39:42, 53248 bytes
Driver: C:\Windows\system32\atiumd64.dll, 8.14.0010.0716 (English), 12/15/2009 00:19:54, 4684288 bytes
Driver: C:\Windows\system32\atiumd6a.dll, 8.14.0010.0241 (English), 12/15/2009 00:13:34, 2604032 bytes
Driver: C:\Windows\system32\atitmm64.dll, 6.14.0011.0022 (English), 12/15/2009 00:45:42, 120320 bytes
Driver: C:\Windows\system32\atiicdxx.dat, 10/22/2009 16:59:00, 196565 bytes
Driver: C:\Windows\system32\amdpcom64.dll, 8.14.0010.0023 (English), 12/14/2009 23:55:18, 53248 bytes
Driver: C:\Windows\system32\atimpc64.dll, 8.14.0010.0023 (English), 12/14/2009 23:55:18, 53248 bytes
Driver: C:\Windows\system32\atiadlxx.dll, 6.14.0010.1053 (English), 12/14/2009 23:54:48, 312320 bytes
Driver: C:\Windows\system32\atiumd6a.cap, 12/15/2009 00:11:12, 402016 bytes
Driver: C:\Windows\system32\atimuixx.dll, 6.14.0010.1001 (English), 12/15/2009 00:44:54, 12288 bytes
Driver: C:\Windows\system32\atiesrxx.exe, 6.14.0011.1047 (English), 12/15/2009 00:47:04, 202752 bytes
Driver: C:\Windows\system32\atieclxx.exe, 6.14.0011.1047 (English), 12/15/2009 00:47:40, 446976 bytes
Driver: C:\Windows\system32\atipdl64.dll, 6.14.0010.2561 (English), 12/15/2009 00:45:22, 421376 bytes
Driver: C:\Windows\system32\atiedu64.dll, 6.14.0010.2514 (English), 12/15/2009 00:44:50, 59392 bytes
Driver: C:\Windows\system32\ATIDEMGX.dll, 2.00.3635.33836 (French), 12/15/2009 00:47:52, 446464 bytes
Driver: C:\Windows\system32\atio6axx.dll, 6.14.0010.9239 (English), 12/15/2009 00:30:48, 17624576 bytes
Driver: C:\Windows\system32\aticaldd64.dll, 6.14.0010.0515 (English), 12/14/2009 23:49:48, 4739584 bytes
Driver: C:\Windows\system32\aticalrt64.dll, 6.14.0010.0515 (English), 12/14/2009 23:50:12, 43008 bytes
Driver: C:\Windows\system32\aticalcl64.dll, 6.14.0010.0515 (English), 12/14/2009 23:50:00, 39936 bytes
Driver: C:\Windows\system32\atibtmon.exe, 2.00.0000.0000 (English), 5/11/2009 23:35:28, 118784 bytes
Driver: C:\Windows\system32\atidxx64.dll, 8.17.0010.0247 (English), 12/15/2009 00:34:16, 3664384 bytes
Driver: C:\Windows\SysWOW64\atiumdag.dll, 8.14.0010.0716 (English), 12/15/2009 00:25:40, 3618304 bytes
Driver: C:\Windows\SysWOW64\atiumdva.dll, 8.14.0010.0241 (English), 12/15/2009 00:07:36, 2902016 bytes
Driver: C:\Windows\SysWOW64\amdpcom32.dll, 8.14.0010.0023 (English), 12/14/2009 23:55:12, 52224 bytes
Driver: C:\Windows\SysWOW64\atimpc32.dll, 8.14.0010.0023 (English), 12/14/2009 23:55:12, 52224 bytes
Driver: C:\Windows\SysWOW64\atiadlxy.dll, 6.14.0010.1053 (English), 12/14/2009 23:54:40, 225280 bytes
Driver: C:\Windows\SysWOW64\atiumdva.cap, 12/15/2009 00:07:14, 402016 bytes
Driver: C:\Windows\SysWOW64\atipdlxx.dll, 6.14.0010.2561 (English), 12/15/2009 00:45:14, 356352 bytes
Driver: C:\Windows\SysWOW64\Oemdspif.dll, 6.15.0006.0006 (English), 12/15/2009 00:45:00, 274432 bytes
Driver: C:\Windows\SysWOW64\ati2edxx.dll, 6.14.0010.2514 (English), 12/15/2009 00:44:44, 43520 bytes
Driver: C:\Windows\SysWOW64\atioglxx.dll, 6.14.0010.9239 (English), 12/15/2009 00:13:22, 13487616 bytes
Driver: C:\Windows\SysWOW64\atidxx32.dll, 8.17.0010.0247 (English), 12/15/2009 00:41:58, 3056640 bytes
Driver: C:\Windows\SysWOW64\aticaldd.dll, 6.14.0010.0515 (English), 12/14/2009 23:48:52, 3629056 bytes
Driver: C:\Windows\SysWOW64\aticalrt.dll, 6.14.0010.0515 (English), 12/14/2009 23:50:10, 53248 bytes
Driver: C:\Windows\SysWOW64\aticalcl.dll, 6.14.0010.0515 (English), 12/14/2009 23:49:58, 53248 bytes
Driver: C:\Windows\atiogl.xml, 10/30/2009 18:44:16, 19017 bytes
Driver: C:\Windows\system32\ATIODCLI.exe, 1.00.0000.0001 (English), 2/3/2009 22:52:06, 51200 bytes
Driver: C:\Windows\system32\ATIODE.exe, 1.00.0000.0001 (English), 2/18/2009 19:55:22, 332288 bytes

------------------
DirectShow Filters
------------------

DirectShow Filters:
WMAudio Decoder DMO,0x00800800,1,1,,
WMAPro over S/PDIF DMO,0x00600800,1,1,,
WMSpeech Decoder DMO,0x00600800,1,1,,
MP3 Decoder DMO,0x00600800,1,1,,
Mpeg4s Decoder DMO,0x00800001,1,1,,
WMV Screen decoder DMO,0x00600800,1,1,,
WMVideo Decoder DMO,0x00800001,1,1,,
Mpeg43 Decoder DMO,0x00800001,1,1,,
Mpeg4 Decoder DMO,0x00800001,1,1,,
Full Screen Renderer,0x00200000,1,0,,6.06.6002.18005
Multiple File Output,0x00200000,2,2,WMM2FILT.dll,
WMT Black Frame Generator,0x00200000,1,1,WMM2FILT.dll,
WMT Import Filter,0x00200000,0,1,WMM2FILT.dll,
DV Muxer,0x00400000,0,0,,6.06.6001.18000
Color Space Converter,0x00400001,1,1,,6.06.6002.18005
WMT Interlacer,0x00200000,1,1,WMM2FILT.dll,
WM ASF Reader,0x00400000,0,0,,11.00.6001.7000
Screen Capture filter,0x00200000,0,1,wmpsrcwp.dll,11.00.6001.7000
AVI Splitter,0x00600000,1,1,,6.06.6002.18005
VGA 16 Color Ditherer,0x00400000,1,1,,6.06.6002.18005
Microsoft MPEG-2 Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,11.00.6001. 7110
AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,6.06.6002.18005
WMT Format Conversion,0x00200000,1,1,WMM2FILT.dll,
9x8Resize,0x00200000,1,1,WMM2FILT.dll,
StreamBufferSink,0x00200000,0,0,sbe.dll,6.06.6001. 18000
WMT Virtual Source,0x00200000,0,1,WMM2FILT.dll,
Microsoft TV Caption Decoder,0x00200001,1,0,MSTVCapn.dll,6.00.6001.1800 0
MJPEG Decompressor,0x00600000,1,1,,6.06.6002.18005
CBVA DMO wrapper filter,0x00200000,1,1,cbva.dll,6.00.6002.18005
MPEG-I Stream Splitter,0x00600000,1,2,,6.06.6002.18005
SAMI (CC) Parser,0x00400000,1,1,,6.06.6002.18005
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.6001.18000
ATI MPEG File Writer,0x00200000,1,0,atimpenc64.dll,10.12.0000.41 214
ATI MPEG Video Decoder,0x005fffff,1,2,atimpenc64.dll,10.12.0000.4 1214
MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,6.06.6002.1800 5
WMT AudioAnalyzer,0x00200000,1,1,WMM2FILT.dll,
Microsoft MPEG-2 Video Encoder,0x00200000,2,0,msmpeg2enc.dll,11.00.6002.1 8005
Stretch Video,0x00200000,1,1,WMM2FILT.dll,
Internal Script Command Renderer,0x00800001,1,0,,6.06.6002.18005
MPEG Audio Decoder,0x03680001,1,1,,6.06.6002.18005
DV Splitter,0x00600000,1,2,,6.06.6001.18000
Video Mixing Renderer 9,0x00200000,1,0,,6.06.6002.18005
Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,11.00.6002.1 8005
Frame Eater,0x00200000,1,1,WMM2FILT.dll,
Allocator Fix,0x00200000,1,1,WMM2FILT.dll,
ATI MPEG Audio Encoder,0x00200000,1,1,atimpenc64.dll,10.12.0000.4 1214
ACM Wrapper,0x00600000,1,1,,6.06.6002.18005
Video Renderer,0x00800001,1,0,,6.06.6002.18005
MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,6.06.6001.18000
Capture ASF Writer,0x00200000,0,0,WMM2FILT.dll,
Line 21 Decoder,0x00600000,1,1,,
Video Port Manager,0x00600000,2,1,,6.06.6002.18005
Video Renderer,0x00400000,1,0,,6.06.6002.18005
Bitmap Generate,0x00200000,1,1,WMM2FILT.dll,
ATI MPEG Video Encoder,0x00200000,1,1,atimpenc64.dll,10.12.0000.4 1214
Proxy Sink,0x00200000,1,0,WMM2FILT.dll,
DivX Decoder Filter,0x00800000,1,1,divxdec.ax,7.00.0000.0031
Proxy Source,0x00200000,0,1,WMM2FILT.dll,
ATI MPEG Multiplexer,0x00200000,2,1,atimpenc64.dll,10.12.00 00.41214
WM ASF Writer,0x00400000,0,0,,11.00.6001.7000
VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,6.00.6000.1638 6
WMT Sample Information Filter,0x00200000,1,1,WMM2FILT.dll,
File writer,0x00200000,1,0,,6.06.6001.18000
ATI Video Scaler Filter,0x00200000,1,1,atimpenc64.dll,10.12.0000.41 214
DVD Navigator,0x00200000,0,3,,6.06.6002.18005
WMT DV Extract,0x00200000,1,1,WMM2FILT.dll,
Overlay Mixer2,0x00200000,1,1,,
Microsoft MPEG-2 Audio Encoder,0x00200000,2,0,msmpeg2enc.dll,11.00.6002.1 8005
WST Pager,0x00800000,1,1,WSTPager.ax,6.06.6001.18000
MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,6.06.6002 .18005
Record Queue,0x00200000,1,1,WMM2FILT.dll,
DV Video Decoder,0x00800000,1,1,,6.06.6001.18000
SampleGrabber,0x00200000,1,1,qedit.dll,6.06.6002.1 8005
Null Renderer,0x00200000,1,0,qedit.dll,6.06.6002.18005
WMT Log Filter,0x00200000,1,1,WMM2FILT.dll,
MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,6.06.6001.18000
Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,11.00.6002.180 05
WMT Virtual Renderer,0x00200000,1,0,WMM2FILT.dll,
StreamBufferSource,0x00200000,0,0,sbe.dll,6.06.600 1.18000
Smart Tee,0x00200000,1,2,,6.06.6001.18000
Overlay Mixer,0x00200000,0,0,,
AVI Decompressor,0x00600000,1,1,,6.06.6002.18005
WMT MuxDeMux Filter,0x00200000,0,0,WMM2FILT.dll,
NetBridge,0x00200000,2,0,netbridge.dll,6.01.6001.1 8000
AVI/WAV File Source,0x00400000,0,2,,6.06.6002.18005
WMT Volume,0x00200000,1,1,WMM2FILT.dll,
Wave Parser,0x00400000,1,1,,6.06.6002.18005
MIDI Parser,0x00400000,1,1,,6.06.6002.18005
Multi-file Parser,0x00400000,1,1,,6.06.6002.18005
File stream renderer,0x00400000,1,1,,6.06.6002.18005
WMT VIH2 Fix,0x00200000,1,1,WMM2FILT.dll,
ATI Video Rotation Filter,0x00200000,1,1,atimpenc64.dll,10.12.0000.41 214
Microsoft MPEG-1/DD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,11.00.6001. 7000
AVI Mux,0x00200000,1,0,,6.06.6001.18000
Line 21 Decoder 2,0x00600002,1,1,,6.06.6002.18005
File Source (Async.),0x00400000,0,1,,6.06.6002.18005
File Source (URL),0x00400000,0,1,,6.06.6002.18005
Media Center Extender Encryption Filter,0x00200000,2,2,Mcx2Filter.dll,6.01.6002.180 05
AudioRecorder WAV Dest,0x00200000,0,0,,6.00.6000.16386
AudioRecorder Wave Form,0x00200000,0,0,,6.00.6000.16386
SoundRecorder Null Renderer,0x00200000,0,0,,6.00.6000.16386
Infinite Pin Tee Filter,0x00200000,1,1,,6.06.6001.18000
WMT Switch Filter,0x00200000,1,1,WMM2FILT.dll,
Enhanced Video Renderer,0x00200000,1,0,evr.dll,6.00.6002.18005
Uncompressed Domain Shot Detection Filter,0x00200000,1,1,WMM2FILT.dll,
BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,6.06.6002.18005
MPEG Video Decoder,0x40000001,1,1,,6.06.6002.18005

Périphériques de répartition Tree/Splitter WDM:
Convertisseur en T/site-à-site,0x00200000,1,1,,6.00.6001.18000

Video Compressors:
WMVideo8 Encoder DMO,0x00600800,1,1,,
WMVideo9 Encoder DMO,0x00600800,1,1,,
MSScreen 9 encoder DMO,0x00600800,1,1,,
DV Video Encoder,0x00200000,0,0,,6.06.6001.18000
MJPEG Compressor,0x00200000,0,0,,6.06.6002.18005

Audio Compressors:
WM Speech Encoder DMO,0x00600800,1,1,,
WMAudio Encoder DMO,0x00600800,1,1,,
ATI MPEG Audio Encoder,0x00200000,1,1,atimpenc64.dll,10.12.0000.4 1214
IMA ADPCM,0x00200000,1,1,,6.06.6002.18005
PCM,0x00200000,1,1,,6.06.6002.18005
Microsoft ADPCM,0x00200000,1,1,,6.06.6002.18005
GSM 6.10,0x00200000,1,1,,6.06.6002.18005
CCITT A-Law,0x00200000,1,1,,6.06.6002.18005
CCITT u-Law,0x00200000,1,1,,6.06.6002.18005
MPEG Layer-3,0x00200000,1,1,,6.06.6002.18005

Audio Capture Sources:
Microphone (Logitech Mic (Webca,0x00200000,0,0,,6.06.6001.18000
"Ce que vous entendez" (Creativ,0x00200000,0,0,,6.06.6001.18000
Auxiliaire (Creative SB X-Fi),0x00200000,0,0,,6.06.6001.18000
Entrée ligne (Creative SB X-Fi),0x00200000,0,0,,6.06.6001.18000
Entrée numérique (Creative SB X,0x00200000,0,0,,6.06.6001.18000

Midi Renderers:
Default MidiOut Device,0x00800000,1,0,,6.06.6002.18005
Microsoft GS Wavetable Synth,0x00200000,1,0,,6.06.6002.18005
SB X-Fi Synth A [EC00],0x00200000,1,0,,6.06.6002.18005
SB X-Fi Synth B [EC00],0x00200000,1,0,,6.06.6002.18005

Périphériques de capture de flux WDM:
,0x00000000,0,0,,
,0x00000000,0,0,,
SB X-Fi Audio [EC00],0x00200000,2,2,,6.00.6001.18000
Logitech Webcam Pro 9000,0x00200000,1,2,,6.00.6001.18000
Logitech Mic (Webcam Pro 9000),0x00200000,1,1,,6.00.6001.18000

Périphériques de répartition de rendu WDM:
ATI HD Audio rear output,0x00200000,1,1,,6.00.6001.18000
SB X-Fi DMusic Synth [EC00],0x00200000,1,1,,6.00.6001.18000
Sortie SPDIF,0x00000000,0,0,,
SB X-Fi Synth A [EC00],0x00200000,1,1,,6.00.6001.18000
SB X-Fi Synth B [EC00],0x00200000,1,1,,6.00.6001.18000
SB X-Fi Audio [EC00],0x00200000,2,2,,6.00.6001.18000

BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.6000.16386
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,6.06.6002.18005

Video Capture Sources:
Logitech Webcam Pro 9000,0x00200000,1,2,,6.00.6001.18000

Multi-Instance Capable VBI Codecs:
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.6001.18000

BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,6.06.6002.18005
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,6.06.6001.18000

BDA CP/CA Filters:
Decrypt/Tag,0x00600000,1,0,EncDec.dll,6.06.6002.18005
Encrypt/Tag,0x00200000,0,0,EncDec.dll,6.06.6002.18005
XDS Codec,0x00200000,0,0,EncDec.dll,6.06.6002.18005

Transformateurs de répartition de communications WDM:
Convertisseur en T/site-à-site,0x00200000,1,1,,6.00.6001.18000

Audio Renderers:
Haut-parleurs (Creative SB X-Fi,0x00200000,1,0,,6.06.6002.18005
Default DirectSound Device,0x00800000,1,0,,6.06.6002.18005
Default WaveOut Device,0x00200000,1,0,,6.06.6002.18005
DirectSound: Haut-parleurs (Creative SB X-Fi),0x00200000,1,0,,6.06.6002.18005
DirectSound: Sortie SPDIF (Creative SB X-Fi),0x00200000,1,0,,6.06.6002.18005
Sortie SPDIF (Creative SB X-Fi),0x00200000,1,0,,6.06.6002.18005

[robtek]

@FredBelge

did i understand right?
when you use the rudder the plane yaws a bit and turns around the longitudal axis?
Well that is how it is in real life when you use only the rudder on a plane.
to execute a turn you should use the ailerons to bank, the elevator to turn and the rudder to hold the ball in the middle (turn indicator).
This is a simulation of real flying and no console/arcade shooter that can be steered right with just 4 buttons.
Look up some material how planes are handled, those could help.
you also could look here http://forums.ubi.com/eve/forums/a/tpc/f/23110283/m/9121094645

[ZaltysZ]

Seafire F.MK.III has a LOD bug - at medium to far distances its model has invisible wings. Only if you get closer, its wings "pop up" and become visible. Very irritating, because it is very easy to misjudge its direction and orientation from far away. Seafire L.MK.III seems not to be affected.

[FredBelge]

Thanks you for your answer and the link.

[robtek]

your welcome

[Romanator21]

LODs in general need a re-work. Many seem to be the wrong size entirely, with Stukas having some of the worst issues.

[Aviar]

I was working with the Blenheim template by Macwan when I noticed a problem with the fin flash on the left side of the plane. The template looks ok but the problem is obvious in-game.

When I looked at the in-game default skin, the problem was also there.

The problem: The blue stripe does not cover the entire intended area. There is a white/gray area (looks like an upside-down triangle) that should be blue. The fin flash on the opposite side looks ok.

I looked on every Blenheim skin I have and it shows the same problem area. It looks like the problem is with the 3d model, as this area cannot be painted.


Bad:

http://img706.imageshack.us/img706/6348/badtail.th.jpg (http://img706.imageshack.us/i/badtail.jpg/)


Good:

http://img689.imageshack.us/img689/9440/goodtail.th.jpg (http://img689.imageshack.us/i/goodtail.jpg/)


Aviar

[Tempest123]

Just noticed this today flying the Hungarian campaign, the pilots oxygen mask floats around the cockpit and occasionally leaves the aircraft only on AI He-111's, this does not happen on a player controlled He-111.

[Snuff_Pidgeon]

Sooo... How about a message?

Regards

Viking

EDIT; Problem solved with "new" mg_snd.dll and mg_snd_see.dll files!

Hi all, ihave new system running windows7 32 bit. 1946 patched up to 4.09 b but cannot run 4.09m can someone please PM these files that Viking quotes.thanks in advance!

[KG26_Alpha]

Hi all, ihave new system running windows7 32 bit. 1946 patched up to 4.09 b but cannot run 4.09m can someone please PM these files that Viking quotes.thanks in advance!

Take the v408m mg_snd.dll and mg_snd_see.dll files and paste them into v409m

Or from here if you have no v408m backup

http://www.mission4today.com/index.php?name=Downloads&c=568

[Snuff_Pidgeon]

Many thanx for the quick reply Alpha, i will give that a go.

[Flanker35M]

S!

Just a FYI for ppl. Catalyst 10.1 drivers do not fix the problem with corrupted/flickering planes and/or effects with IL-2 so stick with 9.10's. Those work. Really hope some luv could be given to ATI users as IL-2 is the only game around I have problems with my ATI :(

[Arrow]

I have a very strange sound problem that I wasn't able to solve for some days of trying everything possible and impossible. I am using soundblaster X-FI extreme as my sound card and win 7 enterprise OS. TO get EAX effects I am using latest creative alchemy and latest sound blaster driver. Everything works quite well appart from a bug that occurs in the following situation:

When I fly with a wingmen in any mission and I turn off my engine I can still hear my engine running, like my engine sound wouldn't turn off. When I hit pause and then unpause only silence remains as it should. I am of course running a clean absolutely unmodded install and I've tried all different sound settings and even older snd.dlls to no help. It doesn't happen without HW acceleration. I don't know if anything can be done about it, and I think that it is a bug in the sound engine.

[ZaltysZ]

I have a very strange sound problem that I wasn't able to solve for some days of trying everything possible and impossible. I am using soundblaster X-FI extreme as my sound card and win 7 enterprise OS. TO get EAX effects I am using latest creative alchemy and latest sound blaster driver. Everything works quite well appart from a bug that occurs in the following situation:

When I fly with a wingmen in any mission and I turn off my engine I can still hear my engine running, like my engine sound wouldn't turn off. When I hit pause and then unpause only silence remains as it should. I am of course running a clean absolutely unmodded install and I've tried all different sound settings and even older snd.dlls to no help. It doesn't happen without HW acceleration. I don't know if anything can be done about it, and I think that it is a bug in the sound engine.

Try "Duration=5" in Alchemy.

[Arrow]

Just tested it with different durations, buffer settings and even the downloaded new alchemy dll from M4T didn't help at all. I send wingman back to base and switch off the engine and the sound is still there.

[MikkOwl]

DESCRIPTION / SYMPTOMS

When using IL-2's native courves or deadband functions for joysticks, IL-2 in-game joystick will move away from true center if physical joystick is centered.

VERSIONS AFFECTED

Observed since at least version 4.08m. Mods or not does not alter outcome.

HARDWARE

WinXP-32 Home Edition (latest service pack). ASUS P5-B Deluxe with up to date drivers. Tested with older and newer drivers, including for USB. Tested with different USB ports and USB drivers, hubs vs no hubs.

TESTED WITH:
Logitech Extreme 3D PRO
Logitech G940
Logitech G25 Racing Wheel (!)
Saitek Quadrant
All devices tested with different versions of their corresponding drivers.

Was present from beginning, no mods. Have reinstalled completely fresh to make sure. Have deleted all config files for user and conf.ini for testing purposes.

TO REPRODUCE


Start IL-2.
Go to Hardware > Input
Change deadband for joystick pitch and roll to something so large it leaves no doubts (50% for example).
Move joystick around and observe the red input and green output squares in the monitor on the same screen. Move around some ways from center, and then center repeatedly, slowly and quickly, especially near and at center.

The red is where the user's joystick is, the green is how it is moved in IL-2 after being adjusted/filtered by IL-2. When moving it around the center, the green square is centered (since deadband means there should be no reaction at all in IL-2). But when centering the red square (actual joystick), the green moves approximately one pixel up and to the left away from center. Moving away from center, makes the IL-2 adjusted/filtered green square move INTO center again (where it should have been all along).

You may enter a cockpit on the ground and zoom in on the stick in the cockpit, and repeat the same movements. With a big deadband, the stick should not move at all when moving the stick around, only remained static in center. But it moves slightly (very little) to the left, and forward, when joystick is centered. Behaviour also visibly seen with rudder pedals and levers (if they use courves or deadband).

If using a normal no deadband & sensitivity courve (going from 5, 10, 15, 25 etc) you can observe this: moving away from center slowly, makes the IL-2 adjusted/filtered green square move INTO center first, until a certain point is reached (not far), at which it starts behaving completely correctly. Bug is only when near or at center.

NOTES


Affects every type of controller from various manufacturers.
Affects every axis that is bindable in IL-2 (trims, flaps, rudders).
Device calibration is irellevant. It applies even to axes and IL-2 things that have no center (throttle etc). If the red input square is centered, the adjusted green will move offset from center.
The offset is always to the left, or if the axis is vertical (like pitch) it is upwards.
The offset is seen only when any kind of deadband or less than 100 sensitivity is set at the center (i.e. the leftmost sensitivity slider in the hardware > Input screen). It does not affect the axes already set uniformly by default to be flat (like flaps, trims, prop pitch, throttles) but they too will display it if deadband or sensitivity is tweaked.
The offset bug is not visible in the third party IL-2 joy utility, but by using that utility, lowering sensitivity or having deadband near the center of any axis bound to anything (like flaps) can show that in game, the bug really does affect every single axis.
The only way to not experience this self-moving offset is to set the sensitivity to 100, deadband to 0 and use external programs to try to tweak in a joystick/device courve, such as dxtweak2 or the Logitech Profiler.
Reported by two additional individuals (lacking detail to verify). The rest either do not have the bug or they are incapable of that level of perception (users in forum tend to be unwilling to even test, and instead try to explain that it is just IL-2's realistic torque modeling that we are seeing).

[Rubberchicken]

Hi,

I installed the 4.09 patch and everything seems to work right. There is but one problem. If i'am in a quick mission or flighing an online mission i can't refly after being shot down or after landing. The "escape" button doesn't seems to work. The ony way to leave the game is by ctrl+alt+del.

[AndyJWest]

Hi,

I installed the 4.09 patch and everything seems to work right. There is but one problem. If i'am in a quick mission or flighing an online mission i can't refly after being shot down or after landing. The "escape" button doesn't seems to work. The ony way to leave the game is by ctrl+alt+del.

That's an odd one. I'd check you haven't accidentally configured the Esc key to do something else.

[KG26_Alpha]

In the conf.ini

[HotKey gui]
Escape=activate

[Rubberchicken]

Thanks Alpha, i wrote the lines into the config file and it works. Strange do that the entire line was erased after intalling 4.09m. The chapter [HotKey gui] wasn't even in the file.

[MikkOwl]

DESCRIPTION / SYMPTOMS

When using IL-2's native courves or deadband functions for joysticks, IL-2 in-game joystick will move away from true center if physical joystick is centered.

VERSIONS AFFECTED

Observed since at least version 4.08m. Mods or not does not alter outcome.

HARDWARE

WinXP-32 Home Edition (latest service pack). ASUS P5-B Deluxe with up to date drivers. Tested with older and newer drivers, including for USB. Tested with different USB ports and USB drivers, hubs vs no hubs.

TESTED WITH:
Logitech Extreme 3D PRO
Logitech G940
Logitech G25 Racing Wheel (!)
Saitek Quadrant
All devices tested with different versions of their corresponding drivers.

Was present from beginning, no mods. Have reinstalled completely fresh to make sure. Have deleted all config files for user and conf.ini for testing purposes.

TO REPRODUCE


Start IL-2.
Go to Hardware > Input
Change deadband for joystick pitch and roll to something so large it leaves no doubts (50% for example).
Move joystick around and observe the red input and green output squares in the monitor on the same screen. Move around some ways from center, and then center repeatedly, slowly and quickly, especially near and at center.

The red is where the user's joystick is, the green is how it is moved in IL-2 after being adjusted/filtered by IL-2. When moving it around the center, the green square is centered (since deadband means there should be no reaction at all in IL-2). But when centering the red square (actual joystick), the green moves approximately one pixel up and to the left away from center. Moving away from center, makes the IL-2 adjusted/filtered green square move INTO center again (where it should have been all along).

You may enter a cockpit on the ground and zoom in on the stick in the cockpit, and repeat the same movements. With a big deadband, the stick should not move at all when moving the stick around, only remained static in center. But it moves slightly (very little) to the left, and forward, when joystick is centered. Behaviour also visibly seen with rudder pedals and levers (if they use courves or deadband).

If using a normal no deadband & sensitivity courve (going from 5, 10, 15, 25 etc) you can observe this: moving away from center slowly, makes the IL-2 adjusted/filtered green square move INTO center first, until a certain point is reached (not far), at which it starts behaving completely correctly. Bug is only when near or at center.

NOTES


Affects every type of controller from various manufacturers.
Affects every axis that is bindable in IL-2 (trims, flaps, rudders).
Device calibration is irellevant. It applies even to axes and IL-2 things that have no center (throttle etc). If the red input square is centered, the adjusted green will move offset from center.
The offset is always to the left, or if the axis is vertical (like pitch) it is upwards.
The offset is seen only when any kind of deadband or less than 100 sensitivity is set at the center (i.e. the leftmost sensitivity slider in the hardware > Input screen). It does not affect the axes already set uniformly by default to be flat (like flaps, trims, prop pitch, throttles) but they too will display it if deadband or sensitivity is tweaked.
The offset bug is not visible in the third party IL-2 joy utility, but by using that utility, lowering sensitivity or having deadband near the center of any axis bound to anything (like flaps) can show that in game, the bug really does affect every single axis.
The only way to not experience this self-moving offset is to set the sensitivity to 100, deadband to 0 and use external programs to try to tweak in a joystick/device courve, such as dxtweak2 or the Logitech Profiler.
Reported by two additional individuals (lacking detail to verify). The rest either do not have the bug or they are incapable of that level of perception (users in forum tend to be unwilling to even test, and instead try to explain that it is just IL-2's realistic torque modeling that we are seeing).




After more testing, I've found that it is not as apparent with using only deadband as I suggested using. When using only deadband to test it, it does move offset, but since the stick never returns to true center this is almost impossible to notice when in the cockpit visually.

So if anyone could please try the following method and I would be very happy.

REVISED STEPS TO REPRODUCE BUG

1. Set sensitivity of your roll and pitch in IL-2 to zero for the three leftmost ones, and set deadband to zero for both.

2. Step into the cockpit ON THE GROUND (do not be airborne since it is harder to verify) and zoom in on the control column/stick.

3. Move your joystick very carefully across it's center point, as if barely moving from center at all. What I see is that the column moves slightly to the left (just a bit) and slightly forward whenever the joystick is at true center. When moving away from it, the (cockpit) control column returns to true center.

If you have any external software to change the curves of your stick, set it to lowest sensitivity, as that will make it much easier to hit the centermost positions of the stick.

I just tried this with my Saitek Quadrant with nothing Logitech control-wise connected and the virtual driver bus interface disabled in the system settings even, and I observed the above.

I find it very unlikely that IL-2 would be any different on my computer compared to others', and it cannot be a hardware problem since it is only brought on by trying to use the IL-2 curves (Sensitivity) native to that application. The bug itself appears when a control input is at true center, which implies that there could be a coding mistake where the curve sensitivity processing is turned off if the controller is centered, as 'there is no need for it', and it re-engages as soon as the controller leaves center. But for some reason what is considered 'center' for the processed input is slightly offset, perhaps the exact same distance that is required for the controller to move before the curve processing is re-enabled again.

[Mysticpuma]

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

I think it has to be the most off-putting bug I've ever seen :(

Is it possible to fix this (I understand) very long-standing bug?

Cheers, MP


(Enhanced version so the effect can be seen obviously)

[FC99]

I think it has to be the most off-putting bug I've ever seen :(

Is it possible to fix this (I understand) very long-standing bug?

Simple to fix, IIRC some other planes have similar bugs.

FC

[Mysticpuma]

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

Brilliant, I hope it can be in 4.10, that would be great. I think the P-38 also suffers from this too?

Good luck, and cheers TD/ FC99 for the quick reply.

MP

[MikkOwl]

Update on the off-center controller bug:

Another user has verified the bug and recorded a video showing it in action. See a few posts down here:

http://forum.1cpublishing.eu/showthread.php?p=146603

[Mysticpuma]

The video below details a few of the aircraft. I have since found the B-24 have the same awful contrail bug.

Currently I have found Six aircraft that are affected by the contrail bug (probably more but I'm only into US AC) five of which are shown below.

The video below shows those aircraft, but also finishes with video showing the current position of the mesh hook for most aircraft.

Followed by a clip showing the authentic position of contrails.

I understand that the P-38 contrails should appear just above the engines as they exhaust from the top rather than behind.......but if behind is easier it's got to be way better than the ones that are there at the moment?

Basically this would be a long winded piece of work (I would think without having any knowledge of what's involved), but to have the contrail start at the aircraft rather than 20-feet behind would be fantastic!

So, the video below shows the positions of misplaced contrails, followed by a P-51D with the current contrail mesh-hook position. Then I used a Blue Screen technique to create a video that shows how the contrail really should look.

Hopefully someone will be able to to a contrails mod and fix the position of the contrails. Can I have first dibs on all P-47, 51 variants though?

Cheers, MP.

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

[MikkOwl]

The spring centering part of force feedback gives plenty of resistance (as if in flight) when spawning on the ground, and only loosens up when the tail has been lifted from the ground at least once, typically during take-off.

Steam version, G940, 5.08 Profiler version, XP Home Edition -32 bit.

[rollnloop]

Old bugs still present

Mig3 série cockpit (all):

Landing gear light indicator are green when gear up, red when gear down. Should be the contrary, as in all other aircraft.

Yak15 cockpit:

compass is reversed. It works ok only at heading N and S, it reads W when real heading is E, 030 when real is 300, and so on.

I know one can only see it with 6DOF, since otherwise it's hidden by the gunsight, but i like to play with no text on my screen, not even speedbar heading indication.


Another humble request: would it be possible to have subtitles in the lower part of screen, instead of the upper part ? I know most of the time i scan high to look for ennemies, and there subtitles distract me much.

I still need them to know what my finnish, romanian or russian flymates are saying though. In fact EAW worked well for subtitles, with one black line background in the lowest part of screen and white text on it. Do you think DT could give us an option to have this kind of display ?


Thank you very much for what you're all doing at DT, IL2's getting better and better !

[kumpel]

I have just found out that on some aircraft, that I rarely use, I-16 (all versions - old and new) and F4F-3/4 the landing gear is no longer working after the 409m was installed. Everything else works fine.
Does anyone experience the same problem? There may be more planes like that.

[csThor]

In the types you mentioned you need to assign keys to manually raise/lower gear since in them you had to operate a crank to lower/raise a gear.

[kumpel]

Thanks, it's just my inexperience. Works Ok.
For small convenience, it would be nice if gear up/down keys had self repeat feature, so one can get continuous action.

[KG26_Alpha]

You can set up manual gear raise/lower in your RCU file so you dont have to "tap" the keys.

[ZaltysZ]

Thanks, it's just my inexperience. Works Ok.
For small convenience, it would be nice if gear up/down keys had self repeat feature, so one can get continuous action.

They (manual gear keys) are not continues on purpose: to be tiring. ;)

[Wolkenbeisser]

Something that is wrong since very long time:

Smoke on engine-startup with P-51B and C comes only out of the left smoke-stacks. The right ones seem to be "dead" (btw: P-51D works correct).

[kumpel]

Pardon my ignorance, but how does one handle this RCU task?

[dflion]

Need some help? Ver. 4.09

I have just updated to a later driver for my ATI HD4870X2 Graphic card. Everything seemed very good, then I noticed all the 'Furniture Tree lines' (Object 165) missing. The position indicator is showing on the map for the trees, then zooming in on the position -no trees?

Do I have to alter the graphic card settings to get them to show? I apologise if this bug has been reported before.

DFLion

[dflion]

Sorted out the problem myself -

In the config.ini file I changed 'LandShading=3 to LandShading=2' and the trees mysteriously returned?

DFLion

[StealthMonkey23]

After downloading the patch my game would start up, and close before the load screen even got past 5% load, it returns to the desktop as if nothing happened. This happened to me before also when i tried to download plane mods onto it, it doesnt give an error message or anything, it just closes, help please?

[Blackdog_kt]

If you have installed a version of mods that was made before the 4.09 patch, then it's natural that 4.09 won't install correctly on top of that.

The correct process each time is:
clean installation-->official update 4.09--->mods that work with 4.09
clean installation-->official update 4.10--->mods that work with 4.10
...and so on.

You will have to install official updates on a stock, unmodified version each time.

[StealthMonkey23]

If you have installed a version of mods that was made before the 4.09 patch, then it's natural that 4.09 won't install correctly on top of that.

The correct process each time is:
clean installation-->official update 4.09--->mods that work with 4.09
clean installation-->official update 4.10--->mods that work with 4.10
...and so on.

You will have to install official updates on a stock, unmodified version each time.

this was before i got the patch, ive already reinstalled the game and it was completely stock when i put in the patch, its got no mods at all on it now

[MicroWave]

this was before i got the patch, ive already reinstalled the game and it was completely stock when i put in the patch, its got no mods at all on it now

Maybe you forgot to install 4.08 patch?

Installation sequence goes:
Il2 1946 -> 4.08 -> 4.09
or:
Il2 1946 -> 4.08 -> 4.09beta -> 4.09

[KG26_Alpha]

Hi

A long standing bug now from several patches back has been the gliders and towing them.

Online its now not possible to use the tow planes for human pilots:

He111
Bf110

Can this function be restored and if so please add a release button for the glider release cable, also a better AI release point to target a drop/trlease point on the map.

There are many small features about IL2 1946 that make the sim unique and this was one of them. :)

Regards

[=69.GIAP=STENKA]

On 4.09m you cannot map axes in the Hotas section for the fourth USB device. It will detect buttons but not an analog axis.

This was also the case with 4.08.

If I remember right it did work OK with 4.07 but that was so long ago I'm not sure.

[KG26_Alpha]

Hi

A long standing bug now from several patches back has been the gliders and towing them.

Online its now not possible to use the tow planes for human pilots:

He111
Bf110

Can this function be restored and if so please add a release button for the glider release cable, also a better AI release point to target a drop/trlease point on the map.

There are many small features about IL2 1946 that make the sim unique and this was one of them. :)

Regards

Also please fix the FW/Mistel combo.

It no longer works correctly as Human controlled or AI

All you need to do is test it quickly to see the problems.

Thxz

[private_lewis]

I don't know if this is a bug or not, please help.
On the SM.79, the flaps lower automatically (usually under 190km/h). Can someone please tell me if this is a bug or one of the SM.79's 'features'?:confused: Thanks!

[nzwilliam]

I believe it's a feature, not unlike the Ju88's raising automatically above around 250kph.

[AndyJWest]

I don't know if this is a bug or not, please help.
On the SM.79, the flaps lower automatically (usually under 190km/h). Can someone please tell me if this is a bug or one of the SM.79's 'features'?:confused: Thanks!
Nope, it's a feature. From 4.09_Guide.pdf:

Flaps: SM.79 has completely automated flaps/slats. These are automatically and gradually deployed (via hydraulic actuators) when the aircraft IAS falls below 210km/h. Maximum extension is reached when IAS drops to 140km/h. Retraction is also automated, at the same speeds. Ailerons also act as flaps (flaperons) by deflection downwards with the automated mechanism.

I'd suggest downloading this file if you don't have it (from wherever you got the 4.09m patch, or try Mission4Today - http://www.mission4today.com/index.php?name=Downloads&file=details&id=3742). You also need to understand the unusual propeller pitch control. The SM 79 is a nice plane to fly once you get used to its quirks, but it helps to read the manual!

[private_lewis]

I believe it's a feature, not unlike the Ju88's raising automatically above around 250kph.

Nope, it's a feature. From 4.09_Guide.pdf:


I'd suggest downloading this file if you don't have it (from wherever you got the 4.09m patch, or try Mission4Today - http://www.mission4today.com/index.php?name=Downloads&file=details&id=3742). You also need to understand the unusual propeller pitch control. The SM 79 is a nice plane to fly once you get used to its quirks, but it helps to read the manual!

Thanks for the info and support!

[Romanator21]

Also please fix the FW/Mistel combo.

It no longer works correctly as Human controlled or AI

All you need to do is test it quickly to see the problems.

I can vouch for this :) Every time we separate, no matter the speed or attitude, the fighter will spin and collide with the Mistel. It's practically impossible to make a safe separation.

[Viikate]

I can vouch for this :) Every time we separate, no matter the speed or attitude, the fighter will spin and collide with the Mistel. It's practically impossible to make a safe separation.

Strange... I have no problem with Mistel.

[Romanator21]

I did some more testing yesterday, and I was able to make a safe separation. However, I noticed that there is a large tendency for the FW to pitch up, and I noticed that the elevators are deflected fully upward without input from my stick.

The other thing to point out in regards to the Mistel is that the "camera shake" feature seems much stronger in the Mistel than in a normal FW-190. Just try the single missions which give you a normal takeoff scenario to see the effect.

EDIT:

I don't know if this has been reported, but in the QMB under "Coral Sea" when selecting a flight of Zeros in the first "enemy" slot, they spawn in the water, and their usual carrier seems to be missing.

[ovrucm]

I can vouch for this :) Every time we separate, no matter the speed or attitude, the fighter will spin and collide with the Mistel. It's practically impossible to make a safe separation.

I have the same problem. The autopilot does not work for the Mistel combination, it just spins to the ground.

[Tempest123]

Just noticed that is you do a quick mission and its air start with no target selected, your Fokker Dxxi (either version) will have iron sights (sight tube), yet if you select a target or scramble mission your aircraft will have a reflector sight instead.

[AndyJWest]

Just noticed that is you do a quick mission and its air start with no target selected, your Fokker Dxxi (either version) will have iron sights (sight tube), yet if you select a target or scramble mission your aircraft will have a reflector sight instead.

From the 4.09 Guide:
Note: Gun sights randomization

Both Goertz tube sight and Revi 3a were used in Finnish Series 3 Fokkers. About 40% of all planes had
Revi. Therefore a virtual pilot in game has a 40% chance to get Revi when default skin is selected. With user skins (BMP) the sight is Goertz by default but can be certain skins can be bind to Revi with Customization.ini file in skin folder.

[Tempest123]

Thanks for that, I didn't know that but its pretty cool, and the revi is soo much better.

[bugmenot]

Two annoying bugs that have been here for a pretty long time :

When you start airborne with the YP-80 the engine does not work at all and you can't start it. So all you can do is land somewhere on the ground (if there's ground of course).

On the Slovakia Map if you play a Scramble mission for the axis your own AAA starts shooting at you, not very nice. :D

Voilà.

[bugmenot]

Two annoying bugs that have been here for a pretty long time :

When you start airborne with the YP-80 the engine does not work at all and you can't start it. So all you can do is land somewhere on the ground (if there's ground of course).

On the Slovakia Map if you play a Scramble mission for the axis your own AAA starts shooting at you, not very nice. :D

Voilà.

Oh, could it be possible to tweak a little bit the bombers' gunners? I mean they're wayyyy too accurate, it's insane. They can put a bullet in your head at 750 meters. And they shred your plane to pieces in 15 seconds (when you need twice the time to down the bombers)... ^^

[mohaha]

I have problem... Hmm... I installed Il-2 Sturmovik: 1946 (v4.07m) then I installed 4.08m patch and it worked fine but after the 4.09m patch installation the game woudn't start. I can see the process in task manager but it disappears after few seconds. Can you help me? :confused:

PS. Sorry for my bad english...

[WTE_Galway]

Oh, could it be possible to tweak a little bit the bombers' gunners? I mean they're wayyyy too accurate, it's insane. They can put a bullet in your head at 750 meters. And they shred your plane to pieces in 15 seconds (when you need twice the time to down the bombers)... ^^

Only if you choose ACE for the AI gunners. ACE is meant to be insane, just choose Veteran AI for the enemy bomber flights instead.




The following is more an observation than a bug report:

The Dunlop triple brake pressure gauge functions correctly on the Avia B534 but is not enabled on aircraft introduced earlier the J8A. Any chance of getting the gauge functional on older aircraft at some point.

[EJGr.Ost_Caspar]

The Dunlop triple brake pressure gauge functions correctly on the Avia B534 but is not enabled on aircraft introduced earlier the J8A. Any chance of getting the gauge functional on older aircraft at some point.

Well, many gauges on older models doesn't work proper way, but most of them are less important (like a brake air pressure gauge).
It would mean quite some large ammount of work to fix them all.

However, we pay attention to our new creations regarding this aspect, but reworking older once will not happen too soon. Maybe in 2020, when we have no more new ideas. :grin::rolleyes:

EDIT: I have to correct myself... for the new navigation features, it was necessary to rework some of the compass gauges. So we DO rework older gauges, but nethertheless, it was in a bigger context.

[robtek]

So there is still hope that the wrong speed gauge of the g4m gets fixed??
Remember, the scale is meant to indicate knots per hour but the needle indicates km per hour -> the needle is always pegged at full speed in level flight.

[EJGr.Ost_Caspar]

So there is still hope that the wrong speed gauge of the g4m gets fixed??
Remember, the scale is meant to indicate knots per hour but the needle indicates km per hour -> the needle is always pegged at full speed in level flight.

From 4.10-readme-beta:

Betty airspeed gauge unit fix :D

[robtek]

Word!

[Viikate]

The Dunlop triple brake pressure gauge functions correctly on the Avia B534 but is not enabled on aircraft introduced earlier the J8A. Any chance of getting the gauge functional on older aircraft at some point.

From the same readme that Caspar quoted under "Other fixes & improvements:", line 14 out of 62:

"Gladiator/J8A fixes. (revi reticle, spinning wooden prop texture, ski behavior, inclinometer & brake pressure gauge corrections, openable canopy)"

So we've done quite lots of this kind of small fixes & improvements that were requested on different forums.

[WTE_Galway]

From the same readme that Caspar quoted under "Other fixes & improvements:", line 14 out of 62:

"Gladiator/J8A fixes. (revi reticle, spinning wooden prop texture, ski behavior, inclinometer & brake pressure gauge corrections, openable canopy)"

So we've done quite lots of this kind of small fixes & improvements that were requested on different forums.

awesome stuff .. well done :D

[Fafnir_6]

I did some more testing yesterday, and I was able to make a safe separation. However, I noticed that there is a large tendency for the FW to pitch up, and I noticed that the elevators are deflected fully upward without input from my stick.

The other thing to point out in regards to the Mistel is that the "camera shake" feature seems much stronger in the Mistel than in a normal FW-190. Just try the single missions which give you a normal takeoff scenario to see the effect.

EDIT:

I don't know if this has been reported, but in the QMB under "Coral Sea" when selecting a flight of Zeros in the first "enemy" slot, they spawn in the water, and their usual carrier seems to be missing.

I didn't see a response to this anywhere...

The pitching of the Fw190A-8 Mistel is due to the default pitch trim level for that plane on startup. Just reset pitch trim (Shift+Up arrow or down arrow - I can't remember) after separation and the Mistel Fw190A-8 will fly like the stock Fw190A-8. This has been the case since the Mistel was released.

Cheers,

Fafnir_6

[bugmenot]

Only if you choose ACE for the AI gunners. ACE is meant to be insane, just choose Veteran AI for the enemy bomber flights instead.

Hum, I'd like, but no.

I've just tried in Veteran and Average, it's the same. Always those hyper-accurate bombers' gunners.

Maybe not a real "bug" as we understand it, but I do think some tweaks should be made. That's not even funny.

I don't even want to imagine in Ace, that must be pointless and totally surrealistic.

[Aviar]

Two annoying bugs that have been here for a pretty long time :

When you start airborne with the YP-80 the engine does not work at all and you can't start it. So all you can do is land somewhere on the ground (if there's ground of course).

Voilà.

I'm sorry, but I've made and hosted plenty of YP-80 airstart coop missions and I've never once had this problem nor have I heard it mentioned before.

May I respectfully suggest it may be a problem on your end?

Aviar

[Blackdog_kt]

Hum, I'd like, but no.

I've just tried in Veteran and Average, it's the same. Always those hyper-accurate bombers' gunners.

Maybe not a real "bug" as we understand it, but I do think some tweaks should be made. That's not even funny.

I don't even want to imagine in Ace, that must be pointless and totally surrealistic.


The gunners are super-accurate in some cases and totally inaccurate, even downright unrealistic, in others.

The short story is this: if their guns are pointing your way when you make your attack run then prepare to get accurately peppered by their fire, but if you are a bit outside of their direct cone of fire then they just shoot into empty air.

This seems a lot like the way the AI uses fighters too...they can pull of some amazing snapshots and yet, they can't hit you when they're saddled up on your 6 if you make as much as a gentle, low-G turn.

I've spent a lot of time flying QMB scenarios against bombers and i've used pretty much everything, from German cannon armed fighters against B17s to Spitfires against He111s and with varying enemy AI levels.

The thing is, as long as you are pulling a moderate amount of G the gunners will miss most of the time. You can try this on QMB with a flight of 4 AI B17s. Get on their high 6 and dive below them, as you approach them start pulling up behind them. This will either give you a shot at their belly, or a snapshot at their 6 o'clock.
The trick is to never center the stick, but always keep some pressure applied on the controls. So, this is not a tracking shot but just a snapshot, as you are constantly changing your trajectory. This is the trick to the gunners missing, flying your plane in a changing trajectory. It doesn't have to be wild maneuvering, just apply some moderate G (maybe between 2.5-4.5 G?).
This makes the gunners miss more, but also makes it harder for you to aim and score kills. It's well suited against soft bombers or when you are flying a heavily armed plane, for example a Fw190 with Mk108s only needs 2-4 hits on a B-17 to put it out of aciton.

The other attack profile makes it easier to aim both for you and for the enemy gunners, but relies on minimizing your exposure time to them. It involves flying segments of almost-straight lines or slight curves, with the aim of putting you in a position to execute an attack from the bomber's front quarter (not directly head-on, usually you come in from the bomber's 10/2 o'clock).
Fly parallel to the bombers outside their gun range and when they are at your 9 and a half o'clock (or 2 and a half if they are to your right), start turning towards them.
You can increase/decrease your bank and turn rate to keep the bomber's silhouette steady in reference to a fixed point on your aircraft (for example, a bit to the side of a canopy frame), which is effectively putting you in a collision course with it, if you go on like this you will crash into the bomber. The trick is that as you close the distance you make a final correction turn, momentarily increasing your bank and pulling back on the stick and then levelling off.
Now you are no longer on a collision course, you are on a course that will have you flying on one side of the bomber, crossing its frontal quarter and exiting your attack run behind its tail (eg, starting on the bomber's 10 o'clock and exiting on its 4 o'clock). The gunners have an easier time tracking you at this final segment of the attack run because you are levelled off, but closing speeds are high and you won't take a lot of hits. Even better, you are alinged with the target's geometrical plane of motion and the target will move through your gunsight from nose to tail: congratulations, you just raked the bomber from end to end with gunfire!

Most of all, this sets you up for taking advantage of one of the biggest glitches in AI gunners: rotating turrets (like the B17's top turret) tend to get stuck facing the direction of the last attack. So, if you attack from its left frontal quarter and exit to its right rear quarter, the turret will be facing to the bomber's 10 o'clock or so. Since you exited to the bomber's right however, you set up your next attack from its right side. When you attack, the top turret will probably be facing the wrong way and won't be able to rotate in time to track you. By the time they have turned and started firing you'll be exiting your attack run to the opposite quarter, the turret will again get stuck facing opposite from you, so rinse and repeat until you bring him down. That's why a lot of times you see AI bombers shooting tracers wildly into empty sky towards the place you were 2 seconds ago.

Hope it helps. I would upload some tracks but i'm in a bit of a hurry :grin:

[Fafnir_6]

Hum, I'd like, but no.

I've just tried in Veteran and Average, it's the same. Always those hyper-accurate bombers' gunners.

Maybe not a real "bug" as we understand it, but I do think some tweaks should be made. That's not even funny.

I don't even want to imagine in Ace, that must be pointless and totally surrealistic.

Hello,

It sounds like you may not be choosing the most effective attack approach when you are fighting bombers. Closing from dead astern is a poor strategy since you are almost a stationary target for the even the n00best gunners. I'd suggest an approach with a 400-600m height advantage or so (maybe more??). When you are directly above the bomber you wish to kill, roll over and dive straight down on the bomber. Keep your reticle a little bit ahead of the bomber and shoot when the bomber gets big in your sight (you can get good at this with practice). This approach makes it very difficult for the bomber gunners to hit you and you have a ton of speed when you are closest to the bombers, which you can then use to zoom climb back to where you were before your attack. Difficult angles for the gunners, high speed when you are close to the bombers (and most vulnerable) and the ability to hit the wide faces of the wingtips more easily (saves ammo)are all working in your favour this way. I think the AI gunners are not uber.

I hope this helps,

Fafnir_6

[bugmenot]

I'm sorry, but I've made and hosted plenty of YP-80 airstart coop missions and I've never once had this problem nor have I heard it mentioned before.

May I respectfully suggest it may be a problem on your end?

Aviar

I tried again, you're right. It works well. In fact, the problem appears when I lower the engine's power to a certain level. When it's too low, the engine stops and I can't restart it. :-)

I should try in a online game, since the last time I played with the YP-80 on the Internet, I don't remember I faced this issue...

[Aviar]

Engine flame-out on the YP-80 is quite common. However, we can usually restart the engine a good 90% of the time.

Next time, try to increase the throttle setting before you attempt to restart the engine. A higher setting seems to work better.

My personal tip to prevent flame-outs is to set the throttle to 90% and leave it there. Even moving the throttle in very slow increments will sometimes kill the engine...it's very frustrating.

Aviar

[Diga]

hi

i need a help with v4.09
i have il2 platinum collection(russian version 4.07) and want to download the v4.09
which version should i choose from all the patches of 4.09?which russian version?any?

thanks

[SaQSoN]

hi

i need a help with v4.09
i have il2 platinum collection(russian version 4.07) and want to download the v4.09
which version should i choose from all the patches of 4.09?which russian version?any?

thanks

You need to install 4.08 first. Download from here:

http://files.games.1c.ru/perl_harbor/files/patches/408m_ru.exe

Next, install 4.09, download from here:

http://files.games.1c.ru/il2_platinum/files/update/409m_ru.exe

You can ask questions in Russian on the official Russian forum here:

http://forums.games.1c.ru/index.php?type=topics&gid=32

[Diga]

You need to install 4.08 first. Download from here:

http://files.games.1c.ru/perl_harbor/files/patches/408m_ru.exe

Next, install 4.09, download from here:

http://files.games.1c.ru/il2_platinum/files/update/409m_ru.exe

You can ask questions in Russian on the official Russian forum here:

http://forums.games.1c.ru/index.php?type=topics&gid=32




thanks saqson

[koivis]

I found this bug while testing some plane's endurances for air racing. I set up a mission on FMB using the Crimea map and the airfield next to Sevastopol. After testing some short range fighters (like Me 163:rolleyes:) I switched to G4M1-11, and instead of 25% fuel picked only 2%.

Method is simple, take off with full power, start timer, fuel out, stop timer. Then I imported the data to Calc sheet, and got the following figures:

Fuel loadout: 2%
Endurance: 2 min 8 s
Calculated 100% fuel endurance: 1 hour 47 minutes

Which is WAY too low. Yes, I know that you don't get maximum range with full power, but let me explain. The plane's total horsepower is 3060 (2x1530), and if we assume that the specific fuel consumption of the engine is ~0,25 kg/hp/h, the total consumption is 765 kg/h. Now, according to this source (http://www.vectorsite.net/avbetty.html), G4M1-11 had 4900 liter fuel capacity. This means ~3500 kg of fuel, and the with that amount the corresponding endurance is 4 hours 36 minutes. Of course, to get the 6000 km range, you would need to lower the engine settings, and cruise for almost 20 hours!

Now the Betty's range is only ~1/3 of its real range, which means that either the fuel capacity or consumption rate is modelled wrong. If it's too late for 4.10, I'd like to see this fixed in 4.11. I can do some more tests with other planes to see if they're ok.

[robtek]

specific weight of petrol is 1,12 so 4900l equals to approx. 4.375,00 kg.

[koivis]

specific weight of petrol is 1,12 so 4900l equals to approx. 4.375,00 kg.

Are you sure? Anyway, if specific weight of something is 1,12, 4900 liters of that can't weigh 4375 kg...
I used a value of 0,718, this is my source: http://www-static.shell.com/static/aus/downloads/aviation/avgas_100ll_pds.pdf

Also corrected a small error on previous post, wrote 2500 liters when I meant 3500. Doesn't affect the calculation, only a typo when writing the post.

[swiss]

I guess the standard German B4 Fuel is more like Avgas 80/87 so you can use even lower density figures, I think it was 690kg/m3

[robtek]

Ok, i stand corrected, AVGAS 80 has a specific weight of 0,73 - 0,78 kg/l that would indicate a weight of 3285 to 3510 kg.

[Tempest123]

Just a couple of bugs: The Manifold pressure gauge is non-functional in the Macchi 202 (series VII), and when the cockpit instrument lights are put on, the fuel gauge is overlayed by an image of another instrument.

[EJGr.Ost_Caspar]

Just a couple of bugs: The Manifold pressure gauge is non-functional in the Macchi 202 (series VII), and when the cockpit instrument lights are put on, the fuel gauge is overlayed by an image of another instrument.

Acknowledged. Thanks!

[69th_GenSwat]

I know that many don't think highly of the 185, but it seems that something has definitely changed. It does nothing but stall. The MC205 also seems a lot more unstable.

Could it be stick settings? I have always used Crazy Ivans stick settings. Would this, some how, be different in 4.09?

Is your "yet" a polite indicator that recent FM changes have Maddox finger prints on them?:o It is what it is.....it's ok if the FM has been changed, but I would like to know before I go ripping into my stick configurations.

i185: 4 of them made, 2 crashed during testing, the other 2 on standby in hangers. What a mythical plane. Personally I think it is the most over modeled A/C in this game to date... can sustain a Climb on a 44 Fw190 D9 no stalls or wing overs... Can get to 7k meters in no time flat... mater of fact. I have yet to see a max service ceiling for this plane... you could orbit the moon and then some in my experiences with it...

[sermen]

Dear DT I have found two bugs.
1. Cockpit in Yak-3P should be moved backward as it is in Yak-3 VK-107 (all blueprints of Yak-3P have this position of cockpit).
2. (the most important for me :) ) The wings of Yak-3 VK-107 :evil: They should have the same shape and area as Yak-3 wings not Yak-9U!!! It is not a very difficult operation to replace the correct wings from Yak-3 3d model I guess?? The other thing is wrong armament of Yak-3 VK-107 it shoult consist of two B-20 canons.

Why J2M3 maximum speed is 640 km/h at altitude 5000m and J2M5 696 km/h at altitude 9200m? All known data of this types show maximum speed 586-612km/h at altitude 5000m. I'm not sure about J2M5 because it has additional supercharger stage.
I've tested those speeds in Crimea map with 25% of fuel and without ammo.

[Tempest123]

Another small bug, for the Mosquito FB VI, when you are hit and the instrument panel displays bullet holes, the RPM guages and Boost guages become blank (i.e the needles disappear) and do not show damage textures.

[ImpalerNL]

Ive found out that the SM.79 bomber doesnt stall with a full bombload+100%fuel, when doing a minimum radius turn, with max nose up trim.

[Tempest123]

And another one, lol. The Hellcat in RL has dive brakes that use the landing gear as the F4U foes, the gear can be lowered for dive brakes up to 350 kts. Below I think 135 kts or so the gear will lock in place for landing. The Hellcat also had automatic combat flaps.

[ImpalerNL]

Ive found a major bug.
Just kidding.:grin:

Fuel pressure problem for the bf109G10? (Dont know if this applies to the other bf109's too.)
If you look at the fuel pressure gauge, the pressure is almost at minimum, at full power (110%).
If the engine is running very lean at full power, it will destroy the engine in real live.

[ImpalerNL]

I have also tested it in a FW190A8, and in a BF109G6 and its the same bug.
I think all BF109s and all FW190s have this bug.

[Tempest123]

The mark on the airspeed indicator for 400Km/h on the yak-9M, and possibly other yaks too is in the wrong place, the needle passes the 400Km/h mark at 350km/h IAS. The airspeed indicator changes scale by 50% to larger increments at 300km/h, but the needle doesn't take this into effect until 400km/h, causing a 50 km/h difference in IAS. Hope I'm making sense here!

[nzwilliam]

The mark on the airspeed indicator for 400Km/h on the yak-9M, and possibly other yaks too is in the wrong place, the needle passes the 400Km/h mark at 350km/h IAS. The airspeed indicator changes scale by 50% to larger increments at 300km/h, but the needle doesn't take this into effect until 400km/h, causing a 50 km/h difference in IAS. Hope I'm making sense here!

As far as I know IAS (Indicated Air Speed) and TAS (True Air Speed) really only ever overlap values at certain altitude due to air pressure. TAS is calculated based on IAS and air pressure...or something like that, maybe there's other variables.

The cockpit speedometer and speed displayed in the bottom left of the screen (if enabled) are IAS and if you go to no-cockpit view the speed in the HUD is in TAS. If this is the "bug" you're referring to...it's probably not such a bug as it is a feature from reality.

[dduff442]

A good approximation for TAS is to add 2% per 1000ft of altitude to your IAS.

dduff

[Blackdog_kt]

I'm not sure but my understanding is that Tempest is referring to the actual cockpit instruments and not discrepancies between cockpit (IAS) and no-cockpit (TAS) airspeed gauges.

Talking about cockpit gauges that display IAS, it's not rare to see airspeed indicators calibrated in a non-linear scale. So for example, there are tick marks every 20 degrees around the gauge's face for low speeds to provide more accurate readings/better scale resolution where it's possible to encounter a stall, but then the tick marks are placed every 10 degrees for the high speed range in order to save up on the amount of instrument space needed. If the same high resolution scale of 20 degrees per tick mark was used for the high speed range as well, we might need an airspeed gauge that functions in more than 360 degrees (like the ones found in the RAF aircraft for example). Shortening the distance between tick marks in the high speed range means that we can have instruments that display a bigger speed range without having to use a dual inner/outer speed read-out ring like the British indicators, just at the expense of reduced scale resolution at high speeds.

However, this means that the needle also has to move in a non linear way to ensure an accurate change over from one scale to the next.
If the needle's movement keeps linear when the scale of the gauge isn't, then the result is inaccurate readings at high speeds.

I could still be wrong, but that's the way i interpreted Tempest's post.