Issue with offset 580 (heading)

[guda]

Hi Pete,

I'm developping a software and I have an issue with offset 580.

Regarding your documentation I'm reading the value on 4 bits. It works fine with my FS2004.

One of my beta tester (FSX/Win7) has bad value for the heading. I can correct it using 2bits and not 4 bits.

Is it normal?

Regards

Dan

[Pete Dowson]

I'm developping a software and I have an issue with offset 580.

Regarding your documentation I'm reading the value on 4 bits. It works fine with my FS2004.

0580 is 4 BYTES long, not 4 bits. 4 bits can only accommodate values to 15.

One of my beta tester (FSX/Win7) has bad value for the heading. I can correct it using 2bits and not 4 bits.

You have an error then. Assuming you really mean "bytes" not "bits", if you only read the first 2 bytes you will only get part of the fractional value of the heading.

Please use the tools available to check your work. You can use logging and Monitoring in FSUIPC, and of course FSInterrogate.

Regards

Pete

[guda]

Thanks FSInterrogate I think to have found the issue. When I use VB Integer the results is bad in FSX. Now I'm using Uinteger and I seems OK

It's strange because both manage 4 bytes number.

Thank you

[Pete Dowson]

Thanks FSInterrogate I think to have found the issue. When I use VB Integer the results is bad in FSX. Now I'm using Uinteger and I seems OK

It's strange because both manage 4 bytes number.

Maybe you aren't handling negatives with the normal integer. Any heading greater or equal to 180 will look negative with a signed variable. It's still valid. Just add 360 to the computed result if it is negative.

Regards

Pete