Floyd1212

Try setting a dead zone of 4 on that axis. this was an early bug with the cursor getting stuck on the edge of the screens. The dead zone seems to help.

I am exporting Left and Right MFCDs (but not TEDAC) and am able to join the Hoggit GAW server, which requires pure clients. The only thing I see that is different from your lua vs mine is that I have the exports defined first, then the "Viewports" defined after. You might try flipping those around in yours.

A screenshot would be very helpful here. Press the "PrntScr" button on your keyboard, and go find the screenshot in the C:\Users\<username>\Saved Games\DCS.openbeta\ScreenShots folder. Maybe you were in Hover/Bob-Up symbology mode?

I find being able to slave the TADS to the GHS very useful. Lets me keep my head up until I see something interesting, then slave to it and put your head down for closer examination. Dimming the video overlay down is the way to go, in my opinion.

Press LALT+Y to cycle through the different coordinate types. Also, there’s a utility called “The Way” that will automate transferring multiple points from the F10 map into the TSD. It is handy for setting up waypoints in NAV mode, then clear those out and setup some TGT points in ATTACK mode.

Does that “purposes” section enable display exports to stay live when looking at an external view, like F2?

It should work. That sounds like the error you get when the missionscripting.lua hasn’t been properly setup for persistence saves. Did you follow the steps for modifying that file?

Double check and make sure you don’t have another controller that defaulted an axis to pedals or cyclic. That seems to happen on occasion when a patch is applied. You can also try changing your trimming mode to Central or Instant for a test run, to see if it behaves as it should.

Great read. Thanks for taking the time to put this together.

In my example with the screenshot above, where it missed 5 out of 6 times, I did have the LRFD set to LAST.

I was also experiencing this on the Syria map where the tree density is lower than it is on Caucasus, for example, and the target was getting "lost" as it went behind every individual tree.

Just for comparison, I loaded up the Syria hot start Instant Action mission and timed it. The progress bar was on "World Preload : 1/60" for 25 seconds, with a total load time before seeing the world behind the mission briefing of 1m 25s. That in itself is not very helpful, since everyone's hardware specs are a little different, but it is to say that this issue is not effecting everyone across the board. So now the question is what setting or mod is causing the issue?

I tried your track and resumed control and was able to engage ATT Hold. I did trim first, which is my usual procedure, so if that is now a requirement, that might explain it.

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.