Svend_Dellepude

Or fading out when moving the cursor over them? Anyway, good idea! +1

Try in SP. If that works then you know it was the server.

Compression.

I have assymetric soft center cams as well.

follow OP's link.

Based on what exactly?

https://en.wikipedia.org/wiki/AGM-45_Shrike

I think you have to stop looking at aerodynamcis from a ground perspective. You get things mixed up.

My guess is still that the issue is somehow related to clouds.

At least the bug should be fixed in an upcoming beta. :)

In the Eagle you should have two missiles left if you get to the merge, where the Viper should have none.

Airspeed will still be airspeed, regardless of which way the wind is coming from in relation to your A/C. Your ground track and ground speed, will however be greatly affected. As many others have said.

The Israeli attack is out of context since it was done in another bird than the one we have in DCS. F-16 was much lighter back then.

https://forums.eagle.ru/showthread.php?t=258640 related i guess.

No! I hate subscription plans on software.

Not yet.

...and you should. That will give other ppl a chance to see what you are talking about. You might just be the only one with this problem. :)

It's not just LTWS?

I think it will be simplified models of the full module planes that we already have.

Then again. Why assume that the JHMCS works in a different way for US than foreign F-16's. I normally don't argue in these matters, but I find the current implementation very weird indeed. Can you please try to explain why the dynamic crosshair should work the way it currently does and how it helps the pilot aim during maneuvering? :joystick:

Please do. It's very confusing to use as it's implemented right now. Rolling the A/C will have the aim cross flying all over the place and it's practically useless.

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.