Rongor

I loaded your Pilot.trk into replay. I assumed control right after you entered A for the guns ranging on the KU. Triggered the gun with [Weapons Trigger Switch- First Detent]. Gun didn't shoot. Then I switched [Weapons Trigger Guard - Open]. Then I triggered the gun with [Weapons Trigger Switch- First Detent] Worked for me. Gun did shoot, no problems. One of these bindings isn't configured correctly on your end. Your trigger guard is not open or it is but you didn't trigger the shot.

\Eagle Dynamics\DCS World\Mods\aircraft\Flaming Cliffs\Doc

If Batumi doesn't appear in your ATC selection, please make sure you configured Batumi on your side in the mission editor

The solution would be having ED acknowledging this.

This is especially annoying with the lack of map coverage on some map modules in specific map scales. For example I like to select 1:500k on Syria while using the 25km map zoom step. If I cycle to other zoom steps and back, not only do these other steps switch to other default map scales (this maybe so IRL, IDK) but when returning to zoom step 25 km, I am back on a stick map and have to select the 1:500k anew.

There is also the difference to the wind vector shown in the performance page.

Multiplayer, multicrew, I was the PLT. we got our left engine damaged, RTB'ed. After shutting everything down, even battery, repair still didn't work due to alleged engine still running. Just skip forward to the last 5 minutes on this 166 MB trackfile...https://ufile.io/o3vzxw7b

can we keep this thread tidy please? last posts might be worth looked into by ED, yet this thread is addressing George missing moving targets, not George's general performance nor his LOAL functionality.

Here is another track, this time it's only 50 MB. Like @Tank33 I am flying on Rotorheads. My average ping is 170 ms. Flew the Blackshark for more than 110 hours on this server, basically all my Vikhrs hit, never had a problem with lag. In the trackfile I startup cold on a FARP, George AI is my CPG, then transit to the target area. You will see several missiles hit the dirt behind targets. They also fail to hit some static targets. https://www.mediafire.com/file/gvvg5y5nayf2aty/Persistent_Syria_TPE_v4_RUN1-20220408-164408.trk/file

Hey ED, unfortunately your mission playback system doesn't allow file trimming, so please skip forward to the very last 10 minutes or so. I am letting George unload a dozen Hellfires on tanks moving perpendicular to my point of view. You can see on the TADS how they miss repeatedly behind the moving targets. Should be valuable data of the exact kind you might be looking for to investigate... https://ufile.io/amzyhdbh

Stumbling about others reporting this, I just tried to replicate and for me it's starting normally. I get the Boost pump fail caution temporarily but it goes away when RPMs are spooled up to ground idle.

Your video shows static targets. No idea what the benefit of using LMC would be in this situation.

Open the manual and read up how it's done beginning on page 205

yeah we always join for MC in a cold aircraft, not touching any switches until both are in the cockpit, to avoid sync issues

Can your human CPG hear the missile, searching, tracking alerts? He confirmed he turned up the RLWR volume dial on the radio control panel...

well, we don't have a central position trimmer mode IRL either

It's pretty odd that you say that, because I have mapped trim reset in all of them. Didn't you notice these while beta testing? Did I forget one?

so you still don't understand. As long as you think there was relevance, you didn't get it. Please read Raptor9's post above. Or do as you said and move on.

only in the mission editor, but - as mentioned - these changes currently don't show up in the presets displayed in the EUFD preset selection

Hiob is right, the central position trimmer mode always worked like this. the only thing making people think it is a special weirdness with the Apache is that many obviously only ever used default trimmer mode and since this one isn't available in the Apache, now are struggling to adapt.

No you didn't think, you posted it publicly, probably to leave a stain on my credibility, which is sad. I didn't meant to hurt you or anybody. In the aviation world, it's good practice to suppress emotions like this and keep eyes open for ideas opposing your established mindset. I don't understand how this would have prevented misunderstanding the FTR. Because the idea of having these modes magically make the FTR concept go away is one of many misconceptions in this thread.

yeah. two topics in one sentence and now we have a problem. You have to disconnect Wags use of the FTR from the reason he intended to maintain a certain pedal attitude. He could've done it in any other moment, maybe while hovering or during a turn. This doesn't mean FTR is connected to these specific attitudes. read and understand what @Raptor9 explained here English is not my native language so I couldn't have explained it even close that well he did. With any repetition of connecting Force trim to aerodynamic and/or nose-to-tail trim, you will promote further confusion. This thread is much too long already and we can't expect anybody to review all what was said and then differentiate between helpful and misleading.

So how is it relevant to a force trim thread, besides the fact that Wags used force trim in a video in a moment he wanted to maintain aerodynamic trim?

to be honest we shouldn't discuss trim reset here in this already cluttered thread filled with misconceptions. Wasn't there a thread about trim reset?