Floyd1212

Well, would you look at that. It says as much right there in the changelog (which I even looked at when the patch was released.) Carry on.

The IAT is pretty cool, but does not play nice when the PLT is looking at the CPG's video feed. The PLT sees the TADS tracking some phantom vehicle somewhere else in the trees or hills. If the CPG moves the MAN TRACK slightly so the IAT is no longer tracking, it fixes itself.

I've noticed with the recent patch that lasing through the trunks of trees, to armor beyond, is resulting in the missile impacting short. This T90 is out in the open beyond those trees, so the missile can definitely come down on it from above. I tried 6 times, and 5 out of the 6 the missile came down very short, near the row of hedges directly in the foreground. LRFD was set to LAST reflection. I feel like I would have been able to pull this shot off previously.

When you say "load", do you mean the progress bar before you are in the cockpit, or do you mean textures taking a while to load after you are in the aircraft? I'm still noticing long texture loading times, but that has been with us for a few patches now.

The Acquisition Source does not guide the Hellfire in any way, it simply helps the pilot get the aircraft pointing in the right direction prior to launch. Launching at 1000 ft AGL using HI trajectory, you are likely lofting the missile too high over the target.

Well, that's great. The text I wrote up to go with the post got wiped. The abbreviated version: I added some additional buttons to an Xbox controller using a Leo Bodnar MicroBBI button interface buried inside one of the grips (after removing the shaker motor). The paddle kit on the bottom was part of the controller when I bought it, but wiring the connections to the MicroBBI allows me to map them to discrete functions now, not just program them to be macros of the standard buttons.

No, you will need to hold the pedals in this position after unlocking the tail wheel. At this position, the pitch of the blades on the tail rotor are "flat" and not inducing any lateral forces on the tail. Once you increase collective on the main rotor for lift-off, you will also add some left pedal which will bring it back closer to center. If you have springs on your pedals you can "trim" the controls in this position and then release your pedals back to center, and this becomes the new center point for your controls. Most would recommend removing the spring from the pedals and using the "spring-less pedals" trimmer setting so they aren't affected by trimming, then you can leave them in this position for as long as you need to.

To keep the aircraft from yawing to the left, you will need to apply roughly 25% right pedal when you unlock the tail wheel. Something like this: That training mission should probably be updated to explain that, but it was created before the behavior of the tail rotor was changed in a recent patch.

This might come in handy when FCR is implemented, but Joystick Gremlin (JG) has a "Modes" function that sort of acts like a permanent "modifier" layer when activated. For example, you can have the button you use on your controller for selecting TADS as a Sight also put JG into "TADS Mode" and it can then map the D-pad and any other buttons to TADS-related stuff. Then when you press the button on your controller to select FCR as a Sight, it can put JG into "FCR Mode" and it can map the same buttons on the controller to FCR-related functions. It basically takes the modifier aspect out of DCS mappings and is tracked in JG instead, and means you don't have to remember to hold the modifer button down or not, based on what sight you have selected. Of course, if you select the sight using your mouse in the cockpit it won't track with it, but as long as you use the controller it will. I also don't know yet if you would ever need to use functions to control the FCR when it isn't the active sight, or TADS, etc. We shall see...

Check this other thread where a recent solution from ED was discussed. https://forum.dcs.world/topic/314057-tvdvoflir-3-positions-button/

You can’t really find an Xbox controller that has different button options. At least, I haven’t found one. The model I have has the 4 extra finger paddles that you snap onto the bottom, but they aren’t really extra buttons, you can just assign them to emulate any of the other existing buttons on the controller. I know several people that have issues with their wireless controller going to “sleep” on them, so I’m a fan of a wired controller.

This is the thread: https://forum.dcs.world/topic/308874-temporary-apache-fm-edits/

This might be good information to disclose when posting a video claiming the FM isn't an issue for you, just so we aren't comparing apples to oranges. I tried his mods when it first came out and VRS on the tail rotor was an issue, but haven't tried it again since then. I might give it a go again and see how she flies. Does ALT Hold mode work properly with his mods, or does it still oscillate up and down?

@Swift. Do you fly with all the SAS channels enabled, or have you made any mods to the FM lua? Do you use the "tap" or "hold" technique for FTR?

Not sure what you are seeing on your end, but when I replay your track, everything seems to work fine. Are you not seeing the display light up? Maybe a messed up .lua file in the displays folder? Are you able to launch chaff/flares, even though the display is dead?

We get the same thing in MP with humans in both seats. Under some conditions the TOF just isn’t there, then a few minutes later it’s back. This is with the CPG firing all the missiles.

This may be a limitation of your boat switch. If the center position of your switch is the OFF position, then you can't map a function to it. This is often designated on a 3-way rocker switch like: ON-OFF-ON, where the center position is not sending a signal you can use. You would need a boat switch that sends a signal when switched to the middle position, often designated ON-ON-ON, where each of the three positions is making a separate contact.

Yes, there is a solution for this. My controller was working with independent axis on the triggers since the day I bought it. Then one day, it all of a sudden went to a single "split axis" setup after a Windows Update or something. After doing much research, I found the answer... https://www.reddit.com/r/xbox/comments/qer8pv/xbox_controller_right_and_left_trigger_merged/ The old HID driver for the controller was 2-axis, then Microsoft pushed an updated XINPUT driver that changed the behavior of the triggers to be a single split-axis. You need to reinstall the driver for the controller from Device Manager, and when picking from the list, select the old "HID-compliant Game Controller" driver. Then you can map them as different functions with Joystick Gremlin, etc.

But Store does work in MP if you have a human PLT and human CPG. At least, it did for us last night...

I have multiple layers of commands bound with modifiers on my XBox controller and cyclic and collective. Are you saying you have them double-bound to both your XBox controller and HOTAS? That should work with momentary buttons, but probably not toggle switches and axis.

And this was the one I was thinking of. Not sure how helpful it will be over the official manual. https://www.digitalcombatsimulator.com/en/files/3321891/

There was somebody that wrote up a procedural checklist for engaging with missiles a while back. Not sure how easy it will be to find, or if it is still accurate. Let me see if I can find it...

Just hypothesizing here, but maybe there is a technical reason why the center of the IHADSS has to be coincident with the center of the camera, i.e. the center of the rendered view? Being able to arbitrarily move the HUD around independent of the actual camera sounds like it would present all kinds of issues.

I believe it was a one-time event that has already taken place.

I thought the double rendering was an issue with the TEDAC only, no? I'm not seeing it on the left and right MPDs here.