Polonsky

The Humvee blocking the wingman will into the player's unit when the player is still at holding position waiting for the clearance from the ATC before entering the runway. Screenshot: Player bumped into by humvee thus entering the runway with unexpected pattern

Is this fixed? Or at least turn off easy comm in the mission setting as they are designed in the way that the player should tune the Freq

Neither the briefing nor the voiceover of the ground unit suggest the actual laser code so I've assumed 1688. I didn't enter the LST page in FLIR and I've designated with FLIR page without modifying any setting except for the FOV.

The ground unit suggest they will light up a warehouse on the ground and request air support. However they didn't clarify the laser code for this operation. And I've tested with the default 1688 with designation right on the red smoke in the middle of the warehouse and dropped in AUTO mode with LST/NFLR on and end up in a complete miss. I have to arm my own laser designator (LST/NFLR+LTD/R) to hit the target. Not sure if the lasing from ground unit actually work in this mission.

I did press the modifier multiple times after step 3 in case 2 by repeating step 2 and step 3 in an attempt to bring back the trimming control. If it should work like a switch, it would probably work as trimming the second time I press (or even press and hold, assuming switch is triggered upon key down stage) the modifier. It didn’t happen as far as I’ve remember. Anyway, correcting the modifier type solves my problem.

Thanks for the heads up. I may report the issue to the DLC campaign designer instead to see why modifier can't be toggled off in toggle mode.

Thanks for the heads up. I've checked again yet didn't find where to select toggle or hold.ption for selecting

For HT16000M HOTAS scenarios (stick and throttle), modifier button was ALWAYS applied once used. Pic 1 Pic 2: Pic 3: Prerequesites: 1. assign JOY_BTN2 from the throttle the as MODIFIER (pic 1) 2. assign hat on the stick (without modifier) for trim (pic 2, just like the default DCS profile) 3. assign modifier from throttle + hat on the stick for sensor control switch (pic3) Test Cases: 1 The control adjustment page (Expected behavior) √ 1.1 hat on stick - jumped to the correct row for trimming √ 1.2 modifier from throttle + hat on stick (simultaneously) - jumped to the correct row for sensor control switch √ 1.3 hat on the stick again - jumped to the correct row for trimming 2 Inherent Resolve Campaign+The Syria Map, in game (Bugged, modifier is forced after single use) √ 2.1 hat on stick - responded as trimming √ 2.2 modifier from throttle + hat on stick (simultaneously) - responded as sensor control switch × 2.3 hat on the stick again in all all operations - always responds sensor control switch from now on, like modifier is always pressed 3 Stock F-18C Campaign, in game (Bugged, modifier works in toggle manner instead of holding manner) √ 3.1 hat on stick - responded as trimming × 3.2 modifier from throttle, then release, then hat on the stick again - Responded as sensor control switch, as if modifier is toggled on √ 3.3 modifier from throttle again, then release, then hat on the stick - Responded as trim again, as if the modifier is toggled off Exported Profile: My_F18C_T16k_thr_example.diff.lua PS: I've also tested JOY_BTN2 as modifier plus the hat on stick operation in A-10C II, modifier works like case I (applies if and only if pressed and hold)

I've noticed that more gauges were turned in to English compared to the last version yet didn't get related info in the release notes. No idea if it's a bug. The previous version The current version, with the DEFAULT cockpit setting. nullThe altimeter: метры -> RADIO ALT The "HSI": км -> MILES, зпу->COURSE

The same issue was observed in the subsequent Oil Business Mission, better check all missions that starts from H4 Airport in Jordan. @Looking Glass

I’ve disabled Easy Communications in my settings and checked the “ignore mission configuration, use mine” option. This problem doesn’t occur before September

Using COMM I/COMM II with "RAlt+\" or" RCtrl+R" will always ends up in the AUTO COMM option, even if I've deleted the the default "\" key binding for AUTO COMM, as is shown in the "Communication menu" in the screenshot above. This is annoying as the channel were were changed unexpected and user has to scroll all the way back to Chanel 1-2 every time contacting the ATC. Test with the VBIED mission. Check the top right menu in the screenshots below. For comparison, the stock F18C Mission doesn't come with such error as shown in the screenshot below

It’s not about the frequency selected in the channels of radios , it’s the discrepancy between the kneeboard and the actual frequency (top right corner in the screenshots) that works.

null TACAN channel on kneeboard: 31X Actual channel that will reach Echelon: 35X

null Frequency on kneeboard: 250.10 Actual frequency: 250.15