I've updated the B707 V-One gauge with more sounds and functions!

Now available in the Avsim library, search for: V-One Gauge for Boeing 707-300 Complete

List of features: New Items/Features in 'blue'.

• Twenty-Two call-outs sounds integrated into gauge (15 new call-outs).
• Take-off V-Speeds calculated for Flaps 14 with temperature and altitude adjustments.
• Take-off speed bugs automatically set for: V1, VR, V2.
• Flaps-up maneuvering speed (clean speed) bug set after flaps-up.
• Optimum altitude and optimum EPR (EPR calc for M.80) are continually calculated.
• Gross Weight overage will display in 'red' text. Tooltip indicates overweight value (LB/KG).
• Take-off trim calculated for current gross weight.
• Display units can be toggled between LB and KG (default LB).
• Outside Air Temperature can be toggle between Fahrenheit and Celsius.
• Resettable fuel use.
• Resettable flight timer.
• Selectable Vref landing configurations, Vref40 (default) or Vref50.
• Approach / landing speed bugs automatically set for: Vref, Vref + 5, Vref + 10.
• ZFW, Fuel, CG, Gross Weight and Barometric Pressure MSL (QNH) displayed.
• 'Barometer Set' call-out occurs when pressing keyboard letter 'B' (V-One gauge must be open).
• Decision Height adjustment now on Data Card in hidden click-spot located on upper right corner.
• Now installation to a single location will work for all variants.

Thanks very much for this, Paul! I now have the complete set with the '27, '37 and your gauge for this one made me buy it just so I could use the gauge

Adding a note. The readme speaks of.
Quote:

Now the default value is -9, 0, 0, so you could delete that '-' when it comes to the instructions. However, this seems to mix up the stab trim recommendation (and the flight model) a bit and e.g. returns trim values like 15.4.

By this, I'd say that sticking to the default value with the -9 seems appropriate. I could be misunderstanding something here, but only the default value ensured proper trim recommendations for me so far.

BrianG wrote on Mar 7^th, 2013 at 8:29pm:

You are right, the OPT value is for cruise. You can find the rw TO and CL values in a package over at Avsim. 707perf.zip by Matt Zagoren offers some docs which include the thrust tables.

I don't know if they relate perfectly to the sim's flight model, but you'll receive an overview for sure. If you use the TO value first and the 'rated thrust' one for the climb, you should be ok when it comes to the shortened rw docs.  

I think the -9 value instead of the (+)9 could be a sort of typo. Reason is that the -9 value leads to trim recommendations not being achievable or just on the very edge to it like e.g. '15.0', while the default (+)9 value renders them correct.

The VC indicator may not be the best reference but that green band is the one showing a proper trim (range) for TO. Outside of it, the TO warning horn should sound when advancing the #3 thrust lever. And the mentioned '15.0' is well outside of it, hence my note. On another note. The CS707 1.3 warning horn is inop.  

Well, I could be totally wrong since those findings just arise from observation and I may even be using an improper payload layout. Funny thing is that I've actually missed that small minus sign all the time when reading the readme. It was just lately, with the new mod version, when I finally realized that it has to to be added when following the instructions one by one.   That's just to explain why I didn't chime in sooner.

In the end, there's a chance that both values are, somehow, wrong. The default one being too far aft forward and the correction then being an over-correction. So just read the note on the +/-9 value as a starting point for the tests you've ran. Thanks for that input by the way.

To avoid mixups, we may stick to one plane model at a time and perhaps keep in mind that the FSX coordinates we are talking about always refer to a (fictional) reference point of the 3D model. Well, if I got that right. http://msdn.microsoft.com/en-us/library/cc526949.aspx#datumreferencepoint

There are a ton of factors within the aircraft and air files to allow for the setup of the actual flight model, so my focus on just receiving proper trim recommendations is just that. A focus. I think the current 707 FDE would allow for some more improvements to be honest. I could also think of Paul running into this or that limitation when setting up his gauge not aiming at improving the FDE but 'only' at allowing the users a nice and comfortable usage of the proper v speeds and things. Just pointing out that a future FDE mod like e.g. Michael2 did on the 727 would be very welcome.   I guess we agree.

Such a thing would also help to achieve the EPR readings from the rw docs but we both have to ask openly about how many folks really need/appreciate such details. You surely would, me too.