Simulator
2024
Aircraft Version
Development
Build info
{
"built": "2026-08-06T01:40:03+00:00",
"ref": "refs/heads/master",
"sha": "27a6560c92a261d0b437dc0f9f1efcea2490a169",
"actor": "tracernz",
"event_name": "manual",
"pretty_release_name": "master:27a6560c",
"version": "a380x-v2024.2.0-dev.27a6560"
}
Describe the bug
RMP auto-brightness initialisation is non-functional due to two bugs in setRmpBrightness() (LightSync.ts):
-
The target LVar uses a literal, never-substituted #RMP_ID# placeholder, so writes never reached the real per-RMP brightness vars.
-
The brightness value is multiplied by 100 before being sent, pushing it far outside the valid range.
Expected behavior
RMP screen brightness should track auto-brightness the same way PFD/ND/MFD/ECAM etc. do.
Steps to reproduce
- Spawn with cabin auto-brightness enabled.
- Observe RMP screens vs. other displays. Brightness does not match/respond correctly.
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
YouBaconMeCrazy
Simulator
2024
Aircraft Version
Development
Build info
{ "built": "2026-08-06T01:40:03+00:00", "ref": "refs/heads/master", "sha": "27a6560c92a261d0b437dc0f9f1efcea2490a169", "actor": "tracernz", "event_name": "manual", "pretty_release_name": "master:27a6560c", "version": "a380x-v2024.2.0-dev.27a6560" }Describe the bug
RMP auto-brightness initialisation is non-functional due to two bugs in
setRmpBrightness()(LightSync.ts):The target LVar uses a literal, never-substituted
#RMP_ID#placeholder, so writes never reached the real per-RMP brightness vars.The brightness value is multiplied by 100 before being sent, pushing it far outside the valid range.
Expected behavior
RMP screen brightness should track auto-brightness the same way PFD/ND/MFD/ECAM etc. do.
Steps to reproduce
References (optional)
No response
Additional info (optional)
No response
Discord Username (optional)
YouBaconMeCrazy