Version: 1.38.2.0
Frequency: Consistently
Severity: High
Context: Editing and mounted
Bug description: The SDK documentation has the BRAKE LEFT/RIGHT POSITION and EX1 variables listed as writable. When trying to set any value, including zero, the A:vars are trying to jump to 100%.
Repro steps: Create an UPDATE section and put the following code in:
(L:TEST_MODE) 1 == if{
(L:TEST_VALUE) (>A:BRAKE LEFT POSITION, Percent)
}
(L:TEST_MODE) 2 == if{
(L:TEST_VALUE) (>A:BRAKE LEFT POSITION EX1, Percent)
}
Open Simvars.exe to monitor the A:vars.
- Release the parking brake if set.
- Test that the left brake works normally
- In Devmode, go to LocalVars and set the TEST_MODE L:var to 1 or 2
- Now the TEST_VALUE L:var feeds into the A:var. You’ll notice that the A:Var goes to 100% no matter what value you feed it
- Set TEST_MODE to 0 and the Brake works normally again because we aren’t feeding it anything.
The same can be tested by “spamming” the Avar with the Simvars.exe app. As long as you’re clicking SET VALUE it will try to go to 100% and when you leave it it drops back to zero.