LorenLuke

Worth noting that CTLD has radio beacon drops. I don't know if the target information for beacon bombing is stored in the beacons themselves or not as described, but having some sort of potential for a special options menu or the like to implement this as a feature alongside them would be neat.

Title. Apache PNVS-TADS Polarity.trk

It might be a thing, for lack of more apt analogy, like brake pads. Yes, eventually you're going to reach a point where your brakes don't work because... there's no brake left. That's a binary status-- they work or they don't. But, if I were to show you two sets of brakes that worked, but one only had 50 miles of road usage versus a set that had 30k miles of road usage, they're very different looking despite both satisfying the 'they work' binary.

The official stated release time is the current season (winter 2023/24); unless they push it back officially, that's the timetable we were told.

1) The marking laser seems to be viewable from the TGP screen (unsure if this is realistic) 2) There's odd flickering that occurs from the laser itself, especially when designating a point closer to the aircraft's 3/9 line; the source of the laser seems to jump around a good bit. AV-8B Laser.trk

null

I hope so, especially for mod makers. Would love to see this on the A-4.

If anything, the best weapon might be some of the bombs it carries. We won't get Man-in-the-loop capability until the DMAS version, but one of the Walleye IIs would probably be one of the better weapons to use, especially once we get the datalink pods.

To be fair, what could be considered the cold start videos were technically released in January of last year in Barundus' channel.

I can vouch that a Connie Alpha (with WarBRD base) and CM3 Throttle is what I use in the sim (and a head tracker). I won't say I'm a top tier helo pilot, but I can say in my experience it's 100% workable as flight hardware for the module.

Different kind of datalink. This is about the weapon datalink pod (Like what the hornet needs to guide SLAM-ERs/Walleyes), not the 'show me everything Overlord sees' mission datalink.

Alternatively, if they have two thumbsticks (CM3 Throttle and a joystick), the pilot only really has need for one as a cursor control. The left-right axis on the other (with proper curves, saturation, and practice) could be a workable option, as well.

I'll also vouch for a VirPil twist stick. It's been the only thing I've used (current arrangement has no room for pedals) and it's not really been a bother to me. Though it may not work for you, I use partial Y saturation and have rudder trim enabled for flight. It takes some getting used to, but I've made it work well enough, and perhaps it'll work for you, also.

IIRC, you can cancel out a good bit of the movement by using the linear motion compensator. Though admittedly the LMC does take a bit of effort to wrangle, I find it helps a bit when the pilot's flying is being a bit squirrely.

He's not always smart, reactive, or rock steady, but in short, yes you can. The bulk of the George/Petrovich nodes can be done from the flight mode, which basically boils down to 'increase/decrease speed' in stages (64 is 0/40/70/90/120kn/max; don't remember the Hind's), 'increase/decrease altitude' via tens of feet or in meters in the Hind, and then 'point the bird where I'm looking', with some miscellaneous binds scattered around, e.g. 'line up on my cursor' for the hind to shoot a missile, never mind controls for the hover modes. Landings might be touchy, but George/Petro is an adequate pilot for over 90% of situations, and certainly far from a terrible toll to utilize in the front seat.

Ah, an ad hominem. Thank you for confirming the solidity of my points by responding with, essentially, nothing. Except you prove it earlier in your message. It's hard to see how calling people 'low knowledge' or saying they 'don't know or care about the history' on a forum about historical jets can't be seen as anything but an attack.

Button bindings for Autopilot Hover Mode ON Button (Default: LCtrl + LShift + U) Autopilot Hover/Course (Route) Mode OFF Button (Default: LCtrl + LShift + I) Autopilot Course (Route) Mode ON Button (Default: LCtrl + LShift + O) do not work. The keyboard bindings do, but if bound to a button box (Virpil SharKa-50 Panel), they do not seem to press buttons as the keyboard commands do.

I personally just use 'Direct' and press the button a bunch when in zone.

AFAIK, ripple for smart weapons is not yet implemented; a long press only currently releases one per press.

A bit of a workaround until ZOOM functionality arrives is to zoom the TSD onto the area of your targets, maybe with your map set to SAT or DIG, as I often find doing this makes it easier to break out targets if they're too clustered together.

Worth noting that, despite this, if you have a solid track and TADS as the sight, pressing the 'Slave' button will track the target the hellfire seeker is looking at, despite it being labeled in white as '?SKR'.

@Raptor9 I've tried with another scenario that had more than 16 targets, and those additional targets do not seem to show up under any circumstance. Are low priority targets not yet implemented? If they are implemented, I can boot up the scenario and provide a track for it to show they're not there. Just am asking if what I'm experiencing here is a bug or something that's not yet implemented in the simulation.

The X (to my knowledge) doesn't move, and the X generated by shooting a laser hellfire at the target certainly doesn't move. And if you're worried about wasting hellfires, just wait for the LINK function and save some kilos for any you might have missed.

Because 1) It trusts you to be a competent pilot and recognize where you've previously shot. 2) Your missile got shot down or otherwise didn't reach the target, which the FCR can't tell happened. 3) Targets might have moved either from or to that shot position, throwing off any application of that logic within the aircraft computer. 4) Imagine trying to deliberately launch a second missile at a target, possibly to be assured of its destruction, and your aircraft telling you 'no'.