Floyd1212

This new implementation is not really a "bug" per se, as it was discussed that the previous implementation was not totally correct either. Just a different approach that is still being worked on. It would be nice if there was a video/picture/illustration of the real thing to understand this mystical phenomenon...

That is the correct volume knob, but there was also this bug mentioned in June. Not sure the current status, though.

I wouldn't say Redfor is supper aggressive about it, but they do launch some strike missions against your zones, and if one does go neutral, they will send a HIP to capture it. This is more of an issue early-on, when you might only have a single blue group defending a zone you just captured; once you are further down the road with 3-4 groups defending a zone, they don't strike with enough firepower or coordination to really recapture an established zone.

Scroll to the right? Looking for the "Mouse" column. Oh, I see, you don't have those 4 "Camera" functions shown.

You can check that the camera axis are bound to your mouse for the CPG seat, which is a different set of control bindings than the PLT seat.

To answer the OP's question: It doesn't look like the LST is implemented yet, so the LST Mode switch on the RHG probably doesn't do anything at this time.

Glad you were able to get it worked out. Sometimes it's hard to tell if the issue is a genuine bug, or if it's someone new to the module that is still discovering how things work. One more gotcha you might not be aware of: when doing a cold start, the CPG will need to take the extra step of powering on the laser on the WPN > UTIL page.

It's relatively easy to modify the mission to remove the UH-60L player slots, or there is also a way to modify the .miz file so that the UH-60L is optional, and clients that don't have the mod will see some other model in its place. The SAM Site Asset Pack is a little more involved as I am using those assets for the barriers and statics at the Northern FOB. You could go in and view the list of units and find all the assets that require that module and delete them, though. Everything will still work, but the FOB will look a little bare.

Are you saying you can't lase targets? This sounds like an issue with your binds, not the module. Many people are out there lasing targets and shooting Hellfires all day long.

There appears to have been a change made in the last patch such that George cannot tell where you are looking unless you have TADS as the active Acquisition Source. This is how the CPG temporarily slaves the TADS to the PLT's helmet sight, and then de-slaves to start looking in that area for targets. You can set the AQC Source with R6 on either the main TSD page, or WPN page. This is already done for you in a hot start aircraft, but needs to be done manually in a cold start.

Yeah, I much prefer the cover of the trees and hills of the Caucasus map over the flat and barren regions of the Syria map. The mountainous regions are good though. I found Cyprus is a great area for helo ops on the Syria map, though.

Thanks for the write-up! And I couldn't agree more; down low at the treetops is where the fun is. I need to do better at being aware of my egress options, and planning accordingly, though. When I do find myself climbing to higher altitudes it is often to engage a target that is tucked in a valley or on the other side of a small hill, where to engage at a safe distance means a much higher altitude. What is the recommended tactic in that situation? Stay low and get closer to engage, or stay at a safe distance and climb higher? I suspect the right answer is probably to mark the target and wait until I have a better angle on it from another position, but that requires discipline and patience.

As a work-around you can press "up" twice quickly and get it to change and stay on Transition Mode. Fidget with the timing to get it to stick.

Isn't the whole reason the radome is mounted atop the mast is so you can hover behind cover with just the radar exposed and see what's out there? At least that's how they sold it in the brochure. Each method of engagement has its time and place, you just have to know when to use them. You do not what to come to a dead stop and hover directly over the target area, unless you are going to attempt a Death Blossom.

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!