Abandonware?
Otherwise, it’s a great plane to fly. For me at least.
WT GNS 530 uninstalled, no more issues.
Can anyone else confirm removing the Working Title GNS - the bridge version that temporarily helps third party plane makers - solves this issue?
I confirmed it in my previous post, on Sept 22, with video.
Frustrating that this is still an issue. Please uninstall the GPS that probably has thousands of hours poured in to it’s development. Or the “shim” at least.
I’m having similar issues with the altitude selector as well. I followed the steps on how to use the altitude selector, but whenever I press the ARM button it levels the aircraft off immediately instead of leveling off at the selected altitude. If I don’t press the ARM button, the plane will continue the climb or descent through the selected altitude.
If you have the WT GNS 430/530 installed the AP behaves differently. Until Carenado fix it this process will work.
- Dial in the target altitude.
- Press ARM
- Press ENG
- Click the Pull V/S dial
- Dial in target V/S
This consistently works for me.
Thank you. That works for me too. It doesn’t turn the ARM light on, but it works properly, which is what I want.
Yes, not the ideal solution, but the alternative is a lower fidelity Garmin unit. So for me personally I’ll live with this workaround.
I have been working through a bug report with Carenado, and they said will work on a fix for the next version of this aircraft
That is welcome news.
On the other hand it’s totally unacceptable that it took your reaching out to them when this bug was reported in March of 2023.
Why didn’t Microsoft report this to Carenado and initiate the fixes months ago?
What are we even doing reporting these then?
Is Microsoft a bug collector rather than a bug exterminator? I’m confused here.
If I had to bet, I’d say it ended up in their big bug ingestion system as a low priority item and no one is responsible for coordinating the bug fixes on these products (or the person responsible is underwater with something else).
They won’t tell us these details externally, which makes it hard to know what’s even going on.
I believe this bug was first reported to Microsoft. As they have many bugs to work on, this one was not priority. I ended up doing a bug report with Carenado since it was a joint Microsoft/Carenado aircraft. Carenado was not aware of this issue on it until I told them it was a problem with the WT GNS 430/530.
I just saw this pop up and thought I’d chime in. It does do that 99900 thing for me. So I just started controlling it with PMS50’s GTN750. It works perfectly with that. I know this isn’t the answer people want, but supposing it’s continually ignored - well, I have a solution at least to those who own that very handy device.
That is simply ridiculous.
This bug is nearly a year old. All Microsoft had to do was pass this on to them. They didn’t have to try to fix it themselves.
Man, that is just unreal discouraging.
What is the point of all my effort here spending time recreating bugs, making videos, and carefully writing up detailed information about issues if MS isn’t even going to pass this information on to the developers?
Do you have the same issue if you follow the OP’s steps to reproduce it?
yes
Provide extra information to complete the original description of the issue:
alt preselect arm indicator does not light up upon pressing the arm button. Functionality seems random. Pressing alt hold sets altitude at 99,000 ft. Turning the dial sets it to 50000 ft. AP will ascend/descend through preselected supposedly armed altitude (no way to know for sure since the indicator wont light up)
If relevant, provide additional screenshots/video:
Any update news from Carenado?
They said they were going to fix it, but I haven’t noticed any changes. I haven’t used the V35 in a bit though, so they may have updated it since then.
I’ve had my eye on the issue for a long time and I have not seen an update for this yet.
I hope the Microsoft flight simulator 2024 aviator edition launch will correct this bug.