Any possibility to control e.g VS?

[John Dowson]

3 minutes ago, ark1320 said:

My concern with the tests described above, which I conducted with the a/c sitting on the ground,  is the working of Simconnect. As you can see in the picture I posted, the Baron58/G1000 in MSFS has a blue VS bug that can be set. The value of the bug is also shown at the top of the VS scale. This is the target VS for the AP,  not necessarily the current VS.  While the tests showed the VS bug can be set by writing to Offset 0x07F2 , the question is why does this only work if you first execute (write) the non-working AP VS SET control (66102) at least once?  Does this indicate a problem with Simconnect, or with FSUIPC7, or with the sim itself somehow?

Maybe @Thomas Richter could comment on this

 I'm reluctant to implement any workaround for this that I don't fully understand, and could maybe adversely affect other AP implementations,. As a (maybe) temporary workaround, you could overload your button functions so that they always send (although only actually needed on the first press - maybe you could test for this via an offset condition)  an AP SET control before writing to offset 0x07F2.

[ark1320]

8 minutes ago, John Dowson said:

Maybe @Thomas Richter could comment on this

 I'm reluctant to implement any workaround for this that I don't fully understand, and could maybe adversely affect other AP implementations,. As a (maybe) temporary workaround, you could overload your button functions so that they always send (although only actually needed on the first press - maybe you could test for this via an offset condition)  an AP SET control before writing to offset 0x07F2.

John,

I agree you should not implement workarounds at this time. I'm not currently doing any 'real' flying in MSFS because it has so many problems right now. My interest is in helping to get FSUIPC7 working well in anticipation of when MSFS finally is usable in a manner similar to P3Dv5.

Al

[Thomas Richter]

Hi,

at the moment I think SimConnect and MSFS are not really in line at all and we start to try to make too many things work they might (hopefully) partly fixed or implemented with the next SimConnect update. As we found there are even Controls working they are neither listed or tested by Asobo and it was just a very time consuming try and error way to find out.

As you will find in different places of announcements of the MSFS state by MS/Asobo they more and more tell this or the other is not working correct or at all or should not be used. Special automated systems like AP/ AT are often mentioned already by MS/Asobo as "partly" working . . . As long the Systems itself are not fully replicated in their basic functions, the incomplete SimConnect interfacing wouldn't help even if it would work more as it should.

Lets hope the next Update has something more that the last 1.8.3.0

Thomas