olistotch

The laser code of a random hardpoint can change to -1 after pickle press, even if it was set correctly and checked at the ground. Some missions with start in the air (i.e. the quck mission for BRM's) have -1 code from the start, though it's correct in the mission editor.

You can also try to set Options->VR->Mirror Eye Source to BOTH. Helped in my case, playing with resolution had no effect.

See the screenshot. It's OK in VR but no MT... and in MT but no VR. Update: Moreover - it's present only with 'Russia' selected as helo's country! It's OK when you select 'Iran' or something. Some ultra-specific bug...

You're welcome. I'm not quite familiar with Stream Deck, just viewed some videos of it.. looks amazing. But I hope this method is applicable to it, because normally theese IDs are the standard way of DCS' script actions manipulation.

You should start looking in Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua Looking for ATC... bingo! { down = hotas_commands.THROTTLE_ATC, up = hotas_commands.THROTTLE_ATC, cockpit_device_id = devices.HOTAS, value_down = 1.0, value_up = 0.0, name = _('ATC Engage/Disengage Switch'), category = {_('Throttle Grip'), _('HOTAS')}}, So, ATC is one of devices.HOTAS commands. For Device ID, look into \Mods\aircraft\FA-18C\Cockpit\Scripts\device.lua devices["HOTAS"] = counter()--13 -- Stick and throttle grips, The DeviceID is assigned by counter() auto-inc function, but the comment at the right shows that it's 13. Then, open \Mods\aircraft\FA-18C\Cockpit\Scripts\command_defs.lua, and look for THROTTLE_ATC. We once again have this counter() function... But in the beginning of each commands set the counter is reset to 3000 (count = start_command). Counting down to THROTTLE_ATC... The CommandID seems to be 3037. So... DeviceID = 13, CommandID = 3037

После обновления 2.7.2.7910 на карте "Кавказ" присутствует ярко выраженный джиттер текстур земли. На остальных картах не замечал. Особенно хорошо заметно в "Весеннем обострении" на Ми-8 - в VR реально укачивает, но проблема есть и не в VR тоже.

You can assign axis to this frequency knob to reduce a chance of hitting the ground while trying to turn it with mouse wheel. Mini-stick has nothing to do in MiG-19 anyway... Modify ..aircraft\MiG-19P\Input\MiG-19P\joystick\default.lua, add {action = radio_commands.ARK5_freq_tunning, cockpit_device_id = devices.ARK5_CONTROL, name = _('ARK-5 Frequency Tune Knob'), category = _('Radio Navigation')},to res.axisCommands section. It rotates jerky just like with mouse wheel control, and gets stuck sometimes. But if you play with stick up/down a bit, it goes on, and you can finally tune ARK and fly at the same time, by listening Morse codes or making brief looks at the frequency dial. I've tried to assign +/- buttons to this axis, but no luck. Knob turns nice and smooth, dial doesn't rotate at all. Original +/- buttons still work absolutely erratically.

При взлете с "открыток" не фиксируется факт взлета - радиоменю не меняет состояние, остается во взлетном режиме, и запрсить посадку не выходит. Наблюдал с вертолетами и Харриером в том числе. Днем как бы и не критично, а вот ночью напрягает - барышня подсветку не включает :) Баг миссий конкретных, глобальный, или я что-то не так делаю? Трек с Акулой и миссией в "Республике". track.trk