Well before the update the HSI would also capture the glide slope. Lets see what carenado fixes.
For RNAV approaches as well? Thatās my question. I did say it was broken, it should clearly work for ILSās (VLOC) and does not. The issue with RNAV would be is the GPS certified for vertical guidance on its own without external reference?
Hi,
i bought this plane as well and brakes take a long time to stop it. I use the rudder pedal and i tried to play with the sensitivity but no way. any suggestion ?
Thanks in advance
Claudio
Ah sorry I should have read your whole post above. I will do some research since I am not sure about RNAV.
The question in order to help you with this would beā¦ whatās a long time to you?
How fast are you going when you apply the brakes, and how long does it take to stop?
The Warrior I rent, yeah, too me, it takes a long time to slow down once Iāve landed. Granted, part of that is I donāt want to stand on them and burn them to a crisp. But even then it would still be pretty far. I havenāt noticed it being long when Iāve flown the Seminole, itās seemed about right to me, but, Iāve never flown a Seminole in real life, so I canāt say what it should be or give you actual numbers to expect.
First of all thanks for answering.
I notice this problem with the M20 Ovation as well. I am not able to answer you with figures but ihave been flying with P3d For a long time and with similar GA aicraft i never had this feeling and that is why i notice the difference.there are no parameters to increse the strenght of the brakes as far as i know.
As I said, to me, braking power is about right as Iād expect it in MSFS.
Thereās a new update just released for the PA44:
2 Likes
Ah, if only for the Mooney. Still needs some FPS lights performance adjustments.
Just doing a quick testā¦HSI doesnt work with GPS here 
Did a quick test, nav2 obs-ring now working , but the autopilot did a 90Ā° degree bank and trim full forward directly after activation, HDG mode onlyā¦ anybody knows if thatās a carenado thing or does it affect default planes as well?
And both the Mooney and the 182T need to be adjusted to be VR compatible. I mean, they work, but theyāre not VR enhanced. Iāve been so heads down trying to get my fps in VR in general tweaked, I havenāt been able to even think about different aircraft issues. But last time I did, yeah, the Mooney needed some performance tweaks compared to others. Hell, even the Twin G1000 Baron had (has?) better performance.
1 Like
My download failed, but if the same happens to you (the reader, not just you @EvidencePlz), just delete the folder in file manager (/me/AppData/Roaming/Microsoft Flight Simulator/Packages/Official/Steam/carenado-aircraft-pa44-seminole) and reinstall the whole aircraft in content manager from scratch, easy peasy.
The HSI appears fixed (though I had only a short flight with a self vectored ILS approach), as does the OBS for NAV2. I didnāt have time to check it for full proper operation, but initial impression looks good.
They also published updates for the payware KEYW and KPCM.
So kudos to Carenado for getting those fixed, and to MS/Asobo for getting them published in (hopefully, anyway) a quick manner. But I do have to say that Carenado REALLY needs to work on their communication skills with customers, I didnāt even know this was coming until it was here. Iāve got freeware makers who communicate better, right here on this very board!
EDIT: The GS needle (well, pointer really) sometimes disappears from view in VR (at least in mine) but Iām not sure who to point the finger at for that little gem of an issue.
1 Like
@Grinde81, I think itās a Carenado thing, but itās not the autopilot, thatās just doing what itās told. Itās being given bad instructions from the FMS/GPS, though Iām not clear why.
Also, if youāre still using the default Asobo GNS530, I recommend the mod by @ScorpionFilm422 available here. It helps tremendously with those autopilot issues that arenāt really autopilot issues.
2 Likes
Thanks for the extensive testing and feedback.
What about @FlyingFinusās observation that HSI is still not working or getting coupled with GPS? Did you test that too by any chance?
@EvidencePlz, no I just manually input and flew an ILS with no ATC/AP assistance, so I didnāt test that. But Iām about to, gonna fly from KORL to either KGNV, KCRG, or KTLH, havenāt decided which yet, but they all have ILSs (well Iām not certain about Craig, but the others do for sure), and Iāll be on an IFR flight plan, so then Iāll know.
I went and violated the TFR (thatās been in effect for years, so the āTā seems questionable at this point) and altitude regs to do some flightseeing around the Magic Kingdom (which I finally managed to find, after several days of looking) before my self-proscribed ILS in the PA44. But as a general rule, thatās not the worldās best flightseeing aircraft. #Themoreyouknow
Now if I could just find that ā ā ā ā crater out in Arizona! Itās not even marked as a POI, or if it is, I must be looking in the wrong places.
EDIT: @moderators, the word ādā āaā āmā ānā is not considered profane anymore. Back in the 1920s maybe, but weāre in the 2020s.
1 Like
@EvidencePlz, and everyone else who is interested, I did my test flight and here are my findings.
I flew from KORL to KTLH in daylight, real weather conditions. (In reality it was night, but I didnāt want the darkness hindering me.) I flew on autopilot from 1000ā after takeoff to 200ā AGL before touchdown. The only hitch was a 360Ā° turn caused by ATC giving my my approach a little late, and me entering it in a little late because I had the headset off at the time. That resulted in me passing the initial approach fix by a few miles, but that 360 fixed the issue, which in any event was not caused by anything Carenado did.
Aside from that, the GPS coupling with the autopilot and HSI worked perfectly, as did the HSI itself, at least as far as Iām qualified to say, as I donāt have any RL experience with it to see a flaw that I donāt know exists.
The GPS/Autopilot/HSI also captured the glideslope perfectly, though either ATC should have given me a descent they didnāt, or the approach plate (which I didnāt have because I canāt see Navigraph in VR) would have mandated after approach clearance had been received, so I had to do a steep descent from above the glideslope to below it, that was then properly captured.
My conclusion, therefore, is that the HSI performed flawlessly, as did the coupling system from top to bottom.
Next, the NAV2 OBS worked as it should, except the on/off flags and to/from indicator. But the OBS itself indicated as it should when the CDI indicator was set properly. Thereās a little more work that Carenado needs to do on that instrument.
Finally, VR caused a few issues as I previously noted, but I still cannot make any conclusion of who is to āblameā (if anyone) for the issue. It revolved around visibility of the GS indicator (and the top and bottom orange ticks, and the lights on the radio panel) that disappear at certain head angles. I canāt even say with any certainty if this is a limitation of our current VR HMD hardware technology, or something that can be fixed with software, either from device drivers, or from the applications themselves, or even potentially both.
Anyway, thereās my overly wordy analysis. Carenado still needs a little work on OBS2, and if itās possible, someone needs to figure out how to make light sources not disappear from view inside a VR HMD. Carenadoās job seems relatively simple, the VR issue is somewhere in between simple and impossible, but Iām not qualified to comment any further than I already have.
Now where do I send my bill to?
2 Likes
Very detailed, thorough report. Thank you 
As for the OBS on/off flags and to/from indicator, Iām going to test it myself and ask around a bit to see if another batch of zendesk reports needs to be dispatched. Really happy to see Carenado is apparently upping their game and listening to feedbacks.
As for VR, Iāll look around in AVSIM a bit and let you know if others are having similar issue and found a workaround.
1 Like
Okey after I read your post I reinstalled the PA44 completely.
Unfortunately nothing changed the wrong HSI behavior but I figured out what might be the difference here. When using the AP in NAV mode and selecting GPS as the source the AP will follow the programmed route even tho the HSI does not display the lateral deviation to the route. If you select a usable VOR without selecting VLOC the CDI will only display the deviation to selected radial.
Seems like Carenado did not fixed it completely.
Maybe you can varifey that this also happens with your plane? If so I would write a new ticket at the carenado support.
1 Like