Amarok_73

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.

Hi, You can define group entirely with Lua. This is what does Enchanced Gamemaster Script where You can find the Gamemaster_Templates.lua file, which contains plenty of templates definitions.

I've hardlocked the FPS slightly below the minimum shown without lock (about 10 percent) and my graphs are now flat as... Earth.

You brutal, you take pleasure in taking away hope, huh? They could include one in with collision model in the package with module...

Can I have keybind for Collision Steering in the RIO position, please?

That's the preferred setting exactly for the reasons You said. When I'll be back "in cockpit", I'll share my settings. There's chance You'll have some better ideas than I do.