Floyd1212

The default camera position has moved a few times since the launch of the Apache. You can find some additional discussion here: Not sure if the solution provided works in VR, but I'm sure there is a similar procedure.

Setting a dead zone for the cursor axis has also been known to help.

This still doesn't sound like normal behavior. Or perhaps I am not understanding what you mean. If George returns a list of 5 targets, it should have the ">" next to the first unit by default. From there you can press down once to step to the second unit, down again to step to the 3rd unit, etc., then right to select the unit for engagement, or left to cancel out of the target list. It shouldn't jump straight to the 5th unit unless you pressed up while on the first unit. Could your buttons for up and down be reversed? What if you bind those functions to the keyboard? Do they still behave the same way?

Just so you don't think it is a problem with your setup, that is the way the torque display works in the Apache. Think of it more like a reading of how much strain the rotor system is under at any given moment, as opposed to a linear throttle position, like you would associate with the gas pedal on a car. As the aircraft begins to accelerate in the direction you want and comes up to speed, the strain on the rotor system is reduced and the torque drops. I personally don't use a curve on my collective, but I think whatever setting you get used to, your muscle memory will eventually take over and it will become second nature.

Unfortunately for us, DCS gives us all the "Area", and not much of the "High Explosive"

That is the way it has always been. A snip from the manual that was released at launch:

This sort of glosses over the part where you move the stick in the opposite direction of where it is currently trimmed, press FTR, release the stick to center itself (assuming center position trim mode), repeat a few times, and now you are back to center. Or, some people prefer to just press trim reset once, while you are moving the stick to the position it would be in a real helo. Not that I have ever flown a real Apache, but my sense is that if you are flying straight and level at 115 knots, the stick will be fairly far forward. To each his own.

Is this happening in both up and down directions? You should be able to roll around to the other end of the list from either direction, if not mistaken.

I think it's just a matter of preference as to when you might use trim reset. Some people don't mind fidgeting with the trim the entire time they are flying, others prefer a 1:1 relationship with the in-game controls and their physical controls. I only trim when I am in long-distance cruise mode, or when I need to take my hand off the stick, or switch to the F10 map, or when hovering. Otherwise, I prefer to reset trim before slowing to a hover, landing, doing any low- or high-speed NoE flying, etc.

This sounds like the default behavior we have seen with the PNVS since launch. I can't find any threads that discuss it, but apparently the "auto gain" setting is always enabled for the PNVS, when it should be an option you can enable or disable. With it enabled, the gain will change as you look out to the horizon compared to looking at the ground closer to your aircraft. It doesn't have anything to do with looking inside vs outside the cockpit specifically. Actually, I just double checked and the auto gain feature seems to increase the gain when looking closer (inside the cockpit), and decreases when looking to the horizon; opposite of what you are describing.

I think the idea is if you fly in VR you can have both sets in front of you, and depending on the aircraft you are in, press buttons on the appropriate bezel. I don't fly in VR, so I can't comment on how well this might work. I would think it would take some getting used to. This is obviously less useful if you don't fly VR, and have a screen behind them with exported displays.

That looks nice, but where’s the TEDAC already?

Simple track that demonstrates the issue. (I let George do all the work in the back seat.) Spawned into a stationary helo at 120 ft and my frame-rate settled at around 40-50 FPS. Then I tell George to descend to 80 ft and the frames drop to single digits. Tell him to ascend back up to 120 ft and the frame rate returns to around 50. Frame drops at the fortress.trk I'm running an RTX 3090, with the following graphics settings: Curious to see if others see the same results.

I think IRL you would have more SA as the front-seater while the aircraft is maneuvering. Your peripheral vision, and the forces on your body, would tell you a lot about where you are now in relation to what you were just looking at a moment ago. This doesn't translate to the sim world where you feel nothing, and have zero peripheral vision if you are zoomed all the way in to the TEDAC.

Yes, it would be nice to have that, like you do in other aircraft, but the Apache does not allow the CPG to see a cursor in the HMD indicating where the TADS is currently looking. This is possible from the back seat, but not the front seat.

No, nothing has changed with the TADS video recently (or ever). Can you provide a screenshot of what you are seeing so we can better understand what you mean?

You don't need to map the throttle, just the collective. Move the throttles to FLY during the startup procedure with your mouse, then leave them alone. The collective is what you want to manipulate during flight.

The exact same thing happens to me in those two locations. If I try to land inside the walls of the fortress on the east coast, frames drop to single digits when I go below a certain altitude. If I stay above that altitude, I can over-fly the area without issue.

When you view the axis in the controls assignment screen, you see feedback of the axis position? Do you have a dead-zone of 3-4 set on both X and Y axis? The cursor can get “stuck” around the edges of the MFD without a dead zone. Maybe you set one for PLT seat but forgot for CPG?

You can switch to the front seat before you take off, and set the TADS to DTV mode, then switch back to the back seat. This helps you see what he is looking at better, but I'm not sure it has any impact on how successful he is at hitting targets at that range.

There is a dedicated thread for that campaign here: https://forum.dcs.world/topic/300863-ah-64d-griffin-campaign-beta001-gulf-of-oman-mp-coop-2-8/ That might be a good place to post your comments, and videos.

I can see how that would feel natural on a fighter jet, where the aircraft is going to go straight when you are not applying force to the stick. But with a helo, to keep the aircraft flying forward your cyclic stays forward, and when you bank you move the stick to the side, and when you want to level out again, you bring the stick back to center, not in the opposite direction. I guess once you have given up on having a true cyclic with mag brakes to hold the position of the stick for you, you might as well do whatever makes life easy, even if it isn't an authentic feel.

Did you return to land at the same spot you took off from? Do the frames drop when you land somewhere else instead? Do you see the same results when you fly the Instant Action Mission out of Kobuleti (Live Fire Range)?

I'm not seeing this behavior. Maybe a control bind conflict? Maybe a hardware issue?

Did you return to land at the same spot you took off from? Instant Action Mission, or something you made/downloaded? Maybe there was something on the ground there that was tanking your FR, and once you got away from it things improved?