• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

WT GNS Still unusable

Scheduled Pinned Locked Moved Piston & Turbine Dukes
6 Posts 4 Posters 384 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    SomeoneCalledRay
    wrote on last edited by
    #1

    I implemented the existing fix on the GNS back before the Dukes were released so I could fly the TBM850 with the GNS530.

    I did this for both GPS units (530 and 430), and it fixed the issue on the TBM entirely - before implementing the fix, the HDG/NAV modes wouldn't engage at all and the AP was entirely unusable.

    Now, with the Dukes, even after the fix, I still cannot use the GNS in the Turbine Duke (haven't tried in the Piston). NAV mode on the Century IV arms, but does not engage (HDG and NAV both illuminated) even directly on the SID that I'd programmed into the GNS430.

    Absolutely 0 way of getting it to engage. I don't blame Black Square for this as it's a known issue, but I'd really like to use the GNS430 and I'd like to know if there's another fix or anything that can be used to get these working. I should note, my sim seems to be totally fricked, default LNAV seems to do orbits for no reason at all in other aircraft.

    On a side note, well done to everyone who contributed to these wonderful aircraft, absolutely amazing job :)

    Oh, and one more thing, anyone know if the TBM will be getting KLN-90B integration in the future? That thing is awesome.

    1 Reply Last reply
    0
  • B Offline
    B Offline
    Bert Pieke
    wrote on last edited by
    #2

    According to the installation notes, you have to reply YES when asked if you are on SU15 Beta if you have patched the GNS.. Did you do that?

    S 1 Reply Last reply
    0
  • S Offline
    S Offline
    SomeoneCalledRay
    replied to Bert Pieke on last edited by
    #3

    @Bert-Pieke Yes. It appears the same issue is now happening with the PMS50 GTN650.

    1 Reply Last reply
    0
  • Nicotine70N Offline
    Nicotine70N Offline
    Nicotine70
    wrote on last edited by Nicotine70
    #4

    I tried on my end, gns430 with KX155 was working fine, could you screenshot your WT430.js (and why not the WT530.js) at the place where you applied the fix to verify everything is in place ? maybe a conflicting mode ?

    just in case, I think the SU15 is planned for the following days, so maybe this will improve the situation on your end
    (from last msfs development update)
    43c8b93c-b69a-421f-ad3c-1f961dc458df-image.png

    1 Reply Last reply
    0
  • S Offline
    S Offline
    SomeoneCalledRay
    wrote on last edited by
    #5

    So I got the GTN working, haven't retried the GNS because couldn't be bothered, but I had a weird issue today where no lateral modes apart from heading were engaging (pressing buttons, etc).

    I'll post about this shortly.

    J 1 Reply Last reply
    0
  • J Offline
    J Offline
    jmarkows
    replied to SomeoneCalledRay on last edited by
    #6

    @SomeoneCalledRay said in WT GNS Still unusable:

    So I got the GTN working, haven't retried the GNS because couldn't be bothered, but I had a weird issue today where no lateral modes apart from heading were engaging (pressing buttons, etc).

    I'll post about this shortly.

    I just had I think the same issue. Only heading would engage, and once it went into Alt, subsequently pressing Att would remain in Alt and level off at the current altitude.

    I think it was my first flight after updating to SU15, and restarting from the runway instead of cold and dark for a quick test worked OK.

    What ended up happening with you?

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users