Floyd1212

Was that missile you were trying to fire actually there on the rail? Maybe something got out of sync and that missile was actually gone, or maybe you took damage to that wing/pylon? In that scenario, I would have jettisoned the stores on that pylon which would have forced the aircraft to move on to another missile. Just a thought.

Good alternative for VR users. The Way seems to be a little more automated, but only works for 2D users because of the way it registers the center of the screen for the value of the coordinates to copy.

Sorry, I just realized this thread was originally about ATT Hold, and my comment above was about ALT Hold.

I hadn't run into this myself until tonight. I'm using Central Position Trimmer (not using FFB), but I wasn't able to engage ALT hold. I was at a dead hover with ATT Hold engaged, and a stable altitude, making fine adjustments to the collective, and ALT Hold would not engage. Then I realized I was at 101% torque (boxed) to maintain that hover. I was able to drop my collective to reduce torque to 98% (or wherever the box goes away), and I was then able to engage ALT Hold. It soon disengaged itself when it tried to raise the torque again to maintain that altitude, but it worked briefly. Might be unrelated to the issue mentioned above with FFB mode, but thought I would share that revelation.

Are you living in the same house? Shouldn't need to mess with your router if you are on the same network in the same household.

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.