-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ND range change messages are incorrect #9473
Comments
I would like to attempt this. |
i think i saw someone collecting info on discord to work on this. not sure if they have already completed it. best to check on discord. if no one is working on it, make a draft PR first. |
Yeah that was me. Sorry for the confusion. |
@danestfanous Hi just wanted to check if you are still working on this? If not I can take a look at it |
@MrJigs7 Hello! I was able to fix it on my end but I couldn't sync it with Github. Feel free to give it a try and let me know if you'd like to see what I did. |
What’s the issue with the sync? |
@danestfanous Feel free to send over what you did and I can push it and will add you as a credit on the change log 👍 |
My issue was that I was able to make the change with the files on my computer, but when attempting to edit the code on GitHub, I found that the files are in fbw-common so it was a little more complicated. If you'd like, send me your discord, it would be easier to discuss there. |
Sure, MrJigs on discord |
I sent you a friend request. I'm sad10mane |
Whilst working on this I've noticed the RANGE CHANGE flag positioning seems a little off, at least compared to the reference picture provided on Discord for the A380. Happy to update it as part of this issue if someone is able to provide a reference picture of the RANGE CHANGE flag on the A320 so I can check if the positioning is the same |
Aircraft Version
Stable
Build info
N/A
Describe the bug
ND says "RANGE CHANGE"
VD has no message
Expected behavior
ND should say "ND RANGE CHANGE"
VD should say "VD RANGE CHANGE"
Steps to reproduce
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
No response
The text was updated successfully, but these errors were encountered: