StandingCow

Ok, this seems resolved in the latest patch. Thanks ED!

Has anyone tried A/A refueling since the FM changes? A buddy and I did (or in my case attempt to) A/A refueling and it felt like there was a dead zone which made minor pitch corrections really difficult to accomplish, you'd suddenly be pitching up or down way further than expected?

I'll try next time I fly and report back. I think reproducing could be as simple as scrolling through contacts quickly, I'll see if it still happens with the new patch.

FYI the mashing isn't what triggers it, that was just frustration, the mashing only happens after the bug triggers.

Weird that he is switching missile type for no reason. Another workaround might be having George laser your target then take control of the missiles yourself. I attempted that but forgot to flip the trigger safety, so I'll try doing that next time I fly.

Also added a twitch clip of the bug in case that helps: https://www.twitch.tv/videos/1316452913 I probably could have fired as a pilot in retrospect but forgot to flip my trigger safety, still a bug though since George stopped being able to fire.

What happened that resulted in the issue? George will stop lasing targets and you lose hellfire symbology (no box). What were you doing that caused, or seemed to cause the issue? Possibly scrolling quickly through targets on the George target select screen. But I am unsure. I made it happen, as you can see in the track file on the instant action target range mission. Could you reproduce it? Yes, this happened to me on multiplayer servers multiple times, and I recreated it in an ED provided mission, possibly by scrolling through targets quickly in the George target select screen. What module where are you using, and does it happen with others? Only happens in the apache as it's the only thing with a George AI. I have no mods installed, this is an ED provided instant action mission. apachebug.trk

@NineLine@BIGNEWY Can you poke the team? They still haven't fixed this even though they inserted some of the thanks to Asto. We still have to alter the file after every update.

Yea, even worse on planes like the Tomcat.

Someone emailed Jello from the FPP on this as well: “Military power. If you happen to go into afterburner, so be it, but afterburner is not required.”

Yep, agreed. Some folks found a few videos where ABs appear to light up on carrier traps, but many think that's just the force of the trap putting them into AB by mistake.

I created this over on reddit and wanted to see what people here thought: Just this weekend we were doing carrier traps and I noticed our flight lead didn't use afterburner when catching the wire, I joked with him that it was a cut pass, he said you don't use AB when trapping.... a few of us were rathen taken aback and were SURE that we were supposed to and in fact remembered Jello telling the story of his cut pass and how he didn't use AB. Even my twitch chat had a few people saying AB should be used. Turns out we were totally wrong, I looked up videos of all sorts of carrier traps and AB was not engaged on trapping, in fact I think the Jello story was that he DID engage AB and that is why he got his cut pass. We looked up chuck's guide as well as official documentation and... other than extreme cases... no AB is to be used. https://www.reddit.com/r/hoggit/comments/uhx6o9/what_were_you_the_most_confidently_wrong_about_in/ Lex has a carrier trap video where he also says full mil: https://www.youtube.com/watch?v=f5GIW7ZVma0&t=759 So, anyone have a concrete answer on this?

It's a bug report, ACLS should work with the carrier moving at 25 knots.

Newy, we think it may be due to this, it seems if there are two hornet groups it screws with ACLS, client track also below. And here is the client track link: https://file.io/MkSEkgGJd64t

Attached mission file and track file, carrier was moving at 25 knots. The ACLS was drifting left, at one point it will try to correct to the right a bit but not enough, then just gives up with you too far to the left. Track file: https://www.file.io/ssP1/download/uzilWcEjb87U nighttraps.miz

Hey @Asto you got a shout out from the devs in the file now, that's pretty cool. This is is implemented in the hotfix.

Thanks VERY much for this. Pretty much just a plug and play in the code for me.

Totally agree. Liberation shows us how much the DCS AI drags everything else down. Even if ED came out with the dynamic campaign today... the bad AI would really drag it down.

From what I am seeing it is "partially implemented" on all ED modules except for being fully implemented on the Apache. Word is it should hopefully be fully implemented in the next big patch. As far as 3rd parties.... I think they have all enabled it now? Someone put this together with images from a bunch of modules: https://imgur.com/a/8OxkB4I

I use dark mode, that's why it originally was grey, I changed it to a darker grey.

I edited and made the text white, hopefully that helps? Not sure how that would have happened.

Hey all, we found this out while toying with the apache in MP, this was done in the hoggit training service with tons of other folks, so it should work pretty reliably everywhere. Map page set to attack phase (this is so when we create mark points they appear in the threat coord page. Slave the TADS to your general attack area either a waypoint you set ahead of time or a mark point as mentioned above. Create a mark point while lasing on the target you want to destroy then slave to that target. Confirm with your pilot that he sees the same target as you. For some reason slaving to targets seems to undo/reset the desync. Set your aquisition source as the created waypoint, if you set your map page to attack phase this should be in the threat coord page. Laser while still slaved to your markpoint, confirm with pilot he sees you lasing, if he doesn't then unlase and lase again, if that doesn't work cycle the laser from the weapons utility page. Fire hellfire once parameters are confirmed with your pilot (large box, sees laser, etc). A few other random notes: - We also found that things seem to resync after rearming the aircraft, so you only need to do the above steps if the nasty desync demon starts to show it's ugly face during your flight. - If at any time you get out of the aircraft alot of things need to be toggled in order to resync them. Laser in the wpn util page, possibly laser codes, channels, radio squelch, etc. - Best to start from a cold/dark aircraft. Don't touch anything until everyone is firmly seated and buckled up.

Things like this are why I really wish ED would add more to the newsletter... not necessarily asking for everything to be in detail but just a little comment that work continues on this or that, because to us that don't have insight to the inner workings of ED it can almost look like something has been "abandoned" or that devs were put somewhere else and the item isn't important. This would at least put minds at ease.

Pretty simple for me, ED needs to open this up to mod devs to integrate things like Overlord bot before I will be interested. Once that is added I will happily use their in house voice.

It would be nice to get some sort of feedback from ED on this.