ICDO

I am trying to deactivate all my modules (Jesus ED, it it that hard to have a simple deactivation process). So using the individual protect exe files for each module I have received automatic deactivation failed and that I cannot reactivate because deactivation has not been registered on the activation server. Every single module stated the activation server could not be reached but the module is now deactivated and if I reactivate I loose an activation code. Now I have to email their support 17 times with individual activation issues for every single module.

[ame] [/ame]

This is correct, but the razorback Mustangs were mores stable than the bubble canopy ones so maybe this was a factor. Another thing to remember is that the earlier Mustangs had fabric covered elevators that would bulge in a high speed dive and cause porpoising. This was cured with later model D and K versions getting metal elevators but this modification changed/increased the stick and trim forces required to maintain level flight in a high speed dive. Sorry going from memory of America's 100,000.

The idea that poor DCS performance is down to AMD drivers is pure BS to be frank. There are dozens of DX9 games where modern AMD GPUs outperform or match Nvidia cards. The fact is DCS is just poorly optimised. The fact I get identical framerate with my R9 290X at low res and low setting compared to high res 2560x1600 and maximum settings points to game problem, not driver problems. Skyrim DX9 is as fast on R9 290 vs Titan http://www.bit-tech.net/hardware/graphics/2013/11/05/amd-radeon-r9-290-review/7 http://www.tomshardware.com/reviews/radeon-r9-290-review-benchmark,3659-10.html Or how about HD 780 in Witcher 2 DX9. Note how HD780 beats GTX580 or HD6970 comes close to GTX580. No problems with AMD and DX9 there. http://www.hardwarecanucks.com/forum/hardware-canucks-reviews/52165-amd-radeon-hd-7870-hd-7850-review-15.html AMD cards have zero problems with other games on DX9. It's a 100% DCS problem, not AMDs. So this claim that AMD drivers are poor in DX9 compared to Nvidia and this is why DCS runs like crap on AMD are BS. Because every other DX9 benchmark I can find shows no such serious FPS issue. If these bogus claims were correct then every single DX9 game ever released would be far slower on AMD hardware than Nvidia equivalent. Funny that doesn't seem to be the case.

HD 7950 is not a mid range card as it can be overclocked to beyond HD7970 and GTX680 speeds. I am using one and at 1100/1700 overclock DCS runs like crap, even at 1024x768. Huey cold start procedures training mission. All settings max apart from bushes set to 500 and mirrors off. No vsync or FPS caps. 2560x1600 = 30 FPS 1024x768 = 33 FPS 1024x768 with graphics set to low = 36 FPS So even reducing resolution by over 75% and low graphics settings gives only a 20% FPS boost. It the game engine, not the hardware. It was the same scenario on my GTX680, lower settings yielded little or no performance increase.

http://forums.eagle.ru/showpost.php?p=1143206&postcount=3 Have a look at the post above for the answer to your G940 brake problems. I can't help with your missing Su25.

Yes the 3 point landing was the recommended technique for tail draggers. Since you had the stick slightly back when landing the P-51D in a 3 point attitude it meant the tail wheel lock was already. This helped reduce the tendency for the aircraft to yaw or ground loop on the landing run. As the POH suggests the main wheel 2 point landing was only recommended for increased visibility in adverse weather. My own experience in DCS is that 3 pointing is easier than 2 pointing because the plane settles easier and doesn't bounce as much.

I think it is great that sims like DCS P-51D Mustang put us in a position where we have to use the proper procedures. Hopefully they will integrate the proper engine operations as well. Here is the POH for the P-51D. It should help a lot with the operation of your P-51D. :) https://dl.dropbox.com/u/43693296/P-51%20POH.pdf Make sure to "right click" and "save as" to download.

LOL, read what I said, I didn't say not to use flaps on landing, that would be idiotic. I said so many people get the basic procedures wrong, they lower the flaps first, usually long before turning onto finals then they lower the gear. The P-51D POH recommends that the gear should be lowered 1st prior to turning on to finals, then the flaps are lowered when you are turning onto finals or have turned onto finals. Landing flaps on the P-51 cause a lot of drag and if you lower them too far out you WILL need excess power to keep your landing speed manageable. If you are behind the power curve, low and slow with lots of power required just to stay in the air you are doing it wrong. It is not a good state to be in if you need to go around for some reason, or even worse if your engine quits. I only brought this up because many of the images and videos shown of DCS P-51D landings show the full landing flaps long before the gear is lowered.

One of the mistakes I notice many people do is to lower the flaps before the gear. In the P51D and other WWII era warbirds the POH recommends that the gear should be lowered prior to the flaps. The flaps should only be used when you turn in for finals. Gear and flaps cause massive drag and to compensate you need to run much more power. If you are landing with flaps and gear down from too far out then you will need a lot of power to keep speed up. You end up landing with too much power and that brings its own problems in the DCS P51. Just an FYI :)

Sorry for sounding so abrupt but I've heard this as the reason before, but it's wrong. When I hear/read people stating it as a fact it get's the hairs on my arms and the back of my neck up every time. ;) No I don't have the real reason for the whistle. :) Here is a video link to a Miss America flyby. The whistle is there, even though it has the gun ports blanked out. See the image here of the blanked out gun ports, then listen the that beautiful whistle in the video. http://www.airportjournals.com/Photos/0710/X/0710013_9.jpg

The DCS P-51D is a late model block/revision 25 or 30, at a hunch I would say ED chose this late version as it allowed them to include HVARs as part of the weopons aresenal. Most of the skins included with the sim are for ealier revisions and are slightly ahistorical. Most people wouldn't be aware of this minor issue so it's not a problem to be honest (IMHO). The antenna under the nose was a PTO Iwo Jima mod and was PTO only. Lots of very good Iwo P-51D images on this site. http://www.7thfighter.com/albums/index.php/Iwo-Jima-Post-Invasion-Ops/342-FH-3A-42170-70296AC_45th_fs_p_71_mary_beth_67_tom_cat_463433_

I have Windows 7 X640 pro. I would love to test your reversal bug fix please.

I have found out that the missing radio comms menu in eyefinity modes is due to using bezel compensation resolutions. If you use non bezel (standard) resolutions then the list of commands show up. Unfortunately this is not a great work around as we now have to put up with misalligned screens. The main menu problem is becoming very annoying, every time you go into a menu and back out it moves to the wrong position and makes clicking on the menus items pure guesswork. It means you have to constantly keep dragginf your menu window to its proper location. Please ED, fix these problems for eyefinity users. EDIT: I have been trying to get the menu to work as it has become more and more annoying. Tonight I installed DCS Black Shark and the menus worked fine in Eyefinity mode. After a bit of messing and copying of files I discovered a file called lua-gui5.dll in the Blackshark\Bin\Stable folder is the fix. I copied the file over to the \bin\x86\stable folder (overwriting the newer file that already exists there) and now Flaming Cliffs 2 has a full screen menu that works perfectly. :)

I have found out that the missing radio comms menu is due to using bezel compensation resolutions. If you use non bezel (standard) resolutions then the list of commands show up. Unfortunately this is not a great work around as we now have to put up with misalligned screens. The main menu problem is becoming very annoying, every time you go into a menu and back out it moves to the wrong position and makes clicking on the menus items pure guesswork. It means you have to constantly keep dragginf your menu window to its proper location. Please ED, fix these problems for eyefinity users.

Eyefinity Problems I have attached a couple of images of the problems for eyefinity users in FC2. The menu default location is split accross two screens and has to be dragged to a better locations after each mission. Not a big problem but it would be an easy fix for ED to make it default to the centre main screen only. The far more major issue is in relation to the radio comms menu. As you can see from the image attahced the comms dialog box shows up as an empty grey box. This of course renders the comms useless in eyefinity mode. Edit: The images aren't showing. Here is a link to another thread where the images show. http://forums.eagle.ru/showthread.php?t=53226

Bump. If a dev reads this please respond.

I have attached a couple of images of the problems for eyefinity users in FC2. The menu default location is split accross two screens and has to be dragged to a better locations after each mission. Not a big problem but it would be an easy fix for ED to make it default to the centre main screen only. The far more major issue is in relation to the radio comms menu. As you can see from the image attahced the comms dialog box shows up as an empty grey box. This of course renders the comms useless in eyefinity mode. Can we please have a response from a developer show I know not to constantly keep bumping this thread. Thanks :)

I have the exact same problem. I have a eyefinity setup and the radio command dialog box comes up but there is no text. Also the main menue is stretched over two screens and the mouse cursor is not alligned correctly.