backspace340

I basically just held the stick at a point to hold the AOA at 15, and didn't do much else! It looks impressive but it's really not, it's all about controlling the AOA and then just waiting to reel them in. Against a player you'd probably have to do some of that fancy pilot shit, but against the AI it's that simple every time - I repeated the same tactics against the F-15C, Hornet, Su-27 and F-5 and it worked against them all. There's a longer unedited video showing that here: First opponent is an F-15, then Hornet, then F-16, then a couple of F-5s.

Black Lion's advice was perfect - just try not to exceed 15-17 units of AOA at any point in the fight, I just pegged my AOA at 15, tried to put my speed at around 0.6 mach and then just reeled him in. The AOA indicator is just below the HUD - for the first turn I cut my throttle till I was at M0.7 and then just went full burner for the rest of the fight. Video here: Pretty sure the people that are struggling are pulling 20-25 AOA and wasting all your energy.

Just select the landing master mode on the right upright panel (where you pick AA/AG etc) - it's the bottom button.

Your only option with Jester is to STT lock the Su-27, engage him and then try looking for the M2K once the 27 is dead. Personally, I'd probably just fire a Phoenix at them both. If you had a human RIO you could get him to change the priority order and put the Su-27 first, but Jester is a lot more limited.

Thanks for that - really interesting. I assume you're using full burner the entire time, or are you at mil power or doing something more complicated with your throttle?

It's not supported by the ED engine apparently, I wouldn't expect anything to change.

It's a command for STT locking target 2. You don't need to do anything to command a TWS 'lock' - Jester does that automatically, the numbers to the right are missile priority order. If you did nothing except fired two missiles, the second one would have targeted target 2.

Bind the Jester button, the controls are separate for front and back and you've probably not bound it in the front.

The pre-purchase and module pages for the Tomcat don't mention a terrain, so don't expect one. It looks like it was mentioned as a hope in the first announcement back in 2015 when they were still Leatherneck, but I saw somewhere Cobra has already confirmed they're not committed to it and it's not coming as the terrain team went with Leatherneck/M3.

I've heard there are issues with the GBU24 and GBU10s - apparently only the 12s and 16s are following lasers.

I've flown both with him and with several human RIOs, Jester isn't remotely in the same league - not even compared to the day 1 RIOs who were learning as they went. His main problem is spotting and tracking anything between 30nm and 5nm - things will drop off radar and arrive in the merge (or you'll merge with a contact that never even appeared on radar). You can see human RIOs moving the radar left and right, up and down looking for and tracking targets - Jester's radar is fixed straight ahead unless you tell him to move it with fairly coarse commands (which you don't have time for). I'm sure it's fine for fighting AI in SP, but he's just not competitive in MP. Hopefully when TWS auto gets fixed he won't lose contacts so easily.

It's a lot better with a human RIO, so it's not a limitation of the aircraft itself. Jester seems to really struggle with maintaining TWS closer than 30nm. From talking to human RIOs, it sounds like Jester isn't controlling the radar elevation himself as much as he should be to maintain the targets - someone else mentioned that TWS Auto isn't working properly yet. I'm hoping that there are more improvements to come - right now flying with Jester isn't particularly competitive in MP, and there's a significant gap between Jester and a human RIO.

It's showing where you are on the glideslope - think of it as the LSO's view of your landing. When you're behind the boat you'll see a green diamond representing where you are. You can see what I mean in this video: GiM9gKyQ0es

Thanks for the tips, but that doesn't solve the bug. That happened because we were miles away from the action and we assumed the bug was triggering again (like it had 50 times before that). It would just be nice to have launch warning = being launched on, like it is in every other module.

You might also have to arm the ejection seat before he'll continue with his checklist.

You have to start the engines up first (both), then you'll hear him doing some clicking, then you'll hear a squawk on the radio and you'll then see the INS menu next time you open Jester's menu.

It is? I swear I looked for it and couldn't see it... Will have another look when I'm next on.

It can happen from up to 100nm away from the looks of it, it's not that - there's no possible way I could be in any tracking radar cone. You don't have to be anywhere near the unit actually being locked for this to happen.

Yes it's on beta, updates are pushed to stable once major bugs are fixed. Should happen in the next 1-4 weeks or so.

It's the same button you use to open the menu.

Thanks - I thought that was the case but wasn't 100% sure when writing this up. It did actually get me killed earlier - had a human RIO in the back seat as we got pinged and we both thought it was another false RWR hit, until a missile hit us :(

It'd be really useful to have some shortcuts we can bind directly to HOTAS keys, so in a panicky fight we don't have to fiddle with the menus (I imagine this'll also help people using voice attack!). The one I'm most keen on getting is 'STT Lock Enemy Ahead' at that seems to be the one I want to spam the most - but feel free to add your suggestions here for HB too so they're all in one place.

I almost wouldn't mind if the screens were the other way around, and the attitude indicator/TV were at the bottom - those screens I only really need to see the middle, not the very bottom of the screen so I could probably cope with that being obscured. Can't for the life of me understand why they'd design it so the TID/HSI is obscured when you need to see the entirety of the screen for it to be useful. Maybe we're just spoiled being used to looking at the full screen and maybe the F-14 pilots of old would just trust that their RIO knew what was going on and wouldn't bother watching the TID.

Right now in the F-14 if a SAM locks on a friendly/other target (works even with a TALD, for example) then you will receive a lock tone (even if you're separated by 10nm or so) - this one is a long-standing ED bug as far as I know - HOWEVER, if the SAM launches at that other target, then your RWR will show that it has launched at you and Jester will start panicking and telling you to evade a missile that's not being fired at you. That last part is a new issue unique to the F-14. It makes life really difficult because in MP servers someone is almost always being fired at by SAMs, but you never know when it's actually firing at you.

You can adjust your perception of scale using the IPD adjustment in settings. It seems perfectly fine to me in VR, and they laser scanned the real aircraft, so I don't think they've made any measurement mistakes.