Skip to content
This repository has been archived by the owner on May 9, 2024. It is now read-only.

Crash when connected as SUP with another connection #85

Open
RudiZhang opened this issue Nov 4, 2023 · 6 comments
Open

Crash when connected as SUP with another connection #85

RudiZhang opened this issue Nov 4, 2023 · 6 comments

Comments

@RudiZhang
Copy link

connected as a pilot and SUP, crashes when started
pierr3 added a commit that referenced this issue Nov 5, 2023
@pierr3
Another look at #85
574a60a
@pierr3
Copy link
Owner

pierr3 commented Nov 5, 2023

Does AFV native not crash in the same scenario?

@RudiZhang
Copy link
Author

Does AFV native not crash in the same scenario?

No, AFV works normally

@pierr3
Copy link
Owner

pierr3 commented Nov 10, 2023

When you try to connect, is the callsign that appears on the UI your SUP callsign or your pilot callsign?

@RudiZhang
Copy link
Author

When you try to connect, is the callsign that appears on the UI your SUP callsign or your pilot callsign?

AFV shows SUP callsign, VectorAudio crash directly without showing anything

@amosngSP
Copy link

Following up on this, I had two connections, one APP & one SUP connection. VectorAudio detected my SUP connection, but I was unable to XC or TX to my ATC connection. Could this be a feature to allow SUP TX/XC on another frequency? Native AFV supports it.

@pierr3
Copy link
Owner

pierr3 commented Dec 30, 2023

This will be fixed in the next release

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pierr3 @amosngSP @RudiZhang