Figured how to correct the display so here are the configuration parameters for those interested. Being a swing wing I’ll leave the location of the under wing ordinance to you. I’ve set mine up with the wings at the 16 Deg position (swept back).

In the panel.cfg file under the [Vcockpit02] routine edit the gauge00 line to look like this:-

//gauge00=Virtavia_F-111!HUD,            25,22,537,508
gauge00=CSWeapon!hud3d,                  77,60,450,450


In the csweapons.xml file replace the <GaugeInfo> routine with this:-

   <GaugeInfo>
       <!-- gau section -->
       <AntiAlias2d>1</AntiAlias2d>
       <!-- 2D HUD anti-aliasing. 1-yes, 0-no (1).  0 increases performance.  -->
       <AntiAlias3d>1</AntiAlias3d>
       <!-- VC HUD anti-aliasing. 1-yes, 0-no (1).  0 increases performance.  -->
       <HudFov2d>10.37</HudFov2d>
       <!-- 2d HUD field of view. Degrees -->
       <HudFov3d>-17.00</HudFov3d>
       <!-- vc HUD field of view. Degrees // A negative value in this case-->
       <CollimationData>-1.05,7.0,2.30,2.42</CollimationData>
       <!-- see SDK =====  // x,y,z,Radius-->
       <EyePtDeltaRatio>0.8</EyePtDeltaRatio>
       <!-- hud acceleration sensetivity factor -->
       <Collimate>1</Collimate>
       <!-- VC HUD collimation. 1-yes, 0-no (1). -->
       <TestFrame>0</TestFrame>
       <!-- HUD test pattern. 1-yes, 0-no (0). -->
   </GaugeInfo>

You’ll find if the Test Frame is active the circle and square are clipped, makes the display slightly bigger but still central. If you want to set it up by the book change the last value in CollimatorData to 2.58