AlphaJuliet

Hello Ladies and Gentlemen, A feature not present in the last patch log (as it slipped into 2.8 unexpectedly) is a change concerning the ability (or lack thereof) to cycle through steerpoint types with the EHSD (moving map) arrows. Steerpoint types are : waypoints, targetpoints, markpoints IRL, in the jet, you cannot cycle through steerpoint types with the EHSD arrows. (So it goes only W0>W1>W2>W0 instead of W0>W1>W2>T0>T1>T2...) To change type, you have to do it through the Quick Access (QA) menu. Long press on the EHSD arrows or on the Waypoint Increment (WINC) button will bring it in the ODU. If you have a designation (DESG boxed on the EHSD), summoning the QA will bring the T0 between the arrows, select target in the ODU and 0 on the UFC scratchpad. If no designation exists, summoning the QA menu will have the current steer type selected in the ODU and point number populating the scratchpad. Also, while in the QA menu, you don't have the EHSD arrows available anymore, you need to exit/close the QA menu for them to reappear. Once the QA is summoned, you can choose between TGT, MRK, WPT in the ODU , which will bring in the UFC scratchpad either the last selected number of this type or the first of them (if you didn't use any point of this type during the flight). Then you can write a number of your choice in the UFC and push enter. This push on enter will close the QA menu. Then you'll have this point between the EHSD arrows and will be able to cycle through the points of the selected type with the EHSD arrows (and only this type). This makes sense as if you have a very big flight plan and a lot of different points of different types, cycling through them all can by very impractical, hence using the QA menu as a hub to navigate through your steerpoint types in the jet IRL. There is a bug currently where you can end up with a weird mix of steerpoint types that you can cycle through in the EHSD. This is a known issue and we are working on fixing it. Cheers, A.J.

Hello Lads, Here to give a quick heads up on the official manual. As it was said above, @baltic_dragon has paused his work on the manual while we rework the designation system of the AV8B. As a workaround, I direct you towards this forum or our Discord for help, towards the Chuck's guide that is regularly updated by the stellar @Charly_Owl who I would like to thank on behalf of Razbam Simulations for his relentless work for the community despite the constant flow of changes this module is getting through, and towards the most recent Youtube tutorials made by the community. As features are changed or added, I'll make clarification/explanation posts in this forum. I know I've not been active a lot on ED's forums since this summer, I will commit more around here to make sure that informations are properly broadcasted to you guys, and bugs reported and investigated. We are aware that having a full fidelity module released without a proper official and exhaustive manual is not acceptable, and we're working with the resources we have to deliver it to you guys as soon as we can. Cheers, A.J.

EDIT : Fixed on 02/09/2022 Give me a heads up if the issue comes back. Cheers Hello Ladies and Gentlemen, It seems that last update brought quite an annoying bug to the AV8B. It seems it is now impossible to create new waypoints in the DATA EHSD subpage by inputing not yet affected waypoint numbers. This is only for waypoints, TGTpoints and MKpoints are working as they should. A good workaround is to use the TOO function to create a new waypoint and then to edit its coords in the DATA page. Sorry for the inconvenience, we're working on fixing it ASAP. Cheers, A.J. P.S. : If you find other bugs don't hesitate to report them in the bugs and problems subforum.

Updated link

Yup

Hello, When G-LOCing, the stick input is kept at the deflection it had when the loss of consciousness occured, meaning in some scenarios you take even more Gs and never regain consciousness (in my attached track I went up to 17Gs). It's not possible that an unconscious pilot would be able to maintain a 25 to 40 kg pull on the stick at 500kts, obviously. Godspeed, and cheers ! A.J. Track : https://we.tl/t-Y1zmJbbZxy P.S. : had to make a wetransfer as the track is too heavy

Should be fixed for next update, issue was infinite dumping of water was lowering the CG to like 5m below the aircraft lol. No surprise it was a tad unstable at that point.

Issue reported

Issue confirmed and reported, thanks for the track. Cheers

The problem is generalised with all bombing computation. Basically, ED tells us where the bomb is supposed to impact and we put a reticule/calculate trajectories based on that. This computation is flawed and cannot be adjusted easily, if we adjust it for a set of parameters (angle, altitude, speed) it won't work for another set of parameters. We've already pinged ED about it.

It also seems inconsistent to me, investigating

Wow that's weird as <profanity>, seems like some errors of calculation are accumulating over time. I'm reporting it, we'll investigate and see where this is coming from. Thanks for the report, Cheers Censoring profanities, come on we're not 5 years olds ED

Issue confirmed and reported. Cheers, A.J.

Issue confirmed and reported, thanks for the report. Cheers, A.J.

Issue forwarded to the mission team, thanks for the report, Cheers

Issue confirmed and reported, thanks for the report and track. Cheers, A.J.

I personally tested it with no issues, spawning with and without a flight plan worked well. On old and new missions. The Harrier INS needs a flight plan (at least having a WPT1) to work properly, if you don't make any FP via the mission editor the aircraft will automatically generate a WPT1 directly in front of you. I'll investigate to see if the issue came back.

We probably didn't think about that, I'll report it but unless it's very easy to fix it won't be a priority. Thanks for the report, cheers !

That's strange, there may be an issue with the binds, I'll check

Indeed parking brake locks the throttle. If that wasn't the issue give me a heads up

Issue reported, thanks for the heads up lads. Cheers

That's interesting, I'll ask around

Forwarded to the mission makers, thanks for the report. Cheers

Issue confirmed and reported, thanks for the report ! Cheers

Issue confirmed and reported, tha,ks for the heads up. Cheers