Machalot

It is not responsive to axis tuning. Each of the axes behaves like a binary button, and only one can activate at a time.

Corrected. Thanks.

This is the Viggen forum. You might want to post over in the P-52 forum. Make sure your magnetos are turned on, along with the main fuel valve. If it stops in flight, make sure you are not seizing the engine by running at too high manifold pressure for too long and exceeding the limits.

This was specifically mentioned by Cobra from HB as a being fixed in the upcoming patch.

For me, the "view recenter" key is the `~ key. Next to the 1 key of a standard US keyboard.

@IronMike

Should be randomly distributed within the stated accuracy and zero mean. It would be interesting to see if DCS produces random or deterministic nav error.

These are so good. But I can never remember whether I'm supposed to put it in Saved Games or the main installation folder. Can you add that to the post? Thanks!

Seems like it would make sense to no longer pin this as the top thread ***with asterisks*** in their company forum.

I have the same issue with the radar range.

Weapon mode must be ATTACK. Master mode can be NAV, ANF, or (I think) SPA. Trigger UNSAFE. I would recommend setting the switches in that sequence. I have problems sometimes if I UNSAFE first and then switch the master mode.

He told us to tag him.

Common issues are: out of altitude range for launch Bx6 or Bx7 are behind you or out of sequence Bx9 is too close to Bx8. Needs to be at least 30 sec flight time or something. If you move Bx8 you might have to also move Bx9. Bx7 turn angle is too tight.

It might be physically possible depending on the size and power of the elevons and actuators. But we don't know if the FLCS is scheduled to function in that mass configuration, nor if it is notified of (or can detect) the change in mass properties.

Seems like DCS may just stop the aircraft systems sim on ejection.

Make sure to distinguish between two conditions: 1. control inputs remain at last position 2. control surfaces remain at last position In case 1, the FLCS could continue to function and maintain the last commanded G and roll rate. The aircraft might be pulling up or down, rolling left or right, and would just continue on its curved path until it either stalls or crashes. In case 2, the FLCS no longer has a job, and the aircraft will depart and tumble (if it is in a statically unstable configuration, i.e. negative static margin aka "relaxed stability"). I don't know if the F-16 has any fuel/payload configurations that are statically stable (positive static margin) before or after pilot ejection, but in that case (if rolled upright and depending on power setting) the jet would likely enter a phugoid oscillation and gradually spiral to the ground. If the thrust setting is high enough to provide excess power, it could climb for a long time before running out of fuel.

In a crisis shouldn't you use Emergency Jettison?

That's what happens when the actual CCIP is off the bottom of the HUD. The pipper sits on the bottom edge, and it records the target point on the ground when you first press pickle. It doesn't release the weapons until you actually fly to the correct state (range, altitude, speed, flight path angle) that puts the bombs on target.

It could also be related to where the center of pressure falls on the wing or control surfaces. Or it might not be the center of pressure, but the detailed pressure distribution. In transonic flight there can be normal shockwaves in various places, such as on the upper wing surface, and the pressure jumps drastically behind a normal shock. This might cause an unusually high hinge moment on the flaps, for example.

Yes, I would like to use low safety altitude for some missions but it's not possible on most multiplayer servers that leave it at default.

One thing Wags showed in his HARM video was the EOM can fire highly off-azimuth. It was not clear that PB can do this.

Do you have any issues with the trim? Maybe your trim is pushing all the way forward because of a stuck switch.

It also bugs if you are in NAV with the safety open, then momentarily switch to ANF to spot the target, and back to NAV. The CCIP symbols remain on the HUD, but weapon release does nothing.

Could it be that you had not touched the antenna elevation yet, so it was at default, and your control was out of sync? Then when you switched to TWS it scanned your elevation control axis and updated it to match? This assumes you have an axis mapped and it was at the extreme, or something.

You also are at different altitudes, which causes different drag on the bullets.