Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

Round() function

edited February 2013 in Product Suggestions

Hi Steve,

Here's a little tricksy one for you. PMDG's JS41 Jetstream has a curious handing of the Autopilot Vertical Speed Target LVar (VSIASTarget) which can end up being 'non-hundreded' (i.e ends in a spurious ten or integer value). The LINDA scripts handle this on the display-output stage, by rounding the number to the nearest hundred (taking account of whether the VS value is negative or positive, and rounding in the right direction accordingly). The internal LVar quite clearly isn't strapped to a 'round hundred' value, though, and they don't seem to attempt to make it so - they just display it rounded.

In your app, there is currently no way to round up the actual LVar using any of the SET functions, so that's out - like LINDA, the LVar can (and will) wander the odd integer here or there (not sure why the plane does this, but it does happen, I've noticed). All we can do is what LINDA does, and increment or decrement it by 100 each click.

However, none of the display functions in your app will enable it to be displayed 'roundly', so you'll see odd VS targets like "-1302" or "02511" which is a little untidy.

What do you think? Is it worthwhile adding a display rounding function (which can take care of negative rounds correctly too)? Or am I missing something obvious? I tried messing with the multiplytruncate function (using 0.1) which kinda works, but only insofar as it strips off the last integer! It won't help with 'tens off', and of course, the displayed number is a factor of ten too small - which isn't ideal.

Apologies if you have enough to do already! ;)

Regards

Neil

Comments

  • edited November -1

    Hi Neil,

    No worries, adding features like that are quick and easy. Its tracking down the last few bugs that are consuming the little spare time I have at the moment.

    I'll add it to the list.

    Thanks

    Steve

  • edited November -1
    Respect! :D
  • edited November -1

    Hi Neil,

    This feature is now in the latest release (2.0.254.0). Let me know if its not what you were after!

    Best wishes

    Steve

  • edited November -1

    Brilliant, Steve - thanks. I'll test this as soon as possible and let you know! Cheers again

    Neil

Sign In or Register to comment.