jubuttib

What Ryan said, it's been out for hours already. I like to set up notifications for new releases on any mods shared on GitHub.

Is there a similar clickable option for the rear seat? Whenever I'm backseating the throttles always stay in the locked back position, not moving with the pilot's throttle. EDIT: Should have said this more clearly: I'm backseating for someone else.

JEEZ, the new v1.2 flight model makes hovering _butter smooth_! This is now right up there with the post-updates Gazelle as my favorite hovering helicopter, and it's not even actively damped/stabilized! It was a lot of fun even before, but jeez it's just hecking awesome now.

Thanks!

First the WSO Maverick controls: I can slew the seeker around OK, but I can't enable zoom. In the manual's WSO section for the Maverick it says the following: Half-action command on the hand controller does not command a zoom, it enables slew momentarily. So far I've not found any of the inputs on the hand controller to be able to enable zoom on the D Maverick. I suspect the flight stick trigger would work, but I haven't bound anything to that since I wanna leave the pilot stuff to the pilot. Similarly I can't pop off the cover with the hand controller, which doesn't really surprise me. I expect that I would need to bind the flight stick trigger for this as well? Next up Jester: Can I get a confirmation that Jester is unable to lase targets at the moment? I could get him to lock up a point on the ground pretty well, but laser guided bombs definitely didn't guide. Worked fine with a human WSO. The manual does mention Jester's Pave Spike capabilities will be expanded on during EA, so I guess this is one of those things. I would also kinda like it if he could do stuff similar to what Petrovich and George can do in the Hind and Apache, i.e. I could tell him to look at an area and he could spot targets there.

The 12-vis and 9-vis bindings are working the wrong way around, to enable 12-vis you need to press the button that's bound to 9-vis, and vice versa.

Related to this whole subject, though maybe not the thread: I've been having quite good accuracy with slick dumb bombs, but the CBU-87s and RockEyes always stop well short of where I'm actually aiming. Feels like it's not taking into account the bomblets slowing down after the bomb opens up, is this possible? I.e. if the CBU-87 or RockEye never opened up, the bomb would land where I'm aiming, but because it opens up the bomblets fall short?

To my understanding reading the manual, the "radar boresight line" is used for the a-g radar stuff. A-A radar is horizon referenced.

Honestly, in my experience it doesn't even have to be very close. I've had it successfully arrest a slight climb/descend just fine after putting myself into "attitude hold" to change flight levels. The "stick not being perfectly centered" thing tho is a very likely candidate.

And acceleration equals zero when thrust forces = drag forces. EDIT: Man that emoji annoys me... It was supposed to be a simple smile, not a laughing face...

Good catch! Thanks!

Yeah, but he as the pilot can climb, it's just George who can't. I.e. there's a discrepancy between the torque behavior the helicopter exhibits while he's in control, and when George is in control.

The one at 300 feet with him in the pilot seat is showing 88% tho.

FWIW I'm not thinking about thrust to weight at all, more about thrust to size. Aerodynamic forces scale so quickly that I've always considered weight a secondary concern to top speed. Acceleration, sure, but not the primary factor for top speed.

There's at least one loadout with a small rocket pod and 2x Sidewinders on the inner wing pylons, but trying to create that same loadout manually is impossible. Adding the rocket pod removes the Sidewinders, and vice versa. (Video not fully processed at time of posting.)

Would be interesting to have more real life data. The Mirage 2000 is a slippery rascal, as evidence by being rated for mach 2.2 at "high altitude" with an engine rated for 95 kN of thrust, vs. for example F-16 at 2.05 at 40k feet with 130 kN of thrust (rough wiki numbers, please don't shoot me).

I mean... It should be? The SA342 has lots of autopilot/stability augmentation going on with it, while the Loach has none. The SA342 after the flight model update is IMO the _best_ hover and near hover helicopter in the game (ignoring Ka-50 hover hold). With the Loach I'm getting what I'm kinda expecting: A superduper light Huey that never properly settles and kinda wants to overreact to everything.

Yeah I found that out the hard way. My common troubleshooting for not being able to rearm (assuming the UI works) goes like this: Am I parked in the correct spot? -> Do I need to be on intercom? -> Do I need to have doors open? -> Do I need to be shutdown? Usually one of those sorts it out on any given aircraft.

Bless the Dutch. .50 cal door guns, 30x173mm (GAU-8) CIWS... Would really like to have that .50 cal on our Chinook at some point.

Aaah, that's probably it! Just checked and for some reason object and sensor exports weren't enabled, thanks! And I'm trying to cut down on my Discord servers, nothing against you.

Oooh, any hints as to what's coming? Also might as well ask, I've seen some people having success with the door gunner, and others not (including myself). Is it something simple like "doesn't work in MP" or whatever?

Hmm, so here's another question: There's no rearming/refueling binding for the mod, so I can't do that... EDIT: Oh right I can use the radio menu, duh.

Had this happen when playing with a buddy online, their helicopter showed up with a box attached. Their loadout was as follows: -Minigun on left side -7 rockets on right side -Full load of all grenades and color smokes Is this expected, or do I maybe need to fix something?

Not directly Apache related, but talks about various tricks that radars and the computers analysing their output can do to figure out what they're looking at.

Like Raptor9 said, that's not really what the radar on the Apache is doing. It's not nearly high enough resolution to do a 3d scan like that (especially multiple km away), but it does get more detailed information than your typical plane radar does, allowing it a better guess when categorising. The "counting the number of N1 blades" is afaik also a bit wrong, technically. To my understanding it's more that the spinning compressor blades (or turbine blades if rear aspect) create a very distinct kind of signal when the radar waves reflect back from them, and it's that pattern that gets recognized. Of course the number of blades affects the return signal, but I don't think they quite "count" the blades. That's also not quite all NCTR systems do, to an extent they also try to analyze the returns, and the shape of the plane (and the loadout on it) affects those returns. So the radar returns get analyzed and compared to known threat databases, and the computers try to make their best guess at what you're seeing, with varying certainty. I have no doubt the longbow radar also miscategorizes stuff occasionally. How often? That's probably a military secret...