LorenLuke

If you look at your VPC configuration tool that you have for virpil stuff, one of the things I noticed is that any joystick device is labeled by it's base and then you gotta be like 'This has a constellation alpha grip on it' or whatever, somewhere in the menu. So even if you use the same grip, it's considered a different device (which would have different binds) because the device is the base itself. The good news is that if you bind it the same as you had before, it should behave the same as well (as far as I know, anyway; certainly as far as the laser and shooting the hellfires are concerned).

While technically correct, I feel that your missing the point as they see it. While you don't need a lase, strictly speaking, you do, however, need either an acquisition source in constraints, or valid laser energy detected and in constraints. If you don't have the first one (which someone just beginning to learn the module may not know how to do), then a laser is required. A self-lase dead ahead is the most rudimentary and straightforward way to obtain a valid launch condition, and is likely what is meant in this case.

Likely referring to the TEDAC, and (kilo) hellfires requiring a lase of some sort to track.

It would be, methinks, except that they claim they lost the big box when following through with the trigger pull, which makes it seem like there's some sort of bind that loses the laser, unless I'm completely misinterpreting what's being said.

I'll admit that I've fiddle with the software a bit so I'm not completely sure your bind outputs are the same buuuuut, I figure I can try to clarify for absolute clarity, since I have the old Alpha and the binds are slightly different from the modern pro model. First off, the trigger guard setting doesn't apply to using the TEDAC Right- and Left-Hand Grips (RHG/LHG), but the pilot stick. The Copilot does have one of their own, but most of the functions on that stick exist on the TEDAC hand grips, and those should be bound instead. The in-game trigger guard should be something you only worry about in the pilot's seat (and only if the special setting is enabled for it, which I don't think it is by default). For the Copilot/Gunner controls using my constellation alpha: The first trigger, when flipped forward is bind 1, when pulled it's bind 2. When the second trigger is pulled halfway it's bind 3, and when pulled until it clicks and stops moving is 4. Bind 2 to the second detent of the laser (RHG trigger, second detent) , bind 3 to the weapon trigger first detent (LHG trigger first detent), and bind 4 to the weapon trigger second detent: null Nothing: Lasing only: Shooting: null

Try binding the first trigger pull on your Alpha (the flippy trigger) to the RHG trigger (LRFD) second detent, and the second trigger on your alpha (the back one with two detents) to the LHG trigger (weapons trigger) first and second detent. To launch pull the flip trigger back to get a lase, and then with a big box, pull into the first detent of the second trigger to launch the missile. This is how I have my alpha bound for the CP/G Seat.

It'd be nice if you could just... toggle it off as a 'Special' setting.

Well, let's look at the other helos for a moment. The Ka-50 is counter rotating, so nothing there. The Hind has a canted rotor, so its lift vector is tilted a few degrees sideways to offset crabbing. The Gazelle and Kiowa are so light, the output for the engines isn't the same as trying to lift a 10 ton helo, and conversely the gearboxing isn't going to turn the tailrotor into a sideways hurricane. And the Mi-8 and Huey don't have flight path markers, so could you really tell anyway? The AH-64 instructor Pilot you're quoting here is also sure of this. The crabbing issues are known and have been mentioned by him and others countless times before that the Apache has about two and a half more sideways movement than it should. Doesn't mean the rest of the flight model is unstable or otherwise garbage.

The LMC and WPN switches for the copilot still are broken when using a HOTAS/Button Box to toggle them. Using buttons to display the WPN page displays the ASE page, and using a button to activate the LMC does not work. Worth noting: The WPN switch and LMC switches DO flip correctly, but the functionality for using buttons are not the same as simply clicking on them with a mouse.

We're all already here, playing our 'flip switch in cockpit like it's the real deal'-simulator/game with various aircraft, developed and curated for this experience based on their fidelity to the genuine article... Find someone among us who isn't an enthusiast.

