greenmamba

Hello there, Here is what i know, when you use the AIM-120 you have different ranges from which you can shoot the missile. As Madbrood mentionned, there is a lofting cue in your HUD that appears when you are at the maximum Kinematic range of the missile. Therefore to hit the target, you need to loft it to maximise it's range. This is why when you are below Raero there is no lofting cue. At closer ranges (below Raero = maximum range shot for the AIM-120), you don't need to "help" the missile by lofting it to hit your target. A liitle tip, when you are shooting at max range, try to climb as high as you can and while lofting it when you are at high altitude (25 000 - 35 000 FEET ), hit the afterburner during the lofing maneuver. This will add energy to you missile and at high altitude with the thinner air .... all that combined should ensure you hit the target.

I think that it is great to be able to be part of something like an early release. You get to see the project grow, i was interested in an early release because i wanted to go trough the whole process and see the changes along the way. What we have right now is already stunning and there is enough to do already ..... and in multiplayer there is still the possibility to have fun. My two cents.

Thanks buddy

Hello, i am encountering this issue with Nevada theater only.

To everyone, Problem solved, what actually happened is that for some reason DCS decided to map every module i had differently and it was conflicting with my mapping for the F18 sim mode. For some reason also, in settings the play mode was set back to game and not simulation. So i had to delete every mapping dcs made on its own for each module and for general: Now it works fine again. Thanks a lot FragBum :)

will do and report back , thank you very much

hello, thanks for your reply :) Yes i mean VR by 3D world. No in the options menu the controls behave fine. I just tried something, i deleted all the axis assignements mappings, went in VR and once there the controls where again all over the place even if i did not map anything. Rudder controls somehow pitch and yaw ..... thorttle controls rudder .... joystick is controlling what it should .... but the switches don´t respond. i will restart my computer and see what happens.

Ah .... thanks anyway .... i hope to solve this, because it really sucks.

Hello everyone, I am having some serious issues with my HOTAS WARTHOG and my Thrustmaster rudder pedals. I have DCS world instaled for almost 2 weeks now, and i have Nevada theater, persian gulf, and the F18, A10 and AV8 modules. Everything was working fine until i installed the Nevada theater, since then when i go into the 3D world all my axis are going nuts. When i go into settings and into controllers, the mappings are fine, no double or tripple mapping ... all the axis are assigned properly. But in the 3D world nothing works as it should ..... when i assign a switch in the controller settings it shows it has taken in account my mapping, but in the 3D worl it doesn´t work. Does someone have a suggestion ? thank you in adavnce for your help.