[BUG] FFA320 not reporting engine start / stop in smartcars log

[Ezilinx-Craig]

Describe the bug

Upon landing at EGLL was unable to submit a Pirep as the system didn't detect engine off. No engine off appeared in the GUI log viewer.

How do you reproduce this bug?

I flew the same flight sometime later after a restart, including checked for updates and the same result. In my testing I noted

• SC detected the engine on only if XP was configured for engines on start up
• SC did not detect engine start if started by user

After testing flew same route in Zibo 737, SC detected engine start and stop and was able to submit Pirep.

It appears the problem only exists with FF A320

Expected behavior

Expected that upon engine shutdown, it appears in the GUI log and the button submit Pirep to appear

Screenshots

No response

Operating system

Windows 10 22H2

Community airline

Qantas

smartCARS Version

0.13.0

Plugins installed

flight center, flight tracking

Additional context

No response

[Thien42]

Are you using the fsuipc/xpuipc tracking or x-plane native tracking for your flights?

This can be found in the app settings.

[Ezilinx-Craig]

fsuipc tracking, do you want me to try xplane?

[Thien42]

It would actually help us a lot if you could. If this is an issue with xpuipc itself, there won't be much we can do about it unfortunately

[Ezilinx-Craig]

Can confirm when using xplane it works :-)

[GenericNerd]

Since using the correct tracker seems to have fixed this issue, we will be closing it for now.