jeff64

Not certain of my answer, but I think the missile needs to be active before switching target (ie : tracking the target himself). So before switching target, the hud indication needs to be "TTI" (Time to Impact) and not "ACT" (time to active).

from the overhead stack, that brings you abeam the IP.

I support that !

I don't find trapping harder, but scoring is. With alerax lso or airboss, I managed an OK or (OK) about 90% of the time. On about 20 traps on the SC, I only managed to get 1 (OK), and all others were below average ---. I am reassuring myself watching the scores of the AI. Even them are generally getting a below average ! But this below average grading is maybe in relation with the EG sensitivity reported. I noticed too that I receive plenty of EG comments, even if I don't pull back the throttle TL or IW.

hello just bought this shapeways extension, but I must admit : I don't know how or where install it. anyone have done it and can provide some explanations or pictures ? thank you

Yes because in the real aircraft, it is an autocentered axis, like a rudder. As long as you are in the positive range, it will send the input. If you return the axis to the center, the input will stop.

thanks thought this was HILOK poll.

I can not find the official poll you are talking about. Where is it ?

Hello all. Yesterday, on the "Hornet over PG" DCE campaign, I managed to infiltrate myself in enemy territory, avoided SA2 and Hawks, launched my JSOW's from 34.000 fts, just to watch them explode in the reliefs surrounding Lar Airbase. So, how do you do your mission planning to take those iranian rocks into account ? I think the solution is to set an angle for impact in the Jsow Mission page, but how to calculate the best angle to shoot at the max range but be able to clear all the mountains ? Thank you

Unrealistic. A menu in the mission planning to set ALE47 programs and JDAM PP's is planned.

Hello Don't know if it is a bug or normal comportment, but : when having selected from the store page a JDAM (J84 in the instance), the FLIR does not take the slave to the WPDSG function. If I switch from J84 to 82LG, it slaves to the waypoint. If I switch back to the J84, it goes back in "Boresight" function (looking straight forward the aircraft).

the board is not for telling the pilot his aircraft's weight, but for confirming the data given to the deck crew for setting up the catapult is still correct. So you have to know your weight before seeing it on the board.

it only means you have engaged the autopilot in barometric altitude (balt) mode. but if you are not under autopilot at this moment : it is a bug indeed;

slaving the TGP to the WPT is only possible in the Open Beta since the last update.

as far as I understand the logic, the elevation recorded for the target point is the waypoint passage elevation for your flying waypoint in the editor. Ex : gruond elevation is sea level (0 fts). You put a waypoint in the editor. Default altitude is 6.000ish feet, or 2.000 meters. In the hornet, the waypoint altitude is 2.000 meters, and your TGP will search an invisible point at 2.000 mrs in the air, above your target. Correction : In the hornet, select your waypoint. On the HSI, select Data, then UFC. Change Elev point to the Target Altitude. And your TGP will slave correctly.

I was simply not waiting enough time. And it was the same problem for the AP test. Thank you that solved all my problems !!

Hello all Bought the M2K yesterday, and a few things I can't understand. I have read the DCS Manual, Chuck's Guide, and watched a few tutorials on YT or on the www, but there is some things I still don't manage. Starting cold and dark, I startup my aircraft, setup my systems, but : - I can't remove the red "DECOL" (I understand this is an alarm indicating something is not correctly configured for Takeoff). I tried to push and doubletap the "AP STBY" button mapped on my stick, but no effect I tried to move the trim in various position, but no effect All Flaps Slats are in AUTO (Pelles / becs / souris) Canopy is closed and sealed. But as i can't find an exhaustive list of the trigger for the "DECOL" alarm, I don't figure out what is wrong. - after starting up, I can't test my FBW nor AP. If I test the AP (via the switch on the rear left pedestal), I have a master alarm coming on. If I test the FBW, nothing happens. My controls works fine. With all those problems, the aircraft takes off as expected. Anyone have an idea of what I can be doing wrong ?

I concur. Catching a wire is really really easy with the F14. But flying a safe and clean pattern is much hard work.

After an ultimate restart, it seems to work now

Hello there I can't assign any axis in the F14 or map any button. Nothing happens when I move an axis or press a button. If I try on another aircraft BEFORE trying on the F14, it works. As soon as I try on the F14, I can't do anything in the control mapping of any aircraft. If I try to launch a flight AFTER trying to map an axis, it does not load at all (load bar stay empty). If I try to laucnh a flight BEFORE trying to map an axis, it launches, and a few seconds / minutes after, I have a CTD. I disabled my "saved games" open beta folder. A new one has been created, but still the same problem.

Carrier recovery is mostly done ZipLip. So when in the overhead, the lower aircraft check the deck, and when the deck is about to come clear, he left the overhead to enter the recovery pattern.