Floyd1212

Just as an FYI, if you fly in 2D and follow the procedure I describe on Aug 16th on how to save the Default View for the CPG, you won't have to do this every time you get in.

I would be onboard with this approach as a short-term solution. Change the default behavior to Hidden, and let the mission designer specify the relatively few units that should be shown on the MFD. If your mission is go destroy this SAM site, you would likely know the (last known) location of that SAM site, but not all the fun surprises that await along the way. And the large dynamic missions that rely on scripting that are currently broken wouldn't clutter up the database like they currently do.

Keep in mind that they shifted the "neutral thrust" point of the pedals "to the right" (assuming your axis aren't inverted) by a couple inches with this last update. So now the pedal position while lifting the helo lightly off it's wheels is closer to center than it was before. Not sure if you saw that in Raptor9's post above with the pictures. Just wondering if that is throwing off your testing while your axis are inverted from their previous setup.

This was part of another thread that got merged, so posting again in its own thread... As of the 9/21/2022 patch, the Symbology Select Switch Up and Down is bugged when playing in multiplayer with a human CPG. Once the human CPG joins the aircraft, the Up and Down commands will "double press" so that it won't stay on the desired mode. (Work-around: You can quickly press Up twice to get it to execute 3 times, and stay on Transition Mode, for example.) This does not occur in SP, or in MP when George is in the front seat, only when a human CPG is present. Note: These binds were cleared in this patch release, so you will need to rebind these functions as well.

Yes, there are many elements to the Flight Model such that generalizing the entire thing as better or worse is not helpful. Sorry. The subtle changes to SAS pedal authority, or collective authority are changes that are adaptable. It takes a little time to adapt to the new "normal", but you get used to it. The sudden change in the "neutral" position of the pedal took me by surprise in my first take off, but now that I know it is different, I have adapted. I do feel that the tail rotor seems to misbehave more often for me when trying to get into a stable manual hover. Once I'm settled, I feel like it rotates one way or the other, and when I apply some pedal to correct it, the response is delayed and then it starts drifting the other direction. Maybe I will get used to that as well in time. My biggest complaints after this patch are the two bugs that were introduced that are quite frustrating to me. 1) the tail failing to respond to input and then suddenly over-correcting like the snap over-steer in an a Porsche 911, and 2) the severe vertical oscillations introduced when enabling ALT Hold. My flying style was to get into a battle position by establishing a hover peeking over the tree-tops while my CPG goes to work. The helo used to be rock solid with ATT and ALT Hold modes enabled. If I needed to change direction or side-slip a bit to get a better position, I would disable ATT Hold, maneuver, then re-enable. Now I am spending an extra 30 seconds getting it back under control so I can reapply ATT Hold again. And since ALT Hold is unusable (at low altitude) at the moment, I'm constantly monitoring the collective as it has a tendency to all of a sudden decide to SAS itself into a steady descent that you may not be able to recover from. I think what makes these two bugs frustrating to me is because either the changes weren't fully tested by the internal team before releasing the patch, or there was no communication as to what to expect with the patch. If the team knew that ALT Hold is not working correctly in this release, maybe say something in the patch notes about how ALT Hold is currently broken because we are currently working on XYZ. But when it is not mentioned, it appears to everyone else as just a QC issue that could have easily been caught. Because of these two current bugs, if given a choice of flying the previous version vs. the version we have today, I would choose the previous version. I do appreciate the other bug fixes that were included in this release, and I have said so in other threads, but when it comes to actually flying (and hovering) the thing, I would consider this a regression for me.

Perhaps this is just a typo, but you aren't looking for the "sight selection" binds, you want the "Symbology Select Switch - Up/Down" binds. I tried watching T-bone's track, and I can see the symbology mode changing on the IHADSS in the track, but I am unable to resume control of the track for me to try myself.

Yeah, it's a bit rough at the moment; a major regression from where it was previously, in my opinion. Let's hope ED pushes a hot fix soon.

Yes, those two binds were cleared with the recent patch.

Isn't there a little compartment for you to store your stuff in the back? Just saying...

Those commands weren't working for me either, until I realized the bindings had been cleared by the update. After binding them again, they are working as expected. Are you sure you have them re-assigned correctly?

Sweet, I'll give it a try!

This was fixed in the patch released 9/21/2022. Thanks, ED!

As you probably already anticipate this, the response there would be Early Access is not mandatory, and is there for those that want to get in early, with the expectation there will be issues along the way.

+1 I have yet to see ED acknowledge that they even understand the problem they have created with this "feature" in any of the threads discussing the issue. At one point BIGNEWY said the solution is for the mission designer to set the units to "Hidden on MFD", but this is broken, and does not work properly in all situations. Please ED, give us one of two solutions until you have a fully-featured DTC implemented. 1) Make it an option that can be enabled/disabled in the special settings, or 2) give us a command to use after startup to wipe all threats/targets from the database at once.

