Floyd1212

I don't know that you have the choice. Doesn't it decide which to use based on your altitude?

Just flew again and there is still some oscillation there with Rad Alt Hold, but it is manageable.

And there was much rejoicing!

It is much better again, and seems to hold a hover nicely once settled down. I don't know what to expect out of the system when intentionally maneuvering the aircraft with ALT hold enabled. I was in a hover at tree-top level and tried to creep forward slowly with ALT Hold enabled and it allowed me to climb a bit before kicking in, then when I slowed back down to 0 it allowed me to descend a bit as well.

How much movement are you talking about with the pilot drift? What distance over what time? And how much drift on the TADS are you seeing? Without a video showing what you are experiencing, it's hard to say if the rest of us are noticing the same thing, or if it's a controller issue.

This is still a thing... Can a SME chime in to verify this is/isn't an issue in the real aircraft? If it isn't working as intended, can this thread be moved to the Bugs and Problems forum? There are track files attached above.

I can confirm the same thing on Syria. Didn't try any other maps.

Cry is not optional. SAT is my preferred map mode... I just hopped in and ran an Instant Action mission on Caucasus and got the same result. Two steps forward, one step back...

Yes, the flight model has changed over time, and the position of your pedals will not match what you see in that video any longer. On a side note, if you come across any old track files and play them back on a current version of DCS, you will get very different results than you would when they were made. I had some tracks of me flying up and down the length of a runway, practicing decelerating to a hover at each end, and playing back those tracks now result in me spinning around and veering off to one side and crashing.

Very handy!

After he is lasing the target for you, you have to "WAS" Missiles yourself in the backseat, then fire off a missile. The next time you tell him to lase a new target, he will WAS the missiles back again, so you have to WAS them yourself again. Only one crew-member can have control of a weapons system at a time (with the exception of rockets in COOP mode).

I think he is referring to complete 360 degree barrel rolls. This never happens to me in forward flight, or even in aggressive NOE flying at speed, but has happened unexpectedly when trying to do some lateral maneuvers at low speed. For example, while trying to pull a tight circle while keeping the nose pointed toward some infantry on the ground, or when aggressively side-slipping an ATGM coming at me. It seems with a lot of lateral air movement across the rotor system, combined with some pedal input (maybe in the "wrong" direction?) can easily get me in trouble. Maybe there is some advice instructors give their students that I haven't heard mentioned around here, like "never touch the pedals when side-slipping laterally", or maybe it is just a FM WIP thing.

I think this goes back to some of the other threads that discuss the SCAS and the "breakout values" where the computers make the decision to stop fighting you to try and keep the aircraft at the desired heading, and start to help you. Pressing and holding the FTR is the way the pilot tells the computers "I am maneuvering the aircraft now, don't fight me". Personally, my FTR button on my cyclic is too uncomfortable to hold for extended periods, so I use the "tap method" instead, but this means I am constantly butting heads with the SCAS with my intentions to maneuver the aircraft, vs. the SCAS's intentions to maintain an attitude.

That was in 2D, not VR, BTW. But it's the same issue experienced all around, though it probably bothers folks in VR more, since the whole experience is more "in your face".

So you tell George to use Hellfires and search for a target, when he finds one he lases it. You tell him to engage, but if it's beyond 8km he won't shoot at it, saying it is too far So you WAS Missiles from the back seat, and pull the trigger to launch one yourself. George is still lasing the target, and the missile is guided. You won't have a time-to-impact read-out, and at 9km you are looking at a 35+ second flight time, so don't give up on it too early.

In fairness, the training mission he was performing did tell him to unlock the tail wheel while he was still sitting there... Regardless, here is what I am seeing for pedal input to keep the helo from yawing after unlocking the tailwheel. My axis is setup with Y-Saturation of 80. I would say 60% right pedal is a bit of an exaggeration, but yes, you have to apply some right pedal before unlocking that tail wheel. No fantasy FM or other wizardry involved.

Even with the latest 2.8 update, George still engages targets at 7999 meters and closer for me. Maybe post a track file at the shooting range where he isn't engaging below 8km and we can see what the issue might be?

Can you post some screenshots of your controls indicator when it isn't working? Are you saying the red X will stay where you intended when you press and release the Force Trim Release button, but then when you let go of your joystick the white diamond returns to center?

Not a whole lot to go on there, but maybe something similar to this? https://forum.dcs.world/topic/311239-force-trim-not-holding-for-cyclic/

Never heard of them, but the pics make them look pretty bad-ass, not gonna lie.

I tried some different screen capture software, but it didn't seem to really capture the issue quite like how I experience it in person, so I went old-school and used my phone to record the monitor. This is pretty accurate with what I'm seeing in game.

Is there a way for someone at ED, or anyone really, to post a video of it working without the stutter? There are several videos in this thread demonstrating the problem, but I don't think we have seen a video of anyone demonstrating the PNVS working as smoothly as TADS. Also, can you ask the Dev team at what frequency the PNVS is getting updates of the current head position of the pilot? Does the PNVS track the head position 10,000 times per second, or once every 10 seconds? We know it isn't either of those ridiculous extremes, and it is somewhere in between, but where? I tried recording a video of the stutter I am seeing in game when playing at 3440x1440 at 60fps, but my video recording came out scaled down to 1080p at 15 fps and does not capture the issue. I need to find a better video capture solution...

Okay, but the other two issues are not indicated as "reported" anywhere. At least not in this Multi-Display subforum. This thread is about the ghosting issue, but also mentions the brightness issues, and you only seem to have reproduced the ghosting issue of the TEDAC above. Here is a thread about the exported MFDs being too dark at night: https://forum.dcs.world/topic/306391-does-anyone-at-ed-fly-with-display-exports-to-secondary-monitors-at-night/ Can you verify this has been reported, and then mark the thread as such? Until we see some sort of response from ED in the thread, we can only assume it has gone unnoticed. Thanks!

It would be awesome if someone at ED was designated as the "multi-monitor test person", and was running a setup with exported MFDs and TEDAC. There is a group of very dedicated enthusiasts that go the extra step to setup sim pits with additional displays and controllers, and then their experience is thwarted by some of these issues described here and in other threads. TEDAC ghost image in-cockpit when display is exported exported MFDs not matching the gamma setting of in-cockpit displays exported MFDs unusable on night missions when the in-cockpit displays are turned down

I'm sure there is a .lua file you can edit to change the setting back to single-monitor. I'm not sure where that is, though. You might try posting this in a more general forum as it isn't specific to the Apache module only. You might get more eyes on it in https://forum.dcs.world/forum/999-multi-display-support/ for example.