Svend_Dellepude

It isn't. It's not creeping, just offset as soon as you designate a track.

Agree.

Which is why it should be easy for you to make a track and upload it here to help show the problem. If you care to help that is.

Wind?

Distance does matter if we are talking about the AIM-7F. It doesn't track if launched at a target more than approx 8 NM away. At least in SP. You might be able to launch farther out and when the missile and target get's within range the F will start to track, if within the limits of the seeker head.

It happens when you use the radar elevation. Cycle the AUTO/MAN and the box centers.

Because they might not see the problem on their end so that's why you should provide a track to show what the problem is. Besides, it's easier and faster for 8 ppl to upload a track each than it is for one person to make 8 tracks.

Not sure what you are trying to do, but you should probably chance this: chainedFunction = CHAIN(DOWN+DX1, D(1000), EXEC("onLongEnough=1;")); To this: chainedFunction = CHAIN(DOWN+DX1, TEMPO(0, EXEC("onLongEnough=1;"), 1000)); Since that will prevent the flag from turning on if the button is not held for a full second. With a DELAY the flag will turn on after one second regardless.

I would consider that a bug.

Basically it's a matter of philosophy. 1) If it isn't explicitly stated as being illegal, then it has to be assumed legal. 2) If it isn't explicitly stated as being legal, then it's illegal. No1 seems to be the less bureaucratic one and the one used where I live.

What limits applies to which aircraft then, and how do you know?

So if I program a switch to lower gear, lower flaps and trim pitch for landing, that would also be considered cheating according to @Csgo GE oh yeah? Because the game doesn't have a button that does just that? What about if I program the trigger to launch two missiles with a timed interval when holding the trigger, instead of having to press it twice?

Sorry if i don't understand, but did you check the axis bindings? Pointing devices will default be assigned to pitch and roll.

At least the timer ( if they want to keep it) could be for cooling down and not warming up.

It's a game and dundun has a programmable joystick. Don't really see the issue here.

Here is a track og the aim being too low. Sorry for the length. Gun usage appears almost at the end. AG gun aim low.trk

So you don't think any of the FC3 planes has cms programs IRL?

Right, didn't know. Not a big issue i suppose.

Title says it all. Didn't know if I should post here or in MiG-21 section. Tracks show AI dropping chaff and flares respectively. MiG-21 AI chaff.trk MiG-21 AI flare.trk

What you could do is map the up action to the release of the button with a delay, ie. mapkey( xxx, DOWN+ DXxx) mapkeyR( xxx, CHAIN( 0, D(500), UP+ DXxx)

I got one, and it's a pretty solid investment. Had it for a couple of years now i think, and have had zero issues with it.

Not sure about that, but you certainly shouldn't be able to slew the radar completely away from your designated target. In this track i only used the AZ/EL page to control elevation and scanbox centered on L&S when using NWS/undesignate. TWS elevation.trk

Elevation will go below or above the track if you use undesignate to L&S and you can still use elevation axis to force away from your track. If you press MAN and then AUTO the elevation will now be centered and you no longer have elevation control. It seems the the system doesn't remove the elevation bias that you put in to find the target, but rather adds it on top of the calculated bias needed from horizon.

JDAM autopilot is a bit sketchy atm so make sure you are well within range and not slow. They seem to enter an unrecoverable stall if dropped at low airspeed.

Why not just create a waypoint?