PacFlyer23

Update:
Well thanks to everyone for trying to help me with this issue. I ended up pulling the GPU (4070 Super) and sending it to Gigabyte to check. They reported back it was fine, and advised the sort of problem I was seeing could be due to issues with the MB or Power Supply. A little backstory is had replace the PC's original 4070 with a 4070 Super over a year ago - and I just have to wonder if the tech that did the install hooked it up wrong.  So I just decided to punt and get a whole new system. It arrived two weeks ago and I've been getting it up and running. I went with a little more higher end PC setup  - AMD 9800X3D and NV 5070 Ti, with 64GB. I'm not a PC person, but it hasn't been too challenging. I have been surprised by the amount of "muscle" memory on flying the F/A-18 that I've lost in a month of downtime... like remembering that the TP laser needs to be reset after each LGB drop... did a 90 minute training mission last night and I have no idea where that second GBU-12 ended up  🙂

Okay, I got it.
I turned off just the right DDI.
Then launched TrackIR and it opened in the main display as normal. 
I then closed TrackIR, and turned back on the right DDI.
With all monitors on, I launched TrackIR and it opened in the correct main display.

With some additional guidance I've got it fixed. DCS had me rename just the "Config" folder. I also copied my "Input" folder with my AC cockpit control layouts/key bindings from the old "Config" folder and put it into the new "Config" folder once DSC had created it. A little bit of going in and out of DCS to check things... some game settings (display, gameplay, etc) got reset too. 
Rather strange this all happened, but glad for the help here and DCS tech getting it fixed. 

Yes, holding the switch to Elect works but it turns out you have to be on full APU power and not battery. Also, I've not seen this action noted in any of the various A-10C checklists folks have created over the years, so it seems like a change.
Thanks. 

I just did a restart of my pc and the issue has gone away. 
I wonder if the initial stuttering could be caused by the fxo and metashaders going through their rebuild the first time after being deleted.