Good evening all;

So, I've been flying the 727 for awhile and my landing approaches have been consistently "high".  I suspected a problem with the VSI because I still had problems getting down the glidepath, even with a descent rate of -1000FPM.

I installed a default Cessna-172 gauge to check against, and found they were different...the 727 gauge overstated the descent rate by -250 FPM.  This explained my high approaches.

To make sure, I then opened up the "L11_vsi" xml gauge (in cab file Captain_Sim.p721.L11) and placed a compass rose over the background bitmap.  I found that the angular measurements in the "nonlinearity table" were wrong by ~10 degrees or so.  I edited the gauge with 'notepad' so that the "Nonlinearity table" looked like this:

            <NonlinearityTable id="NonlinearityTable">
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>-6.000</ExpressionResult>
                                   <Degrees>10</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>-4.000</ExpressionResult>
                                   <Degrees>50</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>-2.000</ExpressionResult>
                                   <Degrees>100</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>-1.000</ExpressionResult>
                                   <Degrees>135</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>-0.500</ExpressionResult>
                                   <Degrees>155</Degrees>
                   </NonlinearityEntry>
                             <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>0.000</ExpressionResult>
                                   <Degrees>180</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>0.500</ExpressionResult>
                                   <Degrees>205</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>1.000</ExpressionResult>
                                   <Degrees>225</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>2.000</ExpressionResult>
                                   <Degrees>260</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>4.000</ExpressionResult>
                                   <Degrees>310</Degrees>
                   </NonlinearityEntry>
                   <NonlinearityEntry id="NonlinearityEntry">
                       <ExpressionResult>6.000</ExpressionResult>
                                   <Degrees>350</Degrees>
                   </NonlinearityEntry>
            </NonlinearityTable>

I've submitted a ticket so hopefully this can make it into the next update.  CaptainSim, I can put the gauge in my MediaFire folder for you to download if you like.