The ADI on the T-38A has a bank steering bar* that provides a visual cue on which direction to steer the a/c for an intercept.When in TACAN Mode and the Normal/Manual switch is in Manual position, the bank steering bar is visible and will provide a cue to steer based on the heading bug's position.The bank steering range limits are +/- 35º*Note: the bank steering bar looks like a yellow, vertical needle like one that's used for a flight director.The 3d "bank steering bar" is keyframe animated from frame 0 to frame 254, so the center point is frame 127.Here is the animation script for the bank steering bar for this specific mode:

    (L:T38_HSI_NormMan_Switch,bool)    (L:T38_HSI_SourceSwitch,enum) 0 == and    if{    25 (>L:T38_FD_VerticalBar,enum) <!-- Unhides bank steering bar -->    (A:PLANE HEADING DEGREES GYRO,degrees) (A:AUTOPILOT HEADING LOCK DIR, degrees) - 180 + (>L:HdgError,enum)      180 (L:HdgError,enum) - 35 <=      180 (L:HdgError,enum) - -35 >= and          if{ 180 (L:HdgError,enum) - 3.6285714 * 127 + (>L:Attitude_Bank_Steering,enum) }    }

It works quite well until the heading bug is set within the range of +/- 20º due North, when suddenly the computed (L:HdgError,enum) value goes "wonky" as a result of the wierd way that FSX "does the math"...Has anyone any suggestions on how to modify the formula to "unwonky" the computed heading error value?

Bill, Here is some code that I hacked from a Becker ZVG2002 (Radio Homing) gauge I made for someone. I'm assuming it works basically the same. The "difference" math is all done at the 180 side of the rose.. Ex. dnor s1 l1 270 > l1 90 < || if{ 180 } els{ 0 } - dnor I didnot test for your application, but the gauge I made does work.Hope this may help.Roman

    (L:T38_HSI_NormMan_Switch,bool)    (L:T38_HSI_SourceSwitch,enum) 0 == and    if{    25 (>L:T38_FD_VerticalBar,enum) <!-- Unhides bank steering bar -->    (A:AUTOPILOT HEADING LOCK DIR, degrees)   (A:PLANE HEADING DEGREES GYRO,degrees)  - dnor s1     l1 270 > l1 90 < || if{ 180 } els{ 0 } - dnor    180 - -35 max 35 min 35 + 3.6285714 * (>L:Attitude_Bank_Steering,enum)             }

Thanks, Roman! That works much better, although it does also show the HDG Bug's "reciprocal," which isn't something I want. :) I'll figure that part out though. Ideally the needle will "point the turn" to the closest angle from the reciprocal of the HDG Bug's index angle.Here's a screenshot of the T-38A's cockpit with TACAN channel 111X tuned, and the HDG "bank/turn direction needle" displayed, indicating approximately 25º left bank to intercept the HDG Bug at due north.Uploaded with ImageShack.us

Ahh, Yes.. I removed some code that takes care of just that. I had made 2 versions of the same ZVG gauge, a "Comparator" ( the one you need) and a "Reverse". ( the one you have now) Just a little mod should take care of it. Took me awhile to go over such an old gauge ( March of 2005 ), memory just not as good anymore :-)Original - l1 270 > l1 90 < || if{ 180 } els{ 0 } - dnorNew - l1 270 > l1 90 < or if{ 180 1 (>L:Reverse, bool) } els{ 0 0 (>L:Reverse, bool } - dnor On reverse bool = 1 just invert the value

(L:T38_HSI_NormMan_Switch,bool)    (L:T38_HSI_SourceSwitch,enum) 0 == and    if{    25 (>L:T38_FD_VerticalBar,enum) <!-- Unhides bank steering bar -->    (A:AUTOPILOT HEADING LOCK DIR, degrees)   (A:PLANE HEADING DEGREES GYRO,degrees)  - dnor s1      l1 270 > l1 90 < or if{ 180 1 (>L:Reverse, bool) } els{ 0 0 (>L:Reverse, bool } - dnor    180 - -35 max 35 min 35 + 3.6285714 * (L:Reverse, bool) if{ /-/ } (>L:Attitude_Bank_Steering,enum)             }

Will this project be publicly available at some time? Any Info? Been waiting for a replacement for the excellent FSD T-38 for a while. 1 of my favorite birds :-)BEAUTIFUL LOOKING PANEL!!!Hope this helps,Roman

Will this project be publicly available at some time? Any Info? Been waiting for a replacement for the excellent FSD T-38 for a while. 1 of my favorite birds :-)BEAUTIFUL LOOKING PANEL!!!Hope this helps,Roman

Something's not quite right with that, as the script just freezes the needle... I'll take a closer look tomorrow first thing in the morning when my brain isn't so over-cooked... ;)Yes, it has helped a lot to solve one of the last niggling issues with this project. So much so, that when it is released I'm going to gift you with your own copy.It is in the very final stages of a six month long alpha/beta cycle. We've been blessed with quite a few current and ex-military pilots who transitioned through the T-38A/C trainers, including two who were high-hour Instructor Pilots on the T-38A/C models!We're including no fewer than six liveries with the release, as well as seven customized air force bases and accompanying AI traffic (and reduced poly AI models to boot!). With any luck the final Release Candidate will be built by late next week for a final round of validation and "sanity" checks. Once all the team members sign off on it, she'll take off for the skies!Thanks for the kind words regarding the cockpit. The whole model is of the same high quality.

I'll take a closer look tomorrow first thing in the morning when my brain isn't so over-cooked... ;)

That can happen!I took a look at it this morning. Yes, 1 little syntax error, forgot a ")" was all. Anyhow that newest script didn't work either, as I fired up the testbed & tested. I believe I found a more elegant way, that works, which will port over to the ZVG also.. ( Just imagined a "virtual" steering bar LOL! )Basically, if the dnor'd subtraction of the HDG bug & Plane HDG falls on the left hand half of the rose, relevant to the plane heading, subtract 360 to give the negative result. On the right side the math is OK as is. Just the relevant part of the script --

(A:AUTOPILOT HEADING LOCK DIR, degrees) (A:PLANE HEADING DEGREES GYRO,degrees) - dnor s1 180 > l1 360 < and if{ l1 360 - } els{ l1 } -35 max 35 min 35 + 3.6285714 * (>L:Attitude_Bank_Steering,enum)

Hope this one takes care of it, rest your brain for a day LOL!Oh -- THANK-YOU!!!!!!! ,,,,, Kindly! Roman

Ah, poifect! Thanks a bunch Roman. I'm locking down the code/script development now and can move on to putting together the final Release Candidate v1.0 build for the team to put through the wringer!