Amarok_73

What do wrong, so the IR version is not usable?

I think, I was landing on "auto" like 2-3 patches ago without any issues. I wonder, what was the change in the ILS mechanics since then...

Thank You Ramsay for confirmation. I have then to change my message to my friend, who returned to DCS after years, that I informed how nice feature is the APP Autopilot in M2K. We have to wait then...

Sorry, it seems the track I shared was from other mission. Here's the correct one,that shows pretty clearly what I am talking about. M2K ILS and app autopilot problem Caucasus.trk

I ran a test under controlled conditions, after a full repair, without any mods, and it turns out the problem is with the module and the game. It seems that the further away from the airport, the more the autopilot's target point appears to be somewhere outside the airport. As you approach, this point moves towards the actual airport position. However, if you engage the approach autopilot early on, and additionally, with a larger deviation from the approach course, the square marking the approach path for the localizer and glideslope will not follow the actual approach path, but rather to the one marked to the incorrectly indicated point, which also draws a synthetic image of the runway. I suspect there's no way to correct this behavior without digging into the software sources associated with the aircraft module, so until the dispute between ED and Razbam is resolved, we can't hope to fix this. EDIT: Sorry for mistake with track file. I sent the correct one in the recent reply to this topic.

Recently I observe the issue with approach autopilot and synthetic runway symbology. It is like something is really messed-up as the approach dashed line and synthetic runway are totaly not at the correct places, and the square that should show correct approach path is just pointing directly to the airport instead of leading to the localizer/glideslope path. Is it something with my game, or it's confirmed that there's such problem now with the module?

Hello, I have observed that when there's pair of planes taxing for take-off on Pampa Guanaco and Franco Bianco airfields, the backtracking second plane gets on the runway befofe first departs causing them to get stuck.

With yesterday's patch applied, after the botched landing in the F-14 when the "awaiting wing fold" message is shown, switching to the Apache does not clear this message.

Hello, After the yesterday's patch we noticed that it is impossible to get into Game Master slot if it was secured by password. Providing password cause slot to appear on the list, but clicking on it, doesn't put the player into that role. Same we see for the Airboss position, and possibly with the other passworded slots it will be the same. Can anyone confirm our observations?

Anyone can confirm/negate that there's problem with loading the DTC to the Fulcrum spawned from dynamic slot?

For me it's still like pulsating sound of turbulent air.

No xtension, 100, 0.

You say, You don't have this option?

What are You babbling about, actually?

I'll give you usefull tip - apply for refund. You don't seem to be the one compatible with this plane and you already become spiteful, snappy and obviously frustrated before you've even given yourself a chance to get to know the machine properly. There will be no chemistry between you two. Good luck!

For about the last two updates, we've noticed a significant decrease in unit movement smoothness in multiplayer missions hosted on a dedicated server. Device hotplugging is disabled on server and clients, as is replay recording, on server the high performance power profile is used. Nothing has been changed or added to the missions, yet all units jump and warp at relatively consistent intervals, about one second apart. Has anyone else noticed this lately?

Two - Smarter AWACS, and TADS Zoom FLIR TV from Pilot Seat. I did repair and will observe the situation.

I know this requirement, but this was multiplayer session, so track file would be quite large, IF we'd not have disabled the track saving with "disable_write_track = true" on both, the server, and client.

It happened to me yesterday, the SA-11 was higlighted on RWR as actively tracking me, but there were no any warning sound.

I am not sure if You are aware, so I'll ask if after calibrating the axle, you center all of them before you save the settings? I know that thumb stick is centering itself by default, but this is the only reason of such strange behaviour that comes to my mind...

Sometimes - that was my scenario - the joystick grips comes from factory with wrong settings for analogue axles, and require correction/calibration in Virpil software so You should have also the Virpil base (or borrow one) to do it prior to connecting the grip to the Moza base.

...yeah, and there's still no option to enable the LST from the pilot's seat...

Just search the MIST or MOOSE for "net.dostring_in" and You'll know from where to expect unexpected.

Some time ago it was possible to "preselect" SKR in ACQ, and as soon, as the laser spot was caught by the seeker, the crosshair was placed over the lased target. Right now, the way to overcome the limtation that came with change of this behavior, is just to observe the rectangle that follows to some extent the pilot's head, and as soon as it became large and solid, we have the indication that the laser has been spot by the Hellfire's seeker. This moment we know, that it should be possible to switch ACQ on the SKR. I once saw a thread somewhere where @NeedzWD40 explained it quite comprehensively, but I still have hard moments with getting the point, why the dotted cross can't appear automatically, without having to "hunt" for the moment when it becomes possible to turn it on. If it would work as it was initialy implemented, it was pretty natural, that selecting the SKR prior to getting the spot, pilot (or CP/G) declares he has need to see the crosshair as soon as the laser is spotted by sensors. Such behavior rather contributes to improving situational awareness and shooting precision. Apparently something deeper must be escaping my overview of the subject.

Hello, I would like to kindly inquire whether the implementation of a north direction pointer in the TADS is currently under consideration. Such a feature would greatly enhance quality of life and improve spotting efficiency, especially during multi-aircraft operations.