Panel Failure Offsets

[ab-tools]

Hello Pete,

 

I'm currenlty trying to use FSUIPC together with Prepar3d 2.5/3.0 regarding panel failures and found here the offsets 0B64 to 0B73 in your offset documentation.

 

First of all I want to mention that I successfully tested offset 0B69 which worked perfectly for me in read and write mode (so you could update your documentation accordingly  ;-) ).

 

But I do have a problem with offset 0B64:

although this is marked as "Ok-SimC" for both read and write, I can use it without problems in write mode by setting it to "1" (and the corresponding panel also really fails then - so it's working correctly), but when reading the value back, it returns "0" again although the panel is still failed.

 

Any idea what's wrong here - especially as your documentation says this would work fine?

 

Best regards and thanks in advance

Andreas

[Pete Dowson]

First of all I want to mention that I successfully tested offset 0B69 which worked perfectly for me in read and write mode (so you could update your documentation accordingly  ;-) ).

 

Okay. Thank you. 

 

But I do have a problem with offset 0B64:

although this is marked as "Ok-SimC" for both read and write, I can use it without problems in write mode by setting it to "1" (and the corresponding panel also really fails then - so it's working correctly), but when reading the value back, it returns "0" again although the panel is still failed.

 

The variable, being read directly from SimConnect, is "PARTIAL PANEL ADF". If you Monitor 0B64 on the right-hand side of FSUIPC's logging tab it would show the actual variable being read and the value supplied. If that isn't working it needs reporting to L-M. Please check.

 

This variable is actually the same one written to when you write to the offset.

 

Any idea what's wrong here - especially as your documentation says this would work fine?

 

Well I suppose they were confirmed as working fine in FSX, which is all the Offsets Status document actually deals with.  I expect with so much development going on by L-M that another few columns might be needed for versions of P3D. (Ouch! But who's got time to test them all? :sad: )

 

Pete

[ab-tools]

Hello Pete,

 

first thanks a lot for your quick reply on that!

 

I just gave it a try against FSX (standard, no Steam edition) and it did not work either to read the correct value back from offset 0B64:

I always get "0" although it was set to "1" (and the panel has failed).

 

So this really looks like a bug (in FSX and your documentation ;-) ) as only write works, but not read.

 

Although I don't think Lookheed Marting will do much about it in near future, I would at least like to let them know:

do you have a direct way of reporting such bugs or should I just post things like that in their forum?

 

Best regards and thanks for your quick support again

Andreas

[Pete Dowson]

So this really looks like a bug (in FSX and your documentation ;-) ) as only write works, but not read.

 

Or it worked in one of the 4 FSX releases. I don't test all these things -- I don't even understand them all. They are simply exposing values of the given description in FS.

 

If it says "OK" it is because it was reported to me to be okay. All I can do now is add a ? against it. I've already changed my master copy to show 0B69 works because of your report. Maybe now someone will report to me that it is an error because it doesn't work in FSX?  I really don't know how to proceed. Probably best to put in a general warning saying "nothing here is guaranteed to work". ;-)

 

 

Although I don't think Lookheed Marting will do much about it in near future, I would at least like to let them know:

do you have a direct way of reporting such bugs or should I just post things like that in their forum?

 

All bugs need reporting in their Forums please.

 

Pete

[ab-tools]

Hello Pete,

 

OK, thanks for your quick reply again!

 

Bug report in Prepar3d forum is done. ;-)

 

Andreas