Svend_Dellepude

did you try repair?

Try if you can replicate using the keyboard. If not you have a triggerhappy joystick.

Old news.

Why?

It's been discussed before. No engine on the market is able to to what ED needs. Thats why they make their own.

I think the farp is elevated this way for it to be able to be placed even if the ground or area is not completely level. Might be a thing from the past though.

Did you try to load missiles on the hornet to see if it made a difference? As far as I can see you are comparing AIM-120B on the Hornet with C on the F-15.

Might be an engine issue if any. If you look at your virtual throttle while operating the real one, it looks pretty much 1:1. With the WH throttle it's a bit sensitive at low rpm, but not really a problem IMHO. I can refuel and land without problems.

Have a look here: https://forums.eagle.ru/showthread.php?t=249484

Went to a concert with these guys yesterday! :punk:

+1 Sparrow on the F-14 is just deadweight. AFAIK ED updated their code while HB didn't. So HB version is the old ED one before the update. IMHO there should be only 1 version of the same missile ingame.

Just saying again. Going above 42k ft gives flicker everytime. I have a suspicion that it has something to do with the upper cloud layer.

Deleted my post because it turned out I was not correct.

Deleted

AFAIK there is no such mode in the viper.

F-16's. I think it was to demonstrate the new flyby sounds.

It's only on/off. Your pic shows it to be enabled. Anyway, that is the one. When you turn it off you will see jitter when the stick is centered.

They are labeled like that because of the engine they feed.

From memory, you need to click below the stick in the overview or mainview if you like. a popup will appear with a tickbox the says something like 'hardware deadzone'. Just untick. Target doesn't have to running since the deadzone filter is turned off in the stick itself.

Turn off autopilot or slow down. Its not able to keep up.

If you use warthog there is a hardware deadzone the can be turned off in target gui.

Could I be right in assuming that the FCS G-limiter is also affected by this?

Long standing and known issue AFAIK. Radar is still a bit buggy. There are threads around about do's and dont's regarding the radar, in this very section. Just use the search function.

Fixed

boot up without your controllers connected, and then connect once your pc is up and running. I have all my thrustmaster stuff connected to a hub that i only turn on once the pc have booted. Otherwise target sometimes get stuck or doesnt remove the physical devices once the virtual one has been created.