• VOR radials are true tracks instead of magnetic


    kmax59
    • Status: Pending

      717 Version: 1.1.0.0

      System Category: Radio

      Minidump: https://forums.tfdidesign.com/uploads/

    Hi,

    While trying to perform some VOR/DME approaches in Australia, I realized that VOR Rads are actually true radials instead of magnetic.
    It should obviously be set as magnetic radials as VOR are supposed to be aligned to the magnetic north.

    For now, this makes the 717 unflyable on VOR/DME approaches so I hope we can expect an update at some point.

    VOR issue.JPG

    • Like 1


    User Feedback

    Recommended Comments

    This has been an ongoing discussion for a bit - our reference has provided inconclusive results. Traditionally, a "radial" is true, not magnetic, hence our code displaying it that way.

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, turbofandude said:

    This has been an ongoing discussion for a bit - our reference has provided inconclusive results. Traditionally, a "radial" is true, not magnetic, hence our code displaying it that way.

    Well, this is wrong. A VOR is set according to the magnetic north, a radial  from a vor must be magnetic or the reading is completely false.

    Can you imagine an airline pilot converting a VOR magnetic radial from his charts to true in order to perform a VOR approach properly?

    I guess (I hope) the tfdi team has some basic aviation knowledge, VOR radials being magnetic is one. I just can’t believe an aircraft development team does not know that. Pardon me the way I’m answering, but how on earth is it possible to still getting such mistakes/issues 2 years after the initial release? How on earth can we be left with mistakes like this on an airliner which is supposed to be complete with advanced systems? How can we be answered 3 months after a report for such a huge mistake? It really sounds unbelievable for me for an aircraft of that price. Initially we could say it’s okay you’re a small and young team, but 2 years after the release and a silent support now let’s start to do something please.

    I hope this will be fixed soon, at least I got an answer almost 3 month after my report.

    Quite unhappy how we’ve been left with such issues for months without any word from you guys, feeling like the 717 is becoming an abandonware. Hope you’ll show us it’s not.

    Edited by kmax59

    Share this comment


    Link to comment
    Share on other sites

    We put nearly in full time work, 5 days a week, for almost two years after the product was released. We also did not charge for the P3Dv4 version (which required work) or any of the work we've done since (it was a lot). So, although I understand your frustration, please keep that in mind.

    As big of a deal as this may seem to you, it is, overall, a smaller issue to resolve, technically, hence the slowness. We are also working on a decent size update (aimed for release this month), you can track its progress here: 

    .I've added this to the list of items that must be fixed before 1.1.1.0 can come out.

    • Like 1

    Share this comment


    Link to comment
    Share on other sites

    Hello @turbofandude

    Thanks for the quick answer.

    I am totally aware of what you said, however I've never had the feeling this product was ever fully completed (and I guess I'm happy I didn't have to buy a P3Dv4 version as far as it's still crashing). Being in the development as well, I didn't want to put pressure on you with my previous message, it's just that waiting 3 months to hear that you had a wrong idea of how is working a VOR is very frustrating, if not a little funny. I hope you can keep in mind that answering a customer 3 months after his message is quite unacceptable.

    Now, I'm glad that you're still working on solving issues, we just only didn't know, communication/support is half of a product in the simulation world.
    And yes, having a correct VOR reading is important for non-precision approaches, and I'm amazed (not to say afraid) nobody actually reported this before.

    There is no big deal for me, an issue which is not supposed to be there and that prevent the product to be used as it should must be fixed, for me and all the other users who paid and deserves to get what they paid for. If I got an answer earlier, I would not have reacted this way.

    Looking forward to the next version, with the hope the views switch crash will finally have disappeared.

    Thanks,
    Maxime

    Edited by kmax59

    Share this comment


    Link to comment
    Share on other sites

    Thank you Colin for the update,

    Yes this is how it should work :) 
    Take the time you need, as long as we know it's still being improved.

    I've been quite harsh previously and feel sorry as I know you're definitely not bad guys, so now that I've complained a bit and because if it's normal to say what's wrong, it's also normal to say what's great:
    Despites the issues it has here and there, this 717 is one of the most immersive aircraft currently existing, it has a lot of potential and if you bring it where it deserves to, it will be a fantastic add-on.

    Edited by kmax59

    Share this comment


    Link to comment
    Share on other sites


    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now