Typically in order to get something looked on a MS-commissioned plane built by a Third Party, please open a Zendesk ticket.
Pls,
can you be kind again answer to my question, what hardware you mean in my quote section in previous post?
âŠIf no hardware is connectedâŠ
It is SimConnect hardware in the style of KAP-140 developed by myself like I wrote in this topic at 2.Jan. See here again Arduino Parts for Avionics and Cockpit controls. The SimConnect client is an c++ console application between the hardware and the SimConnect server inside the FS2020. The SimConnect client runs outside the FS.
1 Like
I have made a request at zendesk. The first answer was to read at the marketplace the contact information. But the written contact is zendesk. Now Iâm waiting for next reaction.
I have also discovered something strange if only ALT-HOLD and HDG-HOLD are activated in the V35-AP in the situation like before. Setting APR-HOLD is not possible. And even so the aircraft turns onto the directional beam. But the APR-HOLD variable (read back) is not set at this point. At some time later, when the aircraft has already turned in, APR-HOLD then can be activated.
In all fairness to the OP, I have seen this happen once so far, and only after the 1.29.30.0
Prior to that, I had done almost 100 Rnav 01 approaches into KDCA ( one of many test flight used while developing the Wb-SIM C172), and the AP has always, prior to 1.29.30.0 followed the Nvav GS down to the runway.
The 1st time did NOT do this correctly this flight since the 1.29.30.0 - I was surprised to see it NOT descend on the GS.
But on further flights yesterday, it did descend correctly 100% of the time, so I am unable to provide a reproducible test procedure to show this issue.
But it defiantly did not lock onto the GS that 1st time.
(and yes, I was at the correct altitude, at the correct point in the approach, for it to lock onto the GS, as it always has done in the past)
This is not the first function in MSFS that seems to just not work Occasionally, but does âmost of the timeâ, without any obvious reason (or a reason not yest determined).
In a word - lack of âSTABILITYâ, which has plagued MSFS since release date. but hardly surprising, as MSFS is so complex, and might still have many âGhosts in the Machineâ, inherited from the conversion from FSX ?
Zendesk has moved the problem to Carenado. The first reply from Carenado came:
" We will check it.
That update broke many navigations things in the simulator."
Do you have the same issue if you follow the OPâs steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
I find that the waas/LPV approach fails by not following the GPS specified path (the magenta line on the MFD map view). Furthermore, TOD does not appear on the MFD map view and the aircraft (DA-62) does not auto descend when approaching the airport. Prior to this most recent update waas/LPV approaches worked every time. Now, waas/LPV approaches fail very time.
I am sure they will check it â one day, maybe years from now.
Sorry, I have no faith in a statement of âWe will check itâ from Carenado, based in past history of such situations.
One of many reasons why I will never buy another Carenado plane, and the ones I have puchased in the past, are now all in the Aircraft Graveyard, because they interact & interfere with other non Carenado planes ( base sim modifications).
My choice, and I am happy with my own decision⊠your mileage may vary..
So far there has been no progress on my request. The non-compliant programmed AS530 still exists.
So I still fly, when I fly with MS2020, with the workaround as I wrote on 04.01.2023 - i.e. without AS530 in the panel.
However, because of the miserable support, I have lost interest in programming hardware for the MS2020.
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:
Autopilots NAV systems on planes stopped working 2 updates back. Now Autopilots seem totally broke on last update.
If relevant, provide additional screenshots/video:
It seems that the developer of the GNS530 are very ignorant to the SimConnect functions, that are published at the FligftSim pages:
Do you have the same issue if you follow the OPâs steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
So yesterday. A bug just showed up where I turned on, other pilot, the master switch, and it wonât stay on in any of the aircraft. No update that I can see that could change this. The orange change of about my setup is I add another stream deck. To my setup. Thatâs the only thing that has changed OS. Doing the update on the Server side. Which we canât track, of course. I would like to use my new setup but I canât. I havenât tried today yet but I will give you updates when I do. Basically, I turn it on. And after two seconds, it disengages. For no reason. I havenât touched any inputs that would do such a thing really weird.
The post you are responding to is over two years old now, and encompasses a) FS2020 and b) many SUs and improvements in that sim version. Is your post FS2020 related?
Ohh Iâm sorry this website is confusing how do I start a new topic canât find it anywhere
Never mind I found it thank you
So for example, you can click this link to go to User Support Hub > Aircraft & Systems and youâre looking for the + New Topic Button in the upper right.
Click that and you can start a new topic.
Closing this thread as itâs quite OBE (Overtaken By Events) and will just cause confusion because of itâs age.