#Is it a MF bug or is it me?

1 messages · Page 1 of 1 (latest)

tribal birch
#

X-Plane 12 with X-Trident AW109SP aircraft. MF 10.5.3 / 7-Segment LED 4 digit TM1637

I have MF on autostart and fine that works and all is good except the 4-digit display reads 0 0 0 0.......and the QNH is not showing as per on the aircraft. But if I stop the running of MF and then re-start run, it now reads the QNH correctly on the display. In other words it’s not reading the output dataref on initial start but stopping MF and re-running fixes problem. Any idea what's going on? Is there indeed a bug or is it me doing something wrong…….what extra info do you need?

odd skiff
zenith jewel
#

added a comment, apparently Spad waits ~6 seconds before connecting after Xplane starts and finishes loading. Maybe the API needs a bit of time to work properly?

tribal birch
#

thanks for replies…….OK yes it’s the same problem……so, is this something that needs to be looked at (fixed) for future release of MF or is this an X-Plane issue? Not clear about this. I’ll look at a bat file to impose a delay before starting MF after X-Plane finishes loading…….??

zenith jewel
#

it is probably a bit of both, and waiting a bit before commencing autorun might be a workaround

#

and your bat file might indeed be a good way to test the theory that the timeout is needed

#

ie, does autorun work if xplane is started first?

#

or does the issue happen also then?