Official Fulqrum Publishing forum

Official Fulqrum Publishing forum (http://forum.fulqrumpublishing.com/index.php)
-   IL-2 Sturmovik (http://forum.fulqrumpublishing.com/forumdisplay.php?f=98)
-   -   4.09 - Support & Bug Reporting (http://forum.fulqrumpublishing.com/showthread.php?t=10278)

brando 10-09-2009 12:17 AM

Quote:

Originally Posted by JG27_brook (Post 109721)
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 10-09-2009 12:25 AM

Quote:

Originally Posted by JG27_brook (Post 109690)
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 10-09-2009 01:00 AM

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 10-09-2009 12:44 PM

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 10-09-2009 09:06 PM

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 10-11-2009 12:38 AM

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 10-11-2009 10:05 AM

report on SM-79
 
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 10-11-2009 01:27 PM

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

Lazarus 10-11-2009 10:35 PM

Quote:

Originally Posted by csThor (Post 110375)
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 10-12-2009 09:26 AM

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 10-12-2009 05:18 PM

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 10-13-2009 12:13 AM

Quote:

Originally Posted by csThor (Post 110501)
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 10-13-2009 09:04 AM

Quote:

Originally Posted by Aviar (Post 110650)
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 10-13-2009 12:39 PM

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 10-13-2009 12:45 PM

"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 10-13-2009 01:53 PM

Quote:

Originally Posted by Lucas_From_Hell (Post 110844)
"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 10-14-2009 02:49 AM

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

Romanator21 11-05-2009 08:32 AM

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 11-10-2009 04:31 AM

DIEm Win
 
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 11-10-2009 12:13 PM

Bugs in 4.09 QMB
 
1 Attachment(s)
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 11-10-2009 04:46 PM

Quote:

Originally Posted by Bel Air (Post 118584)
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 Hope it helps you clear it up.

B

Aviar 11-10-2009 07:28 PM

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 11-10-2009 09:04 PM

Quote:

Originally Posted by Peteriong (Post 118658)
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).

Quote:

Originally Posted by Peteriong (Post 118658)
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 11-13-2009 08:40 AM

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 11-13-2009 12:44 PM

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

MicroWave 11-13-2009 12:53 PM

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 11-13-2009 05:08 PM

Quote:

Originally Posted by MicroWave (Post 119334)
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 11-21-2009 08:58 PM

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

jlan5031 11-21-2009 09:06 PM

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

Shrike_UK 11-22-2009 11:51 PM

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 11-27-2009 11:45 AM

Cannot run 4.09m in Win7 32bit.
 
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 11-27-2009 12:07 PM

Quote:

Originally Posted by Viking (Post 123169)
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 11-27-2009 08:31 PM

Many times!
 
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 11-27-2009 09:57 PM

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 11-27-2009 10:07 PM

Quote:

Originally Posted by zaelu (Post 123350)
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 11-27-2009 10:08 PM

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 11-28-2009 06:15 PM

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 11-29-2009 07:48 AM

Prob with old dll or all 4.09m?
 
Running the track”P51 vs. V1” the V1 now flies 50m on the left side of the P51!
Regards
Viking

Shrike_UK 12-06-2009 06:47 AM

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 12-06-2009 03:39 PM

Quote:

Originally Posted by Shrike_UK (Post 123593)
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?



Quote:

Originally Posted by Shrike_UK (Post 125677)
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 12-12-2009 08:29 PM

Quote:

Originally Posted by Lucas_From_Hell (Post 107846)
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.

Quote:

Originally Posted by jurinko (Post 108005)
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...very-happy.gif

Quote:

Originally Posted by andrea78 (Post 108407)
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.

Quote:

Originally Posted by IvanK (Post 109031)
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.

Quote:

Originally Posted by JG27_brook (Post 109690)
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.

Quote:

Originally Posted by Oktoberfest (Post 109892)
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.

Quote:

Originally Posted by Aviar (Post 110650)
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 12-15-2009 03:35 AM

Quote:

Originally Posted by KG26_Alpha (Post 125762)
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 12-15-2009 03:56 AM

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 12-15-2009 10:08 AM

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 12-15-2009 12:41 PM

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 12-16-2009 07:42 AM

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 12-17-2009 04:46 AM

Spelling Mistake
 
Quote:

Originally Posted by 6S.Maraz (Post 107693)
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 12-17-2009 01:29 PM

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 12-18-2009 08:23 AM

Quote:

Originally Posted by Dark Sky86 (Post 129247)
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 12-18-2009 09:11 AM

Quote:

Originally Posted by MicroWave (Post 129446)
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 12-18-2009 12:30 PM

Quote:

Originally Posted by Dark Sky86 (Post 129454)
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 12-27-2009 09:03 PM

Spitfire Mk.IXc 25lbs Boost
 
S!

Noticed a bug/feature on the Spitfire Mk.IXc with 25lbs boost. The original thread is HERE for details. Thank you :)

Col. Hogan 12-30-2009 09:21 PM

409m based graphics glitch
 
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/Ss...0/grab0000.jpg

http://lh6.ggpht.com/_qnOz7G98koE/Ss...0/grab0001.jpg

http://lh6.ggpht.com/_qnOz7G98koE/Ss...0/grab0003.jpg

http://lh4.ggpht.com/_qnOz7G98koE/Ss...0/grab0004.jpg

Cheers,
Hogan

csThor 12-31-2009 07:59 AM

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 12-31-2009 04:44 PM

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 12-31-2009 05:31 PM

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 01-03-2010 06:28 PM

You were correct Thor.

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

Most appreciated

!S!

FredBelge 01-03-2010 06:51 PM

Rudder dont work well
 
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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&115 83659&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&1AD 356C7&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&18B A0AA4&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&154 2FBD&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&21D 451D8&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&21D 451D8&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 01-03-2010 08:50 PM

@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/t...3/m/9121094645

ZaltysZ 01-04-2010 06:04 AM

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 01-04-2010 05:44 PM

to Robtek
 
Thanks you for your answer and the link.

robtek 01-04-2010 08:30 PM

your welcome

Romanator21 01-05-2010 12:05 AM

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

Aviar 01-17-2010 02:49 AM

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


Good:

http://img689.imageshack.us/img689/9440/goodtail.th.jpg


Aviar

Tempest123 01-21-2010 08:46 PM

He-111 AI bug
 
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 01-22-2010 04:31 AM

Quote:

Originally Posted by Viking (Post 123352)
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 01-22-2010 07:49 AM

Quote:

Originally Posted by Snuff_Pidgeon (Post 138383)
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.p...ownloads&c=568

Snuff_Pidgeon 01-22-2010 03:04 PM

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

Flanker35M 01-27-2010 06:53 PM

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 02-16-2010 06:15 PM

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 02-16-2010 06:27 PM

Quote:

Originally Posted by Arrow (Post 144000)
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 02-16-2010 06:50 PM

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 02-21-2010 12:45 PM

Joystick centering bug
 
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
  1. Start IL-2.
  2. Go to Hardware > Input
  3. Change deadband for joystick pitch and roll to something so large it leaves no doubts (50% for example).
  4. 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 02-24-2010 10:06 PM

Can't refly
 
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 02-24-2010 10:40 PM

Quote:

Originally Posted by Rubberchicken (Post 146087)
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 02-25-2010 03:22 AM

In the conf.ini

[HotKey gui]
Escape=activate

Rubberchicken 02-25-2010 03:13 PM

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 02-25-2010 10:42 PM

Quote:

Originally Posted by MikkOwl (Post 145265)
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
  1. Start IL-2.
  2. Go to Hardware > Input
  3. Change deadband for joystick pitch and roll to something so large it leaves no doubts (50% for example).
  4. 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 02-26-2010 10:40 PM

Horrible, horrible, long standing Contrail Bug..any fix possible?
 
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 02-26-2010 11:26 PM

Quote:

Originally Posted by Mysticpuma (Post 146520)
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 02-27-2010 07:32 AM

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 02-27-2010 08:14 AM

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 02-28-2010 06:19 PM

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 03-01-2010 06:41 PM

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 03-11-2010 03:04 PM

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 03-19-2010 08:24 AM

Landing gear issue
 
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 03-19-2010 08:33 AM

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 03-19-2010 09:42 AM

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 03-19-2010 09:54 AM

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

ZaltysZ 03-19-2010 09:56 AM

Quote:

Originally Posted by kumpel (Post 150540)
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 03-19-2010 10:36 AM

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 03-19-2010 11:04 AM

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

dflion 03-19-2010 10:15 PM

Object 165 -Furniture Tree Line missing
 
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 03-28-2010 09:53 AM

Object 165 - Furniture Tree Line missing
 
Sorted out the problem myself -

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

DFLion

StealthMonkey23 03-31-2010 10:27 PM

Game crashing on entry
 
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 03-31-2010 11:58 PM

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 04-01-2010 02:02 AM

Quote:

Originally Posted by Blackdog_kt (Post 152635)
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 04-01-2010 11:05 AM

Quote:

Originally Posted by StealthMonkey23 (Post 152648)
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 04-21-2010 08:09 AM

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 04-30-2010 11:18 AM

Fourth USB device
 
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.


All times are GMT. The time now is 03:26 AM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.