BlackRazor

The problem is that the keypresses used to start the engines are only accepted if the throttle is at 0; since you are moving the throttle to start the engines the keypress is ignored and the engine doesn't start. With the Cougar I guess you could add a deadzone and solve the problem because digital axis statements ignore axis shaping but I don't know if the Saitek software allows the same.

It's a bug, already reported it here.

IIRC rearming and refueling requires you to park in specific spots and of course it also requires you to land on allied airfields, neutral airfields will not have these options.

It's called "View briefing on/off" and it is in the General keybinds section; if the key is not already set it's because you have patched the game and you didn't delete your user folder, in that case new keybinds are not added to your existing ones.

Please notice that with the Semiauto setting the CSMS will automatically select the correct ECM and countermeasures programs; all you need to manually do is: - turn on/off the ECM - start/stop dispensing the countermeasures Everything else is handled by the jet computer.

Flaps do have a cockpit switch, it's near the throttle.

I remember that in version 1.0.0.8 the ATC would always deny permission to start engines in the Smerch hunt mission; I reckon that the ATC should only deny permission if the weather conditions are very poor so this should be a bug. As a test you could try to edit the mission and remove all bad weather and all wind, just to see if the ATC gives you permission.

http://forums.eagle.ru/showthread.php?p=1254261#post1254261

IIRC the frequencies are given to you with a scripted radio message while in flight, however I only fly singleplyer so I don't know if those messages work in multiplayer.

Just use the curve settings in the game to change the axis response.

EDIT: doh, I should have read the entire thread.

The procedure seems correct, please provide a track so that we can see the problem.

It has absolutely no effect.

That option was actually a bug and as such it won't come back, so for now you have to choose between looking around and interacting with the cockpit.

Use google ;), I searched "utm to l/l" and the first link I found was this: http://home.hiwaay.net/~taylorc/toolbox/geography/geoutm.html

From the preliminary 1.0.0.9 patch changelog: - Removed broken tree and FARP shadows. :)

To lock on a target the MAV seeker head must be able to "see" the target, i.e. the contrast between the target and the background must be sharp enough. In simple words: the maverick seeker head can lock on targets that are no more than 7-8 miles away, if distance is higher no lock will be achieved.

Nope, there is a setting that prevents the SPI symbology to be occluded by the CCIP gun cross, the gun pipper will however always occlude the SPI symbology.

This has already been discussed thoroughly in the forum, please make a search and read the developers' posts to understand why what you ask is not possible.

The developers have already said that they don't aim to reach the level of fidelity of the DCS series.

Bug, coords should always be two letters followed by an even number of digits (6 to 12); technically the JTAC should also state the zone (37T or 38T in the game).

The tutorial is useful but if you are using the yellow bars for steering you are developing a bad habit, and that will create problems as soon as the developers fix the bug (which is still there btw). Since there is a bug for the moment when you fly an ILS approach you should only use the triangle on the left of the ADI (glideslope) and the HSI (localizer).

If the executable has the /LARGEADDRESSAWARE flag set then it can use up to 4GB of virtual memory; however I don't have the x86 executable installed on my system so I don't know whether this is the case or not. EDIT: also notice that the limit discussed in this thread is about virtual memory, not about physical memory (i.e. RAM memory). They are two completely different concepts that have almost nothing in common.

Hello, I noticed that in the "Serpents Head" mission snapviews are not working correctly, they are completely different than with all other missions. I investigated the miz file that contains the mission and I noticed that apart from the normal files that all missions have there are several files and folders that probably shouldn't be there. Can any tester please check the mission and fix it for the next patch ?

Semi cheat option: 1) Turn towards the threat you want to eliminate 2) With HUD as SOI move the TDC in the general direction of the threat and make the TDC location your SPI 3) Broadcast the SPI to your wingmen with DMS Left Long 4) Ask your wingman to engage Air Defences near your SPI 5) The wingman should broadcast his SPI, which should be dead on the SAM/AAA site 6) Make TAD SOI, hook the wingman's SPI and then make it your SPI 7) Engage the threat you want to eliminate or let your flight take care of it