backspace340

I've not seen it said anywhere that the IR Mavs are waiting for the new FLIR rendering system (only that the ATFLIR is) - that seems to be an assumption some in the community have made but I don't think it's accurate. They've been working on the IR Mavs and they were originally slated for release at the same time as the laser Mav - they're functional (albeit buggy) with a lua edit, I don't expect we're going to have to wait that long.

Which headset do you use? I think I've seen other people using the Vive report this same issue elsewhere on the forums (but it seems to be fine in all other headsets). If you're using a Vive that might be the key bit of info the devs are missing.

1.probably a bug, 2. Put your TDC over the number you want and press TDC depress. 3. That's your ghost velocity vector, it's showing your true path of motion when you have your HUD caged. When the HUD is caged all the symbology is centred so it's easier to see, but because of wind etc you aren't actually travelling straight forwards - the ghost velocity vector is showing which way you're actually travelling.

You need to hold cage/uncage when the target is in the circle.

It's realistic to be in one eye, but Wags has said they're looking into giving us the option of both eyes in the Special menu.

There's also a bug with the merged laser codes on the Maverick page, they acknowledged it in the release notes - assume it'll be fixed in the hotfix.

There's a pretty big difference between the 9L and 9M - mainly that one has a smoky missile trail and the other doesn't. It's a lot easier to get kills with the 9M because they don't necessarily see it coming. With the 120B / 120C, the 120C is longer ranged and has a higher resistance to chaff. There aren't any scenarios where you'd take the 120B / 9L (or 9M for that matter) if the 120C and 9X are available. You might find that the 120C and 9X aren't always available though (especially on something like Blue Flag).

Yeah it would be useful to see a bit lower down on the left - if you've got the master arm off you might have clicked SIM mode by accident or something?

Looks like you've loaded the wrong missiles - they say TST (which i'm guessing means 'test'). You need to load the AIM-9X or AIM-9M, I think you might have loaded the CAP-9M (which is a captive missile used for training - it doesn't launch).

I saw someone mention a mode to slave the radar to the JHMCS as well - guessing like a slewable boresight mode.

Yes you're misunderstanding - the problem does not depend on the launching aircraft. If a Harrier was doing a buddy laze for you at a 10nm target and you fired a laser Mav at it, you would see the same bug. If you launch at 16nm at a target being lazed by a jtac that's 2nm away from the target, you won't see it. So the launching aircraft doesn't matter (which is what he's trying to explain with the statement you think suggests buddy lazing) - the source of the problem is the laser source and how far away it is from the target. It doesn't matter if you're buddy lazing or self lazing, if the designator is more than 8nm away you'll have this issue. In the video he is both firing the laser and launching the maverick - and there's just that one laser.

8nm, but yes. It aims at a floating point 8nm down the laser 'line' even though the ground is 10nm away (for example). And as the aircraft moves, the maverick chases the floating point rather than aiming at the point on the ground you're trying to lase. It's worth pointing out that a LGB would do the same thing, and the A10s TGP has the same issue. It's a problem with the way ED have tried to implement a max range for the TPODs - instead of making the laser pointer not appear on the target if the target is more than 8nm away from the laser source, they've fixed it at a maximum 8nm range so it floats.

In the video there is just one source - the TPOD on the harrier. The Hornet won't have the same issue until it gets the ATFLIR (unless they fix it before then).

It's definitely more useful this way knowing what your actual fuel burn is!

On the menu screen immediately after starting up, what is the version number in the bottom right hand corner? It needs to say 2.5.3.23788. Updates are released to the Open Beta first so people can hunt down the bugs, the JHMCS will come to stable on the 14th mostly likely.

Looks to be the seeker detection range - if you WPDSG where the laser is, you can get the seeker to uncage and slave to the waypoint and look for the spot from any distance, with a bit of trial and error you'll find it pretty much always locks at 16-16.4nm. There is a self-destruct timer on Mavericks IRL I think - set to go off whenever the battery runs out. There is though a bug with the TGP/TPOD in the Harrier/A-10C - the laser range is only 8nm or so, but if you're out of range the Maverick will still lock, only it locks the floating end of the laser wherever that is. So if the laser designator is orbiting 10nm away from the target, the Maverick will chase a floating point 2nm away from the target.

I had the same thing, no idea what I was doing wrong - if you go to the mini-updates thread, Wags has attached a mission just below the Maverick video and after I couldn't get mine working I used that without any issues.

It does it with the E, it's a bug that's been reported. Steps are actually easier than that - select Mav on the stores page twice (so you go to the seeker page), then select AIM-7 (doesn't matter if you've got them equipped), you'll see the placeholder IR Mav page.

It was definitely showing more than 150 before this patch - maybe 2-3 patches ago it changed.

They're broken for us all if you get them from the ground crew - they only work if you load into the mission with them set from the mission editor.

No because it's relative, not absolute - you can see how it would work by assigning something like your joystick Y axis to it. You move the axis 5% and it'll slowly increase/decrease the elevation, let go and your joystick will return to centre and the elevation will stop moving. It's realistic right now, but annoying because there's no natural controls for it on the vast majority of controllers. Personally I'd love to map it to the pinky wheel on the TWCS, so +1 for an option for an absolute axis...

Yeah I spotted this as well - it'll uncage the seeker and the seeker will slave to the WP and lock up as soon as it's in range. It's handy for firing at your maximum range (which seems to be about 16nm) - you can press WPDSG from 20nm and then just watch the DDI for the X to turn into a box to show the 65E is locked and fire.

You have to put the big circle in the JHMCS over the enemy and then HOLD uncage until the smaller seeker circle follows the target, then you can fire.

Hmmmm. Might be worth recording a track & video of it for someone at ED to look at. Might be something obvious we're all missing.

Wonder if it's something to do with your monitor set-up. Maybe just set to one monitor and see if it works then?