If you've seen the actual controls for the YakB, it's this massive contraption that looks kind of like those binocular viewing things you put a coin in and look around the bay, or from the Observation deck of the empire state building or whatever. As far as I could tell, it's something that requires two hands and even then is aimed by a reflex/holographic sight. I can't find it, but I do recall reading a translation of an interview given by one of the people working on the Hind P for DCS, and they mentioned this was a deliberate choice: if the pilot does, the gunner can control the aircraft without losing the functionality of the gun. I presume this to be since they can aim it via a fixed sight AND don't have to take their hands off the flight controls to operate it, this was ultimately one of the reasons why. Also, the GSh30-2 long is a rather chunky and high-velocity cartridge, so it has decent armor stopping power and a flatter trajectory, versus the YakB's 12.7mm (personally the middle ground of the VP's turreted GSh23-2 would be the best option, but I digress). I still think, reasoning aside, the turret would be more fun for the pilot-operator's seat and gives them more engaging things to do, besides navigation, countermeasures, firing 4/8 missiles, and then that's it, however, the point of this post is to show that there was reasoning (and a reasoning I understand, even if I don't completely agree) in choosing the P variant Hind.

That said, if you use the LST, find the target, turn off the LST, then give a quick squirt with the LRFD, it should show you a distance you can use (if it's within ten clicks).

The LRFD is only for direction, not range. The only way to get range is to guess, or to correlate what you see with the map, and put a point down, using distance to that point.

Random question @Hammer1-1... Are you using TAA (temporal anti-aliasing)? I've found that to make a lot of screens near unusable, such as in the Kiowa. Try some of the other anti-alias settings, and that might help out (or at least mitigate).

Did you connect to the ground air supply as well? Engines are started via bleed air from the APU, not by electric power it generates.

The website hasn't updated the manual since March. So that's not exactly an option.

I'm not sure that this is a bug, but its behavior just seems so different from the other radar search modes (but given that it's an air search mode and all the others principally aren't, I could see how it behaving like this would make sense). AH-64ATM.trk

As title suggests. AH-64Jettison.trk

Your radar was set to Auto Elevation, which tries to scam the ground in front of you as best it can based on your radar altitude. Given how low you were, and the fact that this means the radar was pointing downwards per this automatic elevation logic means that any air targets above you would have had to be very close to be picked up. And that all assumes that the trees in front of you wouldn't interfere with the radar in some way, either. Try again, but use the manual elevation and move the elevation indicator to about 2-3 ticks above that large line on the vertical scale (you can do this from the front seat only with the FCR as sight and using the manual track thumbstick up/down) before scanning. Very likely it was shot off in the barrage of cannon fire.

Were you using the FM radios? This issue had occurred to me as well, but only with FM radio usage. I can't say for certain why, try ensuring that both your FM radio presets are on different frequencies, as it might somehow be sending from both FM1 and FM2 (whether that's correct to the aircraft or not), and therefore your teammate picking up two broadcasts.

AFAIK, it's only available to the pilot via the FCR MFD. They seem to be mentioning the 'zoom button' on the CPG's right handgrip, and that for whatever reason the MFD button wasn't working for them previously, until now.

Kept it. The radar is too good. That said, if it gets resolved, not-refunding it just means RB gets my money anyway, and I still have that initial discount, and hopefully I get to play with my GBU-15 at some point.

Asked and answered.

I've noticed that upon receiving datalink target data, or an RFHO track from a donor Apache, the C-Scope on the receiving aircraft does not display the data. For RFHOs, the NTS is shown on the TADS around the RFHO target, but again, there's no C-Scope visual indicators shown. I'm curious how true to life such case are or are not.

It's less about seeing someone's opinion, as much as it is seeing it, expressed repeatedly, unchanging, over a prolonged period of time, in the same space, with each subsequent iteration deviating in no way from the original in terms of form or content, including in response to varied feedback and points addressed in peeps new ways.