Nor are we! 
Will take a while to fully incorporate the new afterburner system and get it right. Having folks’ displays working correctly was the main reason for the update, we’ll need a bit more time to learn the new stuff before adding it properly 
Re the manual, it’s going to be re-written for the next update as so much has changed, but it can be downloaded from Just Flight’s product page for the F-15s.
For managed speeds and altitudes, first you need an active flight plan, if you are going managed speed, connect the autothrottle and the FMC will be setting the target speeds automatically between flight phases, take off, climb, cruise, descent approach and final approach. For managed altitude be sure alt hold is ON, and the next waypoints altitudes will be refreshing in your altimeter’s target altitude, the aircraft should climb and descent by itself from current altitude to target altitude applying a calculated Vspeed. But be careful when using managed altitude since, if the next waypoint altitude is zero, the aircraft will descent to the ground, so you need to correct it by setting selected altitude again.
Technically what the toggle does is unlock a retent when using an specific throttle template, the same way a320 has specific throttle template with retents for climb, flex, toga etc but you didn’t need to press any toggle to change a position.
incorporating native afterburner in MSFS relies in the use of two tables: one for thrust and one for afterburner thrust, which values act as a multiplier over the main thrust table values as function of Mach and N1 when afterburner is triggered. Before the update we could only use one table, and the additional missing thrust from afterburner table was added directly into the thrust table, whitin the range 90-100% of throttle, simulating the afterburner stages. That said, if I used the f-18 throttle template on our engines I would have to apply that Gate pos at 90% and not at 80 like the f18. But, the result is the same. I honestly have not understood why them have put that template in which users needs to bind a toggle, I personally have eliminated that retention on my end and can use afterburners in f18 without the need of the toggle.
Thanks for the quick replies and answers guys. Out of curiosity, what is one thing you from a 3rd party developer point of view you would love to see Asobo add that would add a feature you’ve wanted for the Eagle, and other aircraft of yours obviously or make something a lot easier for you guys on the development side? Either way, keep up the fantastic work guys and I feel like I should send you guys a challenge coin that there are only about 50 of floating around in the world right now.
OK. Thanks Dean and Jack! That makes a lot of sense. I agree with Jack - I am not exactly sure why Asobo implemented it the way they did, but… again, there are lots of things I am puzzled by. We shall wait and see what comes of this. In the meantime, the F-15 is still an absolute blast. As is the F-14. Looking forward to the F-16 now!
Give me that and I will be happy
Canards are in, yeah? Dino was talking about native support for the Long EZ - that was done a while ago, I believe.
F-22 and F-35
B-1B
B-1B, Viggen, Typhoon, XB-70
Sign me up for any of the above when you guys get around to them. Well, except maybe the Typhoon. I really have no interest in that one. But the rest are cool. 
But I do not think it’s native, if we talk about Eurofighter, for example, It would need the elevons as a first pitch control surface, and the Canards to destabilize and stabilize the plane, while in the current model you can only define a single horizontal stabilizer. Unless there is any documentation that I have not read.
Hmmm Jack, might we see your version of the F-18 in the store? I would love not having to use a key bind for afterburner (I’m on Xbox btw)
Not at all, we don’t need to complicate it with a mod:
Open FA18E_cockpit.xml via notepad and look for this part of the code:
Now, replace
<AFTERBURNER_GATE_POS>0.8</AFTERBURNER_GATE_POS>
with
<!-- <AFTERBURNER_GATE_POS>0.8</AFTERBURNER_GATE_POS> -->
Save it and you are ready to go 
Silent, I’m aware of how to turn it down and am able to do it manually, but it doesn’t get “useable” until around 20%. To me, it seems like the scale is off when 100% is totally blown out. Just trying to confirm if A) that’s the correct brightness for 100%, and B) point out that when loading in already running, it’s defaulted to 100% and pretty unusable.
Good stuff, except I can’t do that on Xbox. 
It’s going to take a while to perfect the new features, so it’s best to be patient if you’re on console and unable to perform such mods. The airplanes will be updated in the New Year.
I have faith in Asobo fixing that, as they stated the Afterbuner “toggled” is a known issue, as you have seen is really easy.
If the afterburners requiring a toggle is a known issue, why the heck would they add a keybind option for toggling the afterburners in the first place?
Maybe they’re just really big fans of the Concorde or early Soviet jets that had a separate control to engage the afterburners.
I think the implication here is, they added the option for future developments (e.g., a Concore or Tupolev “Concordski” aircraft) but didn’t intend for the F/A-18 to require it.
Any one else’s engines cutting out at ~51,000ft? It’s weird, they still have graphics of AB, but no thrust. Only tried F-15C lately.
It’s probably some version of the current “altitude bug” that’s causing OAT (outside air temperature) to be inaccurately high - like hundreds of degrees high. That will cause loss of lift, engine power and probably eventually engine overheating. Above 44,000’, this has been a known bug since SU7 was released. But since yesterday it also seems to be affecting any plane flown in Live Weather as low as like 25,000’.
Lamelefty is right - it’s an MSFS internal bug with live weather. Hopefully they will fix it soon - how something so bad gets through their QA testing I have no idea.
