First, somehow, I made an ILS landing. Honestly, I have little to no idea exactly how but I have a short flight (Fredricktown MO to Cape Girardeau MO) that I can do over and over and at least find the solution by trial and error.
BUG:
Tool tips are available obviously to aid the user. I cannot get the tool tip for APR mode button in the TBM to display anything but “OFF”. Man, that threw me for a while and a lot of wasted time trying to deal with all the other new items in AAU1 update.
END BUG
QUESTION: (in response to OP’s original post in case anyone needs reminding)
On my flight plan where I successfully did an ILS landing, I eliminated a bunch of extranious stuff that got thrown in from the world map I guess. However, after eliminating all that, the flight display seemed to show an extra leg to the west. The flight plan that’s displayed and the VFR map match up. The flight display has that extra leg which isn’t anywhere and was never used. It’s like some of what I eliminated in the flight plan never came off the map or something. Is this a bug? Very confusing.
The huge changes makes it difficult to determine (those of us that are casual “flyers”) if something is now “real world” or a bug. Which is this?
EDIT: This appears to be the start of the leg which was away from the airport. Rather than hand fly to that endpoint or whatever it’s called, I did a Direct To (TANZI) so that’s what that little extra leg seems to be. It’s what I would have flown had I hand flown to that beginning point. Originally it was lit up in magenta but I did a Direct To (TANZI) and that unused leg stayed there. At least that’s what I’m understanding now through trial and error. Is this correct?
I was a bit confused to see that WT is providing PC-only added functionality to the TBM and Longitude PFDs. I can understand that was likely done for performance reasons, as even low-end PCs may have problems running the package. But it is somewhat worrying that we are increasingly seeing Xbox functionality separated from PC through the use of these “enhanced” packages from first-party developers.
I don’t want to see my fellow PC simmers throttled by Xbox performance limitations and also get that perhaps this release was done by WT separate from their work with Microsoft, but at some point this trend will call into question Jorg’s stated committment toward making both platforms act in sync with one another, at least from a first-party development perspective.
All the enhanced version does is add the independent pilot and copilot PFDs. A small feature that is by no means a deal breaker and something that the console version would no doubt struggle with. Xbox still has all the benefits of AAU1, while the enhanced package allows PC users to not have to miss out on something because of console limitations.
The enhanced package is the best possible solution, IMHO.
Yeah, it is not a huge feature, but I’m saying that we can’t have it both ways by arguing that the platforms are treated equally by MS and first party developers and yet quietly provide enhanced features to PC. Let’s just be clear about what’s going on there.
I found out on the Discord, which a very large portion of Xbox simmers do not frequent. As it wouldn’t be in the marketplace for them, either, and there hasn’t been a larger discussion on these enhanced packages, I stand by my characterization.
Edit: Maybe it’ll be in the marketplace update, so maybe folks will see it there.
Hi Folks,
Just like a miracle, all of a sudden the Garmin started working (first thing was seeing the RANGE function work). It took a while to learn the ins and outs, and it’s still a little flaky at times…the AP is inconsitent in its reliability…sometimes, for no good reason, the AP turns off and the plane starts to vear wildly. When it works, it’s ok. Hopefully it will get more reliable soon.
They can’t be treated evenly … There are Memory issues with trying to “retain” the additional screen. It is not that they don’t want to give everything to XBOX but rather they run into hardware limitations that just can not be overcome where you need more memory…
Fact is users with lower- mid end specs are not going to be able to run this without issues… and dont believe the hype when someone tells you they run on ULTRA with a i5-8700 and a 2060 super…
It seems my Cessna Longitude Enhanced install conflicts with my TBM930 Enhanced. Both planes use the Garmin G3000, what’s the difference found in the Content Manager.
Deleted the Longitude, keeping the TBM.
Enhanced, really I don’t know nothing what is this and if you want have some good advices, pls report better description. Generally, mix some 3-rd party addons especially aircraft mods is really road to hell and especially if Avionics update was released. If 3-rd party addon devs will not update their packages, more problems with no compatibility.
from his posts is clear that some 3-rd party aircarft addon mode is used and this can be that Enhanced word description. If you see his state, looks like he use also some other??? enhanced mode for Longtitude and it does conflict with his also Enhanced mode of TBM (also 3-rd party mod???). Really this need to be better described. Hope he will do. I don’t think so that WT G3000/5000 is here mentioned as problem but 3-rd party aircraft modes used together.
Thnx CasualClick heh now is clear that I was right ok thnx for clear description.
No, he just said he was using Enhanced mode - which is an Official Working Title update to the TBM and the Longitude. So it’s not third party.
Now, that doesn’t exclude the possibility of other mods being the problem. Which is why when I try to assist, I ask specific questions up front - like did you remove all other mods? This looks like a Livery issue - did you install one recently? Questions like that help focus on the potential root cause.
No you were wrong actually. The Enhanced thing he wrote about is official WT content and not third party like you thought. Go to the Merketplace and you will see them.
Does anyone know how VNAV is suppoed to work on the Longitude (Enhanced) when a hold occurs during descent?
I just flew a VNAV descent from FL450 to 3000ft with a hold at waypoint TUXEM during the descent, and that waypoint was designated to be ‘AT 7000ft’. (constraint no longer shown in screenshot)
When I reached TUXEM the plane correctly levelled off and flew the hold as desired at 7000ft. When I unsuspended the flightplan to continue the descent, that happened correctly too, with the descent resuming under VNAV.
So all good huh?
Apart from, during the hold, the VNAV constraint of 7000ft was no longer shown on PFD, with my manual contraint of 3000ft (for the next waypoint in the flightplan) still showing in green.
Surely the 7000ft whould still be shown at this time as the plane is very much still under VNAV control, with its constraints?
Anyone know what happens in the real plane and whether this is a buglet or real life implementation by Garmin.
I see no logic in hiding an active constraint at all.
See below. I’m in the hold. The plane is held at 7000ft by VNAV, but you would never know from the PFD ALT strip. Only at the top do you see V ALT 7000ft. I’d like to see a purple 7000 at the top of the ALT strip to better indicate what is going on.
If this is how it is in the real plane, then fine. Just seems like an omission.
ok thnx for clear description.