Thanks for the updated config. I gave it a whirl, and I'm seeing a lot of yaw adjustment is needed while ATT Hold is enabled. It feels like there is no SAS helping to hold the nose at the desired heading at all, like the "breakout" percentage is down at 0%. Is this what you are going for? (I'm using pedals without a spring, btw.) For the ALT Hold, I am getting the large vertical oscillations still. In 2a) are you saying that the ALT Hold is still bugged, even with this config?

This is new behavior with this patch. You used to be able to arm the chaff before lifting off. But if it is correct behavior, we will learn to live with it.

Yes, many are able to fly just fine and enjoy themselves. Have I had to learn to adapt to some of the quirks in the FM? Yes. Do I regret purchasing the module in the EA stage? Not at all. It may not be for everyone, though.

Yes, there are some redundant controls between the TEDAC grips and the flight controls. When controlling the TEDAC as CPG, the controls you need to worry about are on the LHG and RHG.

It's a little bit different than your two examples since those require you as the pilot to take a moment to press a button on your joystick, or to look down and use the mouse to press a button in the MPD (or if you have a screen in front of you, for you to reach your finger out and press a button). Think of it like opening and closing the canopy door; you can map that function to a button on your HOTAS, but it still takes a moment for it to execute in the game.

This appears to be fixed with today's patch. I looked at the PrestonAI_page_common.lua file that I normally have to modify after each release to get George working again, and I noticed this section of code got re-written. I didn't modify anything and fired it up, and George is working. Thanks ED!

Yeah, ALT Hold mode is not working properly for me. I activate ATT Hold and ALT Hold while at a stable hover at 50 feet, and the helo will gain and lose altitude in long oscillations to a point where I even bounced off the ground. I really want to give ED the benefit of the doubt here, and that someone did some test flights before releasing this patch, and that I am just doing something wrong. Any advice?

This is because you are using a splitter instead of discrete outputs. To render something different on each screen, it needs to be a dedicated output from your video card. Do you have other unused ports on your card? DVI, USB-C, HDMI-Mini, DisplayPort?

Does the shake occur after you bring the engines up to full throttle ("Fly"), or only before? I was messing around in the TSD for a bit after starting her up the other day, and got some periodic shake while sitting with the levers set to "Idle". Once I bring them up to "Fly" I don't experience the shake again.

You will find a lot of people use an XBox controller as your left-hand and right-hand grips on the TEDAC. You can see some recommendations for how to map those buttons to a controller like that in the Controller Questions and Bugs subforum. When I am in the front seat (which isn't often), I use the controller in my hands and then occasionally use my mouse to click in the cockpit. In conjunction with head tracking, I rarely need to put my hands on my cyclic or collective. I have a button on the controller to toggle between free-looking around the cockpit and out the window with my head-tracker, and to a snap-view of the TEDAC pretty much full-screen. With my wide monitor I get the TEDAC and both MFDs filling my screen. Things are going to get more complicated when IAT and FCR are implemented, but for now there are plenty of buttons.

I occasionally get artifacts as PLT when I am viewing the CPG TADS video on one of my exported displays, but it isn't really a "flickering" as much as a black object moving across the camera quickly. My CPG complains of similar issues while sitting in the front seat looking directly at the TEDAC, and he is not exporting any displays. I never get any flickering or other artifacts on my exported MPDs when looking at other screens.