We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Development
{ "built": "2023-09-04T02:30:14+00:00", "ref": "refs/heads/master", "sha": "12c8e357bccc95d58b6fab4d2e2051ca6b9940fb", "actor": "Benjozork", "event_name": "manual", "pretty_release_name": "master:12c8e357", "version": "v0.11.0-dev.12c8e35" }
The fwd and aft temperatures are using the LVAR for cockpit temperature.
I think it's a regression caused by this PR: #8118
I already put a comment on that PR.
The fwd and aft temperatures should use their own LVAR to get the right temp
Fly as usual and try to change the cockpit temp.
You will see that all temps (including fwd and aft) will be displayed as cockpit temp
No response
The text was updated successfully, but these errors were encountered:
Good catch 👍.
Sorry, something went wrong.
Do I have to assign the issue to myself prior to fixing? Or this done by creating a PR for this issue?
Hi, it’s best you create a draft PR already which mentions this issue you want to fix.
Successfully merging a pull request may close this issue.
Aircraft Version
Development
Build info
Describe the bug
The fwd and aft temperatures are using the LVAR for cockpit temperature.
I think it's a regression caused by this PR: #8118
I already put a comment on that PR.
Expected behavior
The fwd and aft temperatures should use their own LVAR to get the right temp
Steps to reproduce
Fly as usual and try to change the cockpit temp.
You will see that all temps (including fwd and aft) will be displayed as cockpit temp
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
No response
The text was updated successfully, but these errors were encountered: