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

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

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

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.

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.

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

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.

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.

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

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.

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.
:)

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.

Spelling Mistake
 

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

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?

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.