Knives

MFUZE should be set to Off. And EFUZE to INST.

From the RWR page on the DDI, push the corresponding button where it says HUD.

You are deploying the flaps too early which cause the nose-up. Instead respect the flaps speed. To Half when you are at or below 250kt and to Full when you are at or below 175kt. Setting the flaps to full at 250kt is a bad idea. Unless if your air brake is on and gears are down to ensure that the plane decelerate fast enough to 175kt before the flaps transit to full configuration.

FCS Test bit is bugged. There are several complaints about it. But, remember to Reset the FCS before swithching flaps to auto. Another thing make sure the NWS is disengaged and flaps to Auto before performing the FCS test. There is a couple of points you have to remember: Takeoff trim is very important to ensure the aircraft lift off and climb away from ground. 12 degrees for airfield and 16 to 19 for carriers (depending on how much you are heavy). And all of that, of course with Half flaps. The flaps are necessary for flying under a certain speed so that the wing can generate enough lift. There is a term called flap speed. Each configuration of flaps has a certain speed. I think for F-18 the flaps speed are as follow: Half flaps = 250 knots Full flaps =175 knots If your speed is at or below 175 lower the flap to full, and above it rise it to half. Below 250 lower your flap to half, and above it rise it to auto. The takeoff configuration is considering lifting off with half flaps and gear down. So when you raise the flap the nose will go up and the same happens when raising the gears. So nose up is expected when you are accelerating and lowering your drag. You have to correct for that if you wish by pitching down and re-trim.

Look at SFM_Data section in FA-18C.lua file located in "DCS World OpenBeta\CoreMods\aircraft\FA-18C" folder. This could help you.

I redo the mission but at day time. And everything worked as expected. I wonder if it is a day/night issue and not a loadout problem.

Maybe you can you use templates. Save your group as a template then reuse it in the same mission or future missions.

Hi everyone, I'm wondering if there is an available task to instruct a ground unit to only attack a single enemy unit similar to Air units task 'AttackUnit' ?

Track file is attached. F-18 - Night Attack - GBU.trk

Hi everyone, I noticed whenever the F-18 is loaded with laser guided bombs (GBU-12) and GPS guided bombs (GBU-31) you cannot weapon designate a waypoint (WPDSG). Does anyone has the same issue? I forgot to mention. this effect happens when you start hot from the ramp or cold & dark.

Use Weapon Release button to fire the rockets.

Did you try the F-Pole maneuver? As soon as the missile goes pitbull, brake the lock and it will be easy to find the other guy because most probably he still in the radar gimbal limits. Notching will certainly give the chance for the other guy to be on your six. If you are unable to splash the first guy, then turn and run away. Unless if you have a wingman.

Usually metals are designed to its yield strength and not to its ultimate strength. Because after it reach its yield strength the behavior would change from elastic to plastic. And the failure becomes unpredictable. So when you over G or go beyond the design limits, you will never know which part has yielded. Because there are no physical symptoms. Unless you dismantle every part and measure it and compare it with its original manufacturer drawings. But when you see cracks that means that part has reached its ultimate strength well beyond its yield strength which was designed for. Fatigue is a different story. There are several mathematical models to discribe it and being used for design and maintenance (this is why logs are important to compare the usage with the design mathematical model) . But at the end it is a ghost, you know it is there but you cannot see it or measure it. So in general, the design limit for mechanical parts is 70% to 85% percent of its yield strength (not ultimate) to ensure longevity of the part. However, some parts are designed to yield (for example bolts) but the reasons are different.

A track file would help. But for RALT hold below 5000ft, the Autopilot would try to keep the same set altitude. For example if the terrain below changes or sloped upward for example then the Autopilot would try to follow it and drift upward. (RALT is bad when there are buildings or hills) Try to engage the RALT when you're above flat surfaces like the sea and see what happen.

What Autopilot mode do you select? (Attitude hold, BALT hold, RALT hold) I use both stable and open beta and both are OK.

Me too. Faced the same problem yesterday.

Look here how the "A", "B" and "R" changes depending on height, angle and range. For a high level of certainly, the "A" is calculating range and height by A/G radar. Where "B" is calculating range and height by Barometric Altimeter and INS. And "R" is calculating range and height by Radar Altimeter and INS. So, how that can help? When you see "A" that's mean is most accurate, then "R", the "B" is the least accurate.

A - Most probably is calculating the slant range and hight using the A/G radar. Because for accurate CCIP you need the range too. Further when you are in steep dive the RALT is not accurate due to the location of the radar at the tail.

You can also try this script, it will turn the carrier automatically to face the wind, considering the deck angle, so that you will have zero croswind. https://forums.eagle.ru/showthread.php?t=213662&highlight=carrier+script

Very impressive. Something I've never seen before.

It is a bug and it was already reported. Hopefully, it will be fixed with the next update.

Hello everyone, I'm facing a repeating problem all over the PG map. It seems that AI can not follow on road route. I was thinking that the problem was with the AI unit size. But, I tried several units from infantry, HUMVEE to MBT, all with the same results. I cannot for example make a unit to patrol inside a town. some time they don't turn and sometime they act if there is an invisible wall on the street. a miz file is included. Patrol - Test.miz

LTWS does not have enough energy to guide a missile. It is only showing the history. AIM-120 visual mode and below 10nm, the missile needs only a few seconds to go pitbull.

Matt Wagner channel on YouTube has good tutorials.

Till to date, CV comms are for airfields. As above, this will change when the new CV modul is released.