Floyd1212

Interesting observations, but most of them are rather subjective, and are hard to quantify as definitive changes. I'll pay closer attention to some of these the next time I fly, but I would say I disagree with a few off the bat. I haven't seen any nose up/down oscillations during forward flight. At what speed were you seeing this? With or without ATT Hold? The amount of left pedal needed during lift-off was reduced when they made the changes in the previous patch, but I wouldn't say it was "virtually no left pedal" in 2.7. This seems about the same to me prior to 2.8. Uncommanded roll to the left is still a thing for me when pushing the nose down at 100+ knots.

It sounds like that is intentional, and for use with a toggle switch on a HOTAS like the Warthog. When the switch is engaged it "holds" the levers in the OFF position, then when you flip the toggle on the HOTAS in the other direction, it "releases" the throttles to the IDLE position where you can then take over with an axis bind. Without this special bind, you would need a toggle switch on the HOTAS with triggers in both directions, which a lot of them don't have.

We seem to be discussing two different things in this thread. 1) In order to slew the TADS around with the controls on the RHG, TADS needs to be the active Sight. 2) I just confirmed that even though you can bind LT Mode Auto, Manual, or Off in the controls page, pressing these bindings on the keyboard does not move the selector on the RHG in the game. However, you can click on the selector with your mouse and the rocker switch does change position. I think the point being made above is that the IAT and LT Mode features are not implemented in the module yet, so perhaps when they are, these bindings will be tied to the switches and they will animate properly.

You're not seeing it under the "UI Layer" controls? This is a global category that isn't tied to any specific module, so you need to select it from the drop-down menu.

After you launch the missile LOAL, and then lase while the missile is in the air, the constraints box goes to a large solid square to indicate there is good laser return to the seeker. Is this indicating the seeker of the missile in the air, or the next missile on the rack?

Even in LOAL DIR mode, there is a little bit of loft to the missile trajectory to get up over the tops of those trees. Try DIR and see if the missile stays lower, and can pick up on your laser energy later in the process.

You don't mention the trajectory mode you are using in your situation. Have you tried LO or DIR to keep the missile lower, and able to spot your laser later in its flight?

This was stated as a WIP at one point, so it sounds like they intend to make them functional.

It used to hover like a (hovering) rock, until they broke the ALT Hold. Looking forward to it returning to its previous form. Maybe in another month…

That would definitely be a welcome option for trimming.

Try "Central Position Trimming" instead of "Instant Trimming" and see how that works for you. You have to let go of the joystick and let it return to center before you can move it around again and control the aircraft.

Is there an improvement here with the 2.8 patch? I am running Foothold Syria 1.0.3 on my 2.8 server now, and I am not seeing any pre-populated enemy Threats in the COORD page. I do see 3 Control Measures pre-populated, which appear to correlate to the 3 blue FOBs on the map, Alpha, Lima, and Mike, so I'm betting as blue takes over the map, the CM page will still get filled up with friendlies. Can anyone else confirm?

Bring it!

I just flew a mission on a MP server, and the Communications Menu "\" seemed to work for me, both on the ground and in the air.

Do a search here in the forums as I think someone else had a similar problem a couple months ago. Can't recall what they did to fix it, but I think they got it resolved. Found it. Looks like he had to do a reinstall...

Props to the first Navy pilot that can catch a wire on that thing.

You can see here the 37T grid (shown by the red boundries) covers a large portion of the map, and is assumed in their situation. If they were operating on the boundary with another grid, it would be important to include that as well. null

You will want to program your main throttle on your HOTAS to the "Collective" axis in game. This is what controls the pitch of the blades, and therefore how much lift they are producing. The left and right throttle levers you see to your left in the cockpit are set to "Fly" during the startup sequence, and are not adjusted after that. I think a lot of players will adjust these manually with the mouse, and not have them bound to an axis on their HOTAS. Also, you use RALT+HOME and RSHIFT+HOME to get them from "Off" to "Idle", though you can bind those to switches on your HOTAS of you desire.

Bunny mentioned this in the first post of this thread. Known issue.

Yes, you can leave a function unbound if you don't need it, or bound just to your HOTAS.

If driving my car meant my hands were glued to the wheel at "10 & 2", and I had a spring-return on my steering wheel (God help us all), and there could be a scenario where the alignment of my steering wheel might not match the direction my actual wheels are pointing, you better believe I might occasionally look at my steering wheel, and whatever indicator that is provided to show what the current discrepancy is between the two. Have you ever gotten back into a parked car and your wheel was one full revolution from center and you were caught off-guard when you started rolling backwards out of the parking spot and you realized the wheels were actually turned? Yes, we see your point about flying with your eyes out the window, but having information about what the simulator is doing with the controls vs your IRL controls is helpful.

Here is some more of that "trickery" MAXsenna mentioned above, but it seemed like a lot of hassle. https://www.mediachance.com/multikeyboard/faq.html

Keep in mind, Windows won't differentiate between your main keyboard and the mini keyboard, so you can't bind a function to one and not the other. For example, you can't bind the KU "I" button just to the mini keyboard and still expect to press the "I" button on the main keyboard to show/hide the IHADSS. Or the numbers "1" & "2" for data entry on the mini keyboard, and still be able to switch seats with "1" & "2" on the main keyboard. One workaround is to use a modifier button on your cyclic that you can press and hold with your right hand, while typing on your little keyboard with your left hand, then go back and bind all the KU functions to your keyboard with the modifier pressed.

Sounds like your current Acquisition Source is set to "Fixed", which is the default on a cold start. Change the ACQ Source to TADS, or any other TSD point, and the crosshair will move to show the location of that source instead.

I don't think you are doing anything wrong; it is just how the ALT Hold is working at the moment.