SU25T locking behaviour in DCS

[malcheus]

Hi,

I'm still new to the DCS set of planes, and there are some small things I cannot seem be able to untangle from the various sources of information and game versions.

 

First off, I'm a true barbarian and as such I play my flight simulators with an xbox360 controller. To my surprise, the program handles the controller really well, and works fine without the need for 3rd party programs like xpadder.

In my current setup, I can look around using the D-pad (which works just like the numpad of the keryboard) and I can slew around the nose-cam/laser designator using the right analog stick.

However, somehow, the plane doesn't seem to care where I point the camera, when I press enter it will lock a seemingly random object (preferably flares). Several presses of the enter key seem to lock the appropriate target, but to me it feels rather unintuitive to precisely slew the camera to my preferred target, only to lose it once I try to lock.

In the tutorials, there is talk of "ground lock" mode etc. I understood that this is from the "flaming cliffs" version, and is no longer accurate; but is there a way to get the locking behaviour to be more dependent on my input?

 

Cheers,

Malcheus

[Fishbreath]

Hi,

I'm still new to the DCS set of planes, and there are some small things I cannot seem be able to untangle from the various sources of information and game versions.

 

First off, I'm a true barbarian and as such I play my flight simulators with an xbox360 controller. To my surprise, the program handles the controller really well, and works fine without the need for 3rd party programs like xpadder.

In my current setup, I can look around using the D-pad (which works just like the numpad of the keryboard) and I can slew around the nose-cam/laser designator using the right analog stick.

However, somehow, the plane doesn't seem to care where I point the camera, when I press enter it will lock a seemingly random object (preferably flares). Several presses of the enter key seem to lock the appropriate target, but to me it feels rather unintuitive to precisely slew the camera to my preferred target, only to lose it once I try to lock.

In the tutorials, there is talk of "ground lock" mode etc. I understood that this is from the "flaming cliffs" version, and is no longer accurate; but is there a way to get the locking behaviour to be more dependent on my input?

 

Cheers,

Malcheus

 

I'm not sure if this is what you mean, but if you press 'lock' while the Shkval/Merkur pod is pointed at the ground, it will ground-stabilize—that is, it'll track a point on the ground, rather than move with the plane. Slewing it around will continue to track the ground until you're over a target, at which point it should begin tracking that target without further interaction. (You may have to change the size of the tracking gate.)

[malcheus]

I'm not sure if this is what you mean, but if you press 'lock' while the Shkval/Merkur pod is pointed at the ground, it will ground-stabilize—that is, it'll track a point on the ground, rather than move with the plane. Slewing it around will continue to track the ground until you're over a target, at which point it should begin tracking that target without further interaction. (You may have to change the size of the tracking gate.)

 

I found the "problem"; if you have the "game avionics" box checked, you get the behaviour I mentioned, and if you uncheck it, you get the behaviour you mention.

 

Another question; what is the difference between the control "throttle up/down" and "thrust up/down"? I assume they are the same, since using them move the same "lever" in the cockpit. ...