Svend_Dellepude

Don't understand this either..

Should already be trimmed out, because he just touched down. All there is to do is, Power up and the thing should pretty much leave the runway on it's own.

Always use DX for battle important operations. Pickle, trigger, brakes etc. for T/O, landing, cruise stuff, you can use keys. The problem in this case is that you are using a modifier to operate the brakes (shift, ctrl), so when extending the brakes you are pressing shift, which is also added to SPACE, making the game see L_shift + SPACE, which in this case doesn't do anything. Modifiers are global and are added to any keypress or DX or whatever across all controllers. So pressing shift, ctrl or alt, will change all controllers to a different layer. Hope that was somewhat understandable. There is a 120DX t.a.r.g.e.t file in the Thrustmaster section, that will give you more than enough DX buttons. I suggest you download it.

If you read through the thread you will find that it's not that simple.

https://forums.eagle.ru/showthread.php?t=251893

It was never fixed.

Check the ammo. might be without tracers.

Try to unplug and replug your devices after windows has booted. That did it for me. I now have my ™ stuff connected to a USB hub that I turn on after windows has booted.

MapKey(&Throttle, APUON, DOWN+DX52); MapKeyR(&Throttle, APUON, TEMPO(0, UP+DX52, 500)); Used like this you have a 500 ms delay from trigger release, until the virtual button is released. Use any timing you find suitable. This will prevent flicker from the twitchy trigger. This also means that you have to have a 500 ms pause between trigger presses.

There doesn't seem to be any target discrimination taking place when launching in TWS (or in any mode), so if you launch at two or more tightly spaced targets the missiles might choose to go for just one of them. That kind of defies the purpose of using TWS in the first place. More often than not, I end up using RWS and STT.

Might be the button that is a bit trigger happy. IRL there should be a delay from pickle to release, but that is not implemented yet, so be sure to press the pickle firmly.

Old base, new stickers. At least that's what it looks like.

definitely dimmer than before.

Does it actually create a markpoint?

https://forums.eagle.ru/showthread.php?t=256100 Should be fixed now.

After reading the config file in the F-16 folder, it seems that there is a system that limits braking power above a certain speed if you only brake on one side or apply braking uneven. I found that using 'w' or an axis that apply both brakes at the same time, there doesn't seem to be an issue. Am I correct on this one?

I'm seeing the issue with the left toebrake also. sometimes it workes, sometimes it doesn't.

There seems to be an issue when launching 120's in TWS. I've had them go ballistic right after launch. Target was more than 10NM out.

Doesn't help on the annoying sideways bob.

How are they similar? Asking of curiousity, not as a smartass. :) AFAIK they are very far from each other, both in mindset and in function.

The elevons will instantly jump to a new position during some maneuvers. If you drain the A/C from all speed and then release the stick after being held fully aft, you will see that. So probably the electric servos not tracking the hydromechanical part of the FCS as well as they should, or something like that.

You can also reference the markings on the deck once you are hooked, for future reference. After enough hooks to the catapult you can do it without F2 view.

It's been requested by myself and others countless times over the years, but no response. It came along when the F-15 got it's PFM which is still not really finished. Let's see what happens when MAC comes around.

You do not speak for